Skip to content
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

Closed
wants to merge 29 commits into from

Conversation

maurelian
Copy link
Contributor

@maurelian maurelian commented Jan 22, 2025

A strawman PR to demonstrate my understanding of the MTCannon upgrade path.

Important details:

  1. the Mips64 address is hardcoded into the OPCM
  2. ALL games pdg or fdg get the same absolutePrestate taken from releases.json

Copy link
Contributor Author

maurelian commented Jan 22, 2025

@maurelian maurelian changed the title mtcannon upgrade notes feat: Include MTCannon in OPCM upgrade Jan 22, 2025
@maurelian maurelian force-pushed the opcm-up/upgrade-asr branch 5 times, most recently from 5607ae4 to d14c0c6 Compare January 23, 2025 14:26
Base automatically changed from opcm-up/upgrade-asr to develop January 23, 2025 14:38
Comment on lines +174 to +175
/// @notice The prestate hash to be used for the upgrade.
bytes32 public immutable prestateHash;
Copy link
Contributor

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;
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants