test: add token state after upgrade flow

[arad-starkware]

This change is 

---

Note

Adds a new flow and test to verify token enable/disable behavior across upgrade and during consensus rewards, and imports v3 BTC pool reward calc.

• Flow Tests:
  • EnableDisableTokenBeforeAfterUpgradeFlow in src/flow_test/flows.cairo:
    • Sets up two BTC tokens, delegates to both, toggles enable/disable before and after upgrade.
    • Verifies get_tokens view and rewards distribution pre/post-upgrade and under consensus rewards.
  • Registers test enable_disable_token_before_after_upgrade_flow_test in src/flow_test/fork_test.cairo.
• Utilities:
  • Imports calculate_staker_btc_pool_rewards_v3 for v3 reward calculations.
• Docs:
  • Cleans up src/flow_test/flow_ideas.md by removing obsolete token test idea.

^{Written by Cursor Bugbot for commit 8a44fec. This will update automatically on new commits. Configure here.}

[arad-starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• test: add accrue_rewards_across_versions flow #82 : 2 dependent PRs (#83 , #84 )
• test: add attest after upgrade test #71
• test: add token state after upgrade flow #59 👈 (View in Graphite)
• test: add update_rewards toggle tokens flow test #57
• test: add balances delay flow #65
• chore: update flow ideas #61
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[noa-starkware]

Reviewable status: 0 of 3 files reviewed, 5 unresolved discussions (waiting on @arad-starkware)

---

src/flow_test/flows.cairo line 7147 at r1 (raw file):

/// Flow:
/// Add tokens A and B

/// Delegate for both tokens

---

src/flow_test/flows.cairo line 7149 at r1 (raw file):

/// Add tokens A and B
/// Enable token B
/// Advance epoch

not relevant to the test, remove from doc

Code quote:

/// Enable token B
/// Advance epoch

---

src/flow_test/flows.cairo line 7237 at r1 (raw file):

        );
        staking_attestation
            .update_rewards_from_attestation_contract(staker_address: staker.staker.address);

why not system.attest(staker)?

---

src/flow_test/flows.cairo line 7237 at r1 (raw file):

        );
        staking_attestation
            .update_rewards_from_attestation_contract(staker_address: staker.staker.address);

test also staker rewards (own+commission from pool a)

---

src/flow_test/flows.cairo line 7250 at r1 (raw file):

        assert!(expected_rewards.is_non_zero());
        assert!(rewards_a == expected_rewards);
        assert!(rewards_b.is_zero());

test also with V3 rewards? we have such test somewhere?

[arad-starkware]

Reviewable status: 0 of 3 files reviewed, 5 unresolved discussions (waiting on @arad-starkware and @noa-starkware)

---

src/flow_test/flows.cairo line 7147 at r1 (raw file):

Previously, noa-starkware wrote…

/// Delegate for both tokens

Done.

---

src/flow_test/flows.cairo line 7149 at r1 (raw file):

Previously, noa-starkware wrote…

not relevant to the test, remove from doc

Done.

---

src/flow_test/flows.cairo line 7237 at r1 (raw file):

Previously, noa-starkware wrote…

why not system.attest(staker)?

Done.

---

src/flow_test/flows.cairo line 7237 at r1 (raw file):

Previously, noa-starkware wrote…

test also staker rewards (own+commission from pool a)

Done.

---

src/flow_test/flows.cairo line 7250 at r1 (raw file):

Previously, noa-starkware wrote…

test also with V3 rewards? we have such test somewhere?

I'm not sure what's the scenario you're describing, testing V3 rewards with disabled tokens after upgrade?

[noa-starkware]

Reviewable status: 0 of 3 files reviewed, 4 unresolved discussions (waiting on @arad-starkware)

---

src/flow_test/flows.cairo line 7250 at r1 (raw file):

Previously, arad-starkware wrote…

I'm not sure what's the scenario you're describing, testing V3 rewards with disabled tokens after upgrade?

Yes, just continue the test with start consensus epoch, then call update_rewards and test rewards again (only a token enabled)

---

src/flow_test/flows.cairo line 7191 at r3 (raw file):

        system.advance_epoch();
        system.staking.disable_token(token_address: token_b.contract_address());
        system.staking.enable_token(token_address: token_a.contract_address());

I think these lines might be redundant

Code quote:

        system.staking.disable_token(token_address: token_b.contract_address());
        system.staking.enable_token(token_address: token_a.contract_address());

---

src/flow_test/flows.cairo line 7240 at r3 (raw file):

            calculate_staker_btc_pool_rewards_v2(
            pool_balance: delegation_amount,
            commission: 200,

Suggestion:

system.staker_info_v1(:staker).pool_info.unwrap().commission

[arad-starkware]

Reviewable status: 0 of 3 files reviewed, 2 unresolved discussions (waiting on @arad-starkware and @noa-starkware)

---

src/flow_test/flows.cairo line 7250 at r1 (raw file):

Previously, noa-starkware wrote…

Yes, just continue the test with start consensus epoch, then call update_rewards and test rewards again (only a token enabled)

Done.

---

src/flow_test/flows.cairo line 7191 at r3 (raw file):

Previously, noa-starkware wrote…

I think these lines might be redundant

I wanted to explicitly disable a token instead of just leaving it disabled by default. Do you think it's unnecessary?

---

src/flow_test/flows.cairo line 7240 at r3 (raw file):

            calculate_staker_btc_pool_rewards_v2(
            pool_balance: delegation_amount,
            commission: 200,

Done