The migration to L2 is a major step for Beanstalk and as this involves critical protocol updates as:
Burning Beans on L1
Minting Beans on L2 and updating s.sys.migration.migratedL1Beans
with the new amount to be minted.
This operation must be ensured to function only when the protocol is behaving as expected. In case any unexpected incident happens and the protocol needs to be paused, the minting of Beans on L2 will still remain and protocol can be at risk when minting beans should be paused.
When the protocol is paused due to an unexpected/major incident that is related to minting/burning beans, the migration process will not be covered, thus not pausing the development of the incident.
Manual Review
Ensure that the L2 migration is protected by the "pause" check.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.