staking/certora
r4bbit 235b347c33
fix(StakeManager): don't allow migration initialization while migrating
This is actually a bug that the certora prover found.
The rule `epochStaysSameOnMigration` failed because a previous
`StakeManager` could call `migrationInitialize` and change
`currentEpoch` on a next `StakeManager`, even though the next `StakeManager`
might be in migration itself (which means the `currentEpoch` is now
allowed to change).

This commit fixes this by ensure `migrationInitialize()` will revert if
the `StakeManager` already has a `migration` on going.
2024-03-01 13:40:11 +01:00
..
confs fix: StakeManager migration fixes and certora rules 2024-02-20 09:08:00 +01:00
harness fix: StakeManager migration fixes and certora rules 2024-02-20 09:08:00 +01:00
helpers chore: certora setup for stakemanager and vault 2024-02-20 09:04:23 +01:00
specs fix(StakeManager): don't allow migration initialization while migrating 2024-03-01 13:40:11 +01:00