test: add attest after upgrade test

[arad-starkware]

This change is 

---

Note

Adds a flow testing attestation behavior immediately after upgrade (fail then succeed post-epoch) and wires it into mainnet-fork tests.

• Flow tests:
  • Add AttestAfterUpgradeFlow in src/flow_test/flows.cairo to validate attestation immediately after upgrade:
    • First attest via IAttestationSafeDispatcherTrait fails (no previous-epoch trace), then after advancing an epoch attestation succeeds and rewards equal calculate_staker_strk_rewards_v2.
  • Register test attest_after_upgrade_flow_test in src/flow_test/fork_test.cairo.

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

[arad-starkware]

• test: add accrue_rewards_across_versions flow #82 : 2 dependent PRs (#83 , #84 )
• test: add attest after upgrade test #71 👈 (View in Graphite)
• test: add token state after upgrade flow #59
• 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.81%. Comparing base (b42160b) to head (0becc70).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #71   +/-   ##
=======================================
  Coverage   95.81%   95.81%           
=======================================
  Files          42       42           
  Lines       10194    10194           
=======================================
  Hits         9767     9767           
  Misses        427      427           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[noa-starkware]

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

---

src/flow_test/flows.cairo line 7136 at r2 (raw file):

        );
        let result = attestation_safe.attest(block_hash: Zero::zero());
        assert_panic_with_error(:result, expected_error: "Index out of bounds");

Doc why we expect to fail with this error.

[arad-starkware]

Reviewable status: 0 of 2 files reviewed, 1 unresolved discussion (waiting on @noa-starkware)

---

src/flow_test/flows.cairo line 7136 at r2 (raw file):

Previously, noa-starkware wrote…

Doc why we expect to fail with this error.

Done.

[noa-starkware]

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

---

src/flow_test/flows.cairo line 7136 at r2 (raw file):

Previously, arad-starkware wrote…

Done.

fixed in V3 sounds like staker can attest, but we only fixed the error msg.

---

src/flow_test/flows.cairo line 7136 at r4 (raw file):

        );
        let result = attestation_safe.attest(block_hash: Zero::zero());
        // Fails because the staker trace has no entry for the previous epoch (fixed in V3).

Suggestion:

// Fails because a staker can’t attest in their starting epoch (zero balance).
// If the staker started in V2, the trace has no entry for that epoch, so it reverts with an "index out of bounds" error (this case).
// If the staker started in V3, the trace includes that entry, so it reverts with ATTEST_WITH_ZERO_BALANCE.

[arad-starkware]

Merge activity

• Dec 4, 1:12 PM UTC: @arad-starkware merged this pull request with Graphite.