staking/contracts
r4bbit da007451a4 fix(StakeManager): ensure `currentEpoch` is `0` when migrating
A previous manager can only migrate once, because the migration address
is locked in. A **new** manager is always aware of its previous manager.

This means, when a migration happens and is initialized, we know for
sure it's always the first time this is happening.

We probably don't want a migration to take place if the new manager has
already processed epochs, so we're adding a check that its
`currentEpoch` must be `0`.

This also ensures one of its invariants isn't violated:

`epochsOnlyIncrease` and `highEpochsAreNull`.
2024-03-05 10:21:26 -03:00
..
StakeManager.sol fix(StakeManager): ensure `currentEpoch` is `0` when migrating 2024-03-05 10:21:26 -03: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