staking/certora
r4bbit ad224c4872
fix(Certora specs): ensure prover runs rules on `currentContract`
Since we're implementing rules for `StakeManager` migrations, we need
multiple instances inside the certora specs.

This results in the prover trying to run rules on the other
`StakeManager` instance as well, which isn't always desired,
as it causes some rules to fail, even though they'd pass if they'd be
executed only on the `currentContract`.

This commit makes the filter condition for relevant rules stronger, such
that the prover will not run them on the `newStakeManager` contract
instance.
2024-03-01 13:40:05 +01:00
..
confs fix: StakeManager migration fixes and certora rules 2024-02-20 09:08:00 +01:00
harness fix: StakeManager migration fixes and certora rules 2024-02-20 09:08:00 +01:00
helpers chore: certora setup for stakemanager and vault 2024-02-20 09:04:23 +01:00
specs fix(Certora specs): ensure prover runs rules on `currentContract` 2024-03-01 13:40:05 +01:00