r4bbit 5cdd54a884 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-05 10:21:26 -03:00

..

mocks

fix(StakeVault): make unstaking actually work

2024-01-19 09:57:34 +01:00

script

fix(StakeVault): make unstaking actually work

2024-01-19 09:57:34 +01:00

StakeManager.t.sol

fix(StakeManager): don't allow migration initialization while migrating

2024-03-05 10:21:26 -03:00

StakeVault.t.sol

fix(StakeVault): make unstaking actually work

2024-01-19 09:57:34 +01:00

VaultFactory.t.sol

cleanup(VaultFactoryTest): remove unused import

2024-01-23 15:11:10 +01:00