Update and rename governance-criteria.md to governance.md #69
+84
−65
Conversation
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
Clarified the difference between maintenance and regular upgrades, which have different requirements. Added new sections explaining the governance requirements for maintenance and regular upgrades
✅ Deploy Preview for op-stack-pm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
geoknee
reviewed
Oct 20, 2025
Comment on lines
+19
to
+23
| ### Consensus Changes | ||
|
|
||
| - Upgrade type: Regular | ||
| - Rationale: Modifies the state transition function or messaging validity. | ||
| - Examples: Bedrock, EIP‑4844, Shanghai, any L1 upgrade modifying a contract under Security Council control (unless emergency bugfix). |
Contributor
There was a problem hiding this comment.
We should consider upgrades like Fusaka defense (generally, any L1 fork implying a change to L2 state transition function). Generally we want those to be maintenance upgrades, not regular ones. Often, they are under increased time pressure / external deadlines and could result in a superchain halt or chain splits if we don't act swiftly.
Contributor
There was a problem hiding this comment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Clarified the difference between maintenance and regular upgrades, which have different requirements. Added new sections explaining the governance requirements for maintenance and regular upgrades
Tests
none
Additional context
Found here
Metadata
none