Welcome to the next crypto level
← Nexorena

Bitcoin

Optimism proposes Upgrade 21 to prepare interoperability and strengthen withdrawals

The proposal published November 4 concerns Ethereum contracts used by several OP Stack networks. It triggers neither a Layer 2 hard fork nor immediate interoperability, and its timetable remains conditional.

Nexorena Editorial Team

Optimism proposes Upgrade 21 to prepare interoperability and strengthen withdrawals

Ethereum contracts without a universal activation time

A proposal published November 4 on Optimism’s governance forum seeks approval for Upgrade 21. Prepared by OP Labs engineers, it concerns Layer 1 contracts used by OP Stack networks. The operation targets OP Mainnet, Ink, Soneium and Unichain among others. It is not a hard fork of their Layer 2 networks: each contract set must be upgraded through an Ethereum transaction, without a single activation time to configure across every node.

The project aims to standardize ETH custody and the identifier used to pause a bridge around a component called ETHLockbox. Chains already using it keep their funds in the same place; others would move the relevant balance during the upgrade, with an exception for chains using a custom gas token. The networks directly covered by the proposal already have this component. Readers should therefore not infer that identical fund transfers will occur everywhere.

Withdrawals need a verifiable outcome

Another change concerns withdrawals passing through the cross-layer messaging system. If a call cannot correctly record its outcome, the contract should revert that attempt rather than treat the withdrawal as permanently finalized in failure. The aim is to preserve the ability to retry. The project also increases the gas reserved for recording that outcome. This logic distinguishes a temporary operation failure from losing the ability to resume it.

Anyone would also be able to clean up certain withdrawal proofs that have become unusable. Proofs based on valid dispute games and withdrawals already in progress remain valid under the proposal. No action is announced for ordinary users. Relevant operators and integrators, however, need to adapt monitoring tools, balance references and pause procedures. Documentation also provides for an update to challenger software, without presenting this as a mandatory new version of every network component.

Timing depends on governance and testing

Upgrade 21 prepares elements needed for interoperability between chains but does not activate it. Documentation explicitly separates this step from a later migration; its operating runbook is not yet cleared for production chains. This distinction avoids confusing the availability of preparatory contracts with live interoperable transfers. Sharing certain functions changes technical dependencies and requires specific checks before an available service can be announced.

The published plan targets Sepolia testing on November 9, the end of the veto period on November 11 and mainnet execution on November 16. These dates depend on governance approval and a satisfactory seven-day observation period. Authors say an audit covered the changes, but fix review is ongoing and the report must be published before mainnet execution. Problems during these checks would delay it: the proposal is preparation, not evidence of a completed upgrade.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena