r4bbit 5c1c0dfa97

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-04 09:52:09 +01:00

..

StakeManager.sol

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

2024-03-04 09:52:09 +01:00

StakeVault.sol

fix: StakeManager migration fixes and certora rules

2024-02-20 09:08:00 +01:00

VaultFactory.sol

feat: introduce VaultFactory (#38)

2023-11-07 09:49:22 +01:00