[Tracker] OPCM Upgrades (Upgrade 13)

[maurelian]

Description

This is a tracking issue for the work outlined in the L1 Upgrades Design Doc.

Milestone: Devnet

Items which must be completed prior to the devnet deployment.

• Ensure tests run against both the fresh and upgraded system (OPCM - Upgrade 13) #13079
• Support for optional block number to just test-upgrade (OPCM - Upgrade 13) #13339
• Add all necessary contracts to the SystemConfig’s Addresses struct (OPCM - Upgrade 13) #13073
• Add temporary reverts to code paths using a custom gas token (OPCM - Upgrade 13) #13589
• New release() getter to represent the release (OPCM - Upgrade 13) #13076
• Add an upgrade() function to all L1 contracts (OPCM - Upgrade 13) #13072
• Vendor in OZ V5 Initializable implementation (OPCM - Upgrade 13) #13071
• Fully remove CGT code from L1 contracts (OPCM - Upgrade 13) #13671
• Add SuperchainConfig and ProtocolVersions to the OPCM's Implementations struct (OPCM - Upgrade 13) #13682

Milestone: Betanet (Feb 4)

• Implement the initial superchain-ops runbook (OPCM - Upgrade 13) #13362

Milestone: Testnet (Feb 20)

Items which must be completed prior to the testnet deployment.

• New opcm.upgrade() method (OPCM - Upgrade 13) #13078
• Deploy all implementations using Create2 (OPCM - Upgrade 13) #13644
• CI job that runs the upgrade tests for all base chain <> OP Chain pairings (OPCM - Upgrade 13) #13401
• Update FMA status to 'implementing actions' (OPCM - Upgrade 13) #13593
• -rc is removed when upgrade() is called by the Upgrade Controller. (OPCM - Upgrade 13) #13077
• OPCM: New addGameType() method. (OPCM - Upgrade 13) #13070
• Deprecate snake cased OPCM.OUTPUT_VERSION() method. (OPCM - Upgrade 13) #13388
• Add _postCheck() function to OPCM #13836
• Replace delegate caller with safe in OPCM upgrade tests (upgrade 13) #13993
• Add mipsVersion flag to op-deployer bootstrap opcm and default to 2 (OPCM - Upgrade 13) #13996
• Testing to detect when a release has occurred and any non-empty upgrade() methods should be reset. (OPCM - Upgrade 13) #13080
• Add upgrade path testing for all supported chains in CI. (OPCM - Upgrade 13) #13607
• Expand set of tests run in forked upgrade path (OPCM - Upgrade 13) #13411
• [EPIC] op-deployer changes for OPCM upgrades (OPCM - Upgrade 13) #13081
• benchmark cost of superchain upgrade (OPCM - Upgrade 13) #13835
• OPCM fix: addGameType does not emit an event (OPCM - Upgrade 13) #14140
• OPCM Fix: Missing checks in OPCM (OPCM - Upgrade 13) #14141
• OPCM Fix: Failure when addGameType due to common saltMixer (OPCM - Upgrade 13) #14142
• Update OPCM specs to match current implementation (OPCM - Upgrade 13) #14173
• Update generic contract failure modes based on OPCM design-docs#200

Milestone: Governance Proposal (Feb 27)

• Post Proposal

Milestone: Mainnet (April 2)

Items which must be completed prior to the mainnet deployment.

• superchain-registry changes - Design and implement the mechanism for mapping release versions to an OPCM (OPCM - Upgrade 13) #13082
• Detect superchain-registry changes affecting upgrade fork tests (OPCM - Upgrade 13) #13380
• opcm: Define on canonical representation for OPCM addresses in SCR (OPCM - Upgrade 13) superchain-registry#806
• OPCM to release 1.0.0 (OPCM - Upgrade 13) #13599
• Document release process updates #13994

Milestone: Post-Mainnet

Items which must be completed shortly after mainnet.

• New InitializedResetter contract (OPCM - Upgrade 13) #13074
• Modify Test Setup to use op-deployer rather than Deploy.s.sol (OPCM - Upgrade 13) #13331
• Document manual monorepo steps associated with a new upgrade (OPCM - Upgrade 13) #13410
• Revised OPCM oriented bounty and audit processes (OPCM - Upgrade 13) #14055
• Checklist for shipping contracts to prod (OPCM - Upgrade 13) #13228
• OPCM: Add permissionless game to deploy() (OPCM - Upgrade 13) #14235

[K-Ho]

Sharing Product context on the importance of OPCM:

Problem:
There are two major pain points with upgrading the L1 contracts for the chains in the Superchain

1. Because many chains in the superchain currently have different versions of their L1 contracts, upgrading contracts requires a time consuming process of tracking every different version of the contracts for different chains and handling each upgrade differently.
   If we do nothing, the contract changes for Isthmus would force us to perform the same time consuming manual tasks to track down all versions of the contracts and require more work to get all contracts to the same version.
2. If we keep adding chains to the SC with our upgrades process as-is, there is an enormous amount of increased manual labor for the OP Labs security team and for the Security Council. This includes manual validation of every storage slot, for every upgrade, for every chain—along with the ability to track any subtle variations that may exist for chains that are on different versions. This creates a lot of surface area for something to go wrong.
   Solution
3. OPCM upgrades will allow us to easily get all chains in the Superchain to the same version of the contracts with the Isthmus upgrade(although some chains will be permissioned vs. permissionless), making this version hell a thing of the past.
4. OPCM streamlines the security council signing process

Risks
If we do not thoroughly test out the OPCM upgrade for Isthmus on devnets before the Isthmus testnet upgrade we could risk errors in the upgrade process.