-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Include MTCannon in OPCM upgrade #13930
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5607ae4
to
d14c0c6
Compare
/// @notice The prestate hash to be used for the upgrade. | ||
bytes32 public immutable prestateHash; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per @ajsutton, I think this should be an input per-chain, just to be safe? https://discord.com/channels/1244729134312198194/1332055053003001886/1332084289537441912
@@ -109,7 +109,7 @@ contract OPContractsManager is ISemver { | |||
address disputeGameFactoryImpl; | |||
address anchorStateRegistryImpl; | |||
address delayedWETHImpl; | |||
address mipsImpl; | |||
address mips64Impl; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MIPS is a singleton for all chains, so putting it in this struct feels a bit misleading
A strawman PR to demonstrate my understanding of the MTCannon upgrade path.
Important details:
absolutePrestate
taken from releases.json