Add redeployment protection after estop#17
Merged
willemolding merged 3 commits intomainfrom Oct 2, 2025
Merged
Conversation
willemolding
force-pushed
the
willem/redeployment-protection
branch
from
3d99eb7 to
fc354e0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prior to this the Groth16 verifier programs were removed on an estop and an incremented nonce used to ensure no selector reuse.
After switching to hash based selectors it was possible for the owner to redeploy estopped verifiers to the old addresses (and selectors) at a later date. This is not part of the security mode.
estopped