Overview
Important
This is the op-contracts release for Upgrade 20. It moves chains from Output Root to Super Root Dispute Games, removes deprecated SystemConfig functions and the ProtocolVersions contract, and tightens OPCM and StandardValidator checks.
Breaking changes
- Super Root Dispute Games become the respected game types (#21689).
OPCM.upgrade()now always takes the Super Root path: a permissioned chain moves toSUPER_PERMISSIONED(game type5) and a permissionless chain toSUPER_CANNON_KONA(game type9). Their root claim is a Super Root, not an Output Root, and theirl2SequenceNumberis an L2 timestamp, not a block number. Integrations that read dispute game root claims directly must recognise game types5and9and userootClaimByChainId(uint256)to get the chain's Output Root. Games created before the upgrade still resolve, andOptimismPortal2accepts withdrawal proofs from both formats. SystemConfig.batchInbox()andSystemConfig.setGasConfig(uint256,uint256)removed (#21641). Both now revert. Read the batch inbox address from the rollup config or the superchain registry, and usesetGasConfigEcotone(uint32,uint32)to set fee scalars.overhead()remains but is deprecated and returns zero, and the first word of theFEE_SCALARSConfigUpdateevent is now always zero.SystemConfig.initializeno longer takes a batch inbox and clears the legacy slot.ProtocolVersionscontract removed (#20527). OPCM no longer deploys or upgrades it. Tooling that readsProtocolVersionsmust stop doing so.OPContractsManagerContainer.Implementationsstruct changed (#20527, #22218).protocolVersionsImplis gone andsp1PlonkAdapterImplis new, so tooling that decodes OPCM'simplementations()must use the new ABI.SuperPermissionedDisputeGameis a new, simplified game (#20641, #21513). It no longer runs a bisection game: only the proposer can create one, for a Super Root newer than the anchor, and it resolvesDEFENDER_WINSat creation. The fault dispute game interface (attack,defend,move,step,claimData,credit,claimCredit,challenger, the clock and bond getters, and so on) is removed from it, and it takes no bonds. TheGameTypes.SUPER_PERMISSIONED_CANNONconstant is renamedSUPER_PERMISSIONED; the game type value5is unchanged.- OPCM v8 upgrade inputs (#22096).
OPCM.upgrade()no longer permits thePermittedProxyDeploymentinstruction forDelayedWETH, and reverts withOPContractsManagerV2_InvalidUpgradeInstructionif it is passed; drop it from upgrade calls and templates. The upgrade also reverts for a chain that was not last upgraded by an OPCM v7, so a chain must be on op-contracts/v7.0.0 before it upgrades to this release.
Other changes
OPCM
OPCM.upgrade()accepts anoverrides.cfg.startingAnchorRootinstruction, so the Super Root upgrade can set the starting anchor (#21689)- New chains start with Super Root Dispute Games:
OPCM.deploy()accepts onlySUPER_PERMISSIONEDorSUPER_CANNON_KONAas enabled initial game types. A permissionless initial game needs a real starting anchor root rather than the0xdeadplaceholder, a nonzero absolute prestate and a starting sequence number below2^64(#21720, #21588) - Stricter dispute game config checks: an enabled game needs a nonzero init bond (and
SUPER_PERMISSIONEDmust have a zero one), and an enabled game type with no deployed implementation reverts withOPContractsManagerV2_ZeroGameImplementation(#20548) SUPER_CANNON(game type4) is retired. OPCM rejects configs for it, andupgrade()clears any existing registration of it in theDisputeGameFactory(#20363)upgrade()reverts withOPContractsManagerUtils_OZv5InitializableUnsupportedif a new implementation uses OpenZeppelin v5Initializablestorage, which OPCM cannot reset (#21070)- The
CANNON_KONAandL2CMDevFeaturesbits are retired, andSUPER_ROOT_GAMES_MIGRATIONalways reports enabled (#21663, #21591, #21689)
Dispute games
SuperPermissionedDisputeGamerejects a nonzeromsg.valueat creation, so ETH cannot be trapped in a game that has no bond accounting (#22410)
StandardValidator
- Checks that each registered dispute game implementation is the release implementation by address, not only by its reported version (
-150) (#22365) - Checks that
SystemConfig.l2ChainId()matches the expected chain ID (SYSCON-140) (#22366) - Checks that the dispute games use the same
AnchorStateRegistryas theOptimismPortal(-ANCHORP-70) (#22412) - Requires the legacy
CANNONgame type to be unregistered (PLDG-NOSHAPE) (#21621) - Validates the new
SuperPermissionedDisputeGameand its args (#20641)
L2 contracts
- New
FeeVault.setWithdrawalRoute()sets the recipient and withdrawal network in one call, for all fee vaults (#20982) L2ContractsManagergains adeploy()entrypoint, and L2 genesis now uses it to initialise predeploys (#21477)L2ContractsManagerupgrades now also coverConditionalDeployerandL2DevFeatureFlags, and assume the chain is already on Karst (#19847, #20313)L2DevFeatureFlags.isDevFeatureEnablednow reports the real bitmap for the retiredL2CMandCANNON_KONAbits, and always reportsSUPER_ROOT_GAMES_MIGRATIONas enabled (#21591, #21663, #21689)- The Lagoon upgrade bundle has higher gas limits for the
ConditionalDeployerdeployment and theL2ProxyAdminupgrade transaction (#20977, #20986, #21444)
Contract versions
| Contract | v7.0.0 | v8.0.0 |
|---|---|---|
BaseFeeVault
| 1.6.1 | 1.7.0 |
CrossL2Inbox
| 1.0.2 | 1.1.0 |
ETHLiquidity
| 1.1.0 | 1.1.1 |
L1FeeVault
| 1.6.1 | 1.7.0 |
L2ContractsManager
| 1.8.0 | 1.14.0 |
L2DevFeatureFlags
| 1.0.0 | 1.3.0 |
L2ProxyAdmin
| 1.0.0 | 1.1.0 |
L2ToL2CrossDomainMessenger
| 1.3.1 | 1.3.2 |
OPContractsManagerStandardValidator
| 2.9.1 | 3.3.0 |
OPContractsManagerV2
| 7.1.17 | 8.0.1 |
OperatorFeeVault
| 1.1.1 | 1.2.0 |
OptimismPortal2
| 5.6.1 | 5.8.0 |
ProtocolVersions
| 1.1.2 | — |
SequencerFeeVault
| 1.6.1 | 1.7.0 |
SuperFaultDisputeGame
| 0.7.2 | 0.8.0 |
SuperPermissionedDisputeGame
| 0.7.0 | 1.1.0 |
SuperchainConfig
| 2.4.2 | 2.4.3 |
SystemConfig
| 3.14.2 | 4.0.0 |
ZKDisputeGame
| 1.1.0 | 2.0.1 |
Full Changelog: op-contracts/v7.0.0...op-contracts/v8.0.0