mirror of https://github.com/logos-co/staking.git
5cdd54a884
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. |
||
|---|---|---|
| .. | ||
| mocks | ||
| script | ||
| StakeManager.t.sol | ||
| StakeVault.t.sol | ||
| VaultFactory.t.sol | ||