Skip to content

opcm: Prep upgrade 14 for MTCannon#14570

Closed
mbaxter wants to merge 11 commits intodevelopfrom
mbax/upgrade-14/prep-opcm
Closed

opcm: Prep upgrade 14 for MTCannon#14570
mbaxter wants to merge 11 commits intodevelopfrom
mbax/upgrade-14/prep-opcm

Conversation

@mbaxter
Copy link
Contributor

@mbaxter mbaxter commented Feb 27, 2025

Description

Builds on #14564

Add a new OPCM contract for upgrade 14. Cut out upgrade logic so that upgrade() is just deploying new game implementations with the new MIPS64.sol vm contract.

Tests

TODO

Metadata

Part of #14459

@mbaxter mbaxter changed the title Mbax/upgrade 14/prep opcm opcm: Prep upgrade 14 for MTCannon Feb 27, 2025
@codecov
Copy link

codecov bot commented Feb 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.95%. Comparing base (48b645a) to head (b79b658).
Report is 5 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #14570      +/-   ##
===========================================
- Coverage    46.41%   41.95%   -4.46%     
===========================================
  Files         1036      865     -171     
  Lines        88779    78815    -9964     
===========================================
- Hits         41206    33068    -8138     
+ Misses       44507    42848    -1659     
+ Partials      3066     2899     -167     
Flag Coverage Δ
cannon-go-tests-32 ?
cannon-go-tests-64 ?
contracts-bedrock-tests ?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 181 files with indirect coverage changes

getGameConstructorParams(IFaultDisputeGame(address(_disputeGame)));

// Set the new vm value.
params.vm = IBigStepper(_implementations.mipsImpl);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To confirm my understanding, this MIPS contract is the shared singleton instance right?

That would mean that after this upgrade every chain would point to the same MIPS contract instance and thus the same PreimageOracle instance. Currently a bunch of chains have their own deployment of MIPS and PreimageOracle which makes monitoring more complex so would be wonderful if that got fixed as part of this upgrade. Existing games would keep pointing to whatever MIPS/PreimageOracle they were using previously so there's no compatibility concerns here, I'm just checking my understanding to ensure we really do get everything switched to using the singletons.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes - this is my understanding. @maurelian or @mslipper - can you confirm?

@mslipper
Copy link
Collaborator

mslipper commented Mar 4, 2025

Replaced by #14612.

@mslipper mslipper closed this Mar 4, 2025
@mbaxter mbaxter deleted the mbax/upgrade-14/prep-opcm branch October 23, 2025 14:35
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