Closed 0x-r4bbit closed 6 months ago
This commit should actually pass just fine. Here's a certora job I ran on this commit: https://prover.certora.com/output/6199/9108462dc0734e85a63d32a303036c00?anonymousKey=ad4b679fc143ce45ebc4193e4fbd892f93eead05
For some reason, CI is taking an outdated state of the rules.
This is actually a bug that the certora prover found. The rule
epochStaysSameOnMigration
failed because a previousStakeManager
could callmigrationInitialize
and changecurrentEpoch
on a nextStakeManager
, even though the nextStakeManager
might be in migration itself (which means thecurrentEpoch
is now allowed to change).This commit fixes this by ensure
migrationInitialize()
will revert if theStakeManager
already has amigration
on going.Checklist
Ensure you completed all of the steps below before submitting your pull request:
forge snapshot
?pnpm gas-report
?pnpm lint
?forge test
?pnpm verify
?