r4bbit e6e05a3542 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 11:40:21 +01:00
..
StakeManager.spec	chore(Certora specs): comment out purposefully failing rule	2024-03-01 10:56:50 +01:00
StakeManagerStartMigration.spec	fix(StakeManager): don't allow migration initialization while migrating	2024-03-01 11:40:21 +01:00
StakeVault.spec	chore: certora setup for stakemanager and vault	2024-02-20 09:04:23 +01:00