Skip to content
Crypto.world

The Ledger

Upgrade 21 Is the Set of L1 Contract Changes OP Stack Chains Need Before Interop Ships

Upgrade 21 is the set of L1 contract changes OP Stack chains need in place before interop ships. The proposal would give every chain an ETHLockbox and one chain-specific pause identifier, change withdrawal handling and add validator checks for the new lockbox and pause configuration.

Upgrade 21 Is the Set of L1 Contract Changes OP Stack Chains Need Before Interop Ships

Upgrade 21 is the set of L1 contract changes OP Stack chains need in place before interop ships. The proposal would give every chain an ETHLockbox and make it the only identifier for chain-specific pauses. It combines that shift with changes to withdrawal handling and validator checks for the new lockbox and pause configuration.

Source gov.optimism.io

Upgrade 21 is an L1 smart contract upgrade shipped in op-contracts/v9.0.0. It has no hardfork or activation timestamp: every change is applied through a signed superchain-ops execution on L1. Andrea Federici, a Senior Solutions Engineer at OP Labs, prepared the proposal with Matthew Cruz from the OP Labs team.

Upgrade 21 enables an ETHLockbox on every chain

Since Upgrade 16a, new chains have been deployed without a lockbox, and upgrades have not changed a chain’s lockbox status. Standard chains are split between two custody models, with each having its own pause identifier: the ETHLockbox or OptimismPortal.

Under the proposal, chains whose ETH is still in the OptimismPortal would move it into the lockbox during the upgrade transaction; chains already using a lockbox would not change. Custom gas token chains would receive a lockbox but keep custody in the portal. The proposal says the common lockbox and pause identifier would leave one custody model and one pause identifier for Guardian tooling, monitoring and integrations, and provide the starting point for the interop migration, which requires a lockbox on every chain in the set.

Failed messenger relays stay retryable

Upgrade 21 changes OptimismPortal2 so a messenger withdrawal reverts if its relay into L1CrossDomainMessenger fails. That leaves the withdrawal retryable instead of finalizing it without a recorded outcome. The change is paired with a larger gas reserve for recording whether a relay succeeded or failed.

The proposal raises LOCAL_RELAY_RESERVED_GAS from 40,000 to 135,000, with a 15,000 gas-check buffer. It also separates relay gas constants into LOCAL_* and REMOTE_* values and copies the messenger’s payload into memory before its gas check. Upgrade 21 permits anyone to delete a withdrawal proof for a dispute game resolved in favor of the challenger or blacklisted; proofs on valid games would be unaffected.

Upgrade 21 specifies updates for integrations and chain operators

Ordinary L2 contracts and transactions are not affected, and users and node operators need take no action. Integrations that finalize withdrawals must treat the OptimismPortal_L1CDMCallFailed revert as retryable with more gas. Integrations that read relay gas constants would need to account for the LOCAL_* and REMOTE_* names; RELAY_* getters would remain as aliases of REMOTE_*.

Chain operators must point Guardian pause tooling and monitoring at each chain’s ETHLockbox and update op-challenger to v1.11.0. On a chain without a lockbox, the upgrade reverts while the chain is paused under its OptimismPortal identifier, so an active pause is not silently dropped when the identifier moves to the lockbox. All other chains using the standard L1 bridge contracts must already be on Upgrade 20 (op-contracts/v8.0.0) and upgrade with the OPCM instance.

The proposal outcome will determine Optimism Governed chain upgrades

The outcome of this governance proposal will determine how Optimism Governed chains are upgraded. Its Ethereum Mainnet calldata covers OP Mainnet, Ink, Soneium and Unichain, with the shared SuperchainConfig upgrade followed by upgrades for those four chains. The listed OPCM address is 0x2d91e6f2bcf6cd1df90e1faf9714e18705ea331f, version 9.0.3.

The proposal identifies that OPCM as deployed from the op-contracts/v9.0.0-rc.1 tag on October 30, 2026, and says the address could change if the final release redeploys it. The upgrade re-registers the SUPER_CANNON_KONA game on each permissionless chain with the kona-client/v1.9.0 cannon64-kona-interop prestate. The proposal specifies no hardfork and no chain configuration change.

Sources

  1. Original source Optimism Governance Forum gov.optimism.io

Related stories

Explore

More articles