Builders
Node Operators
Network Upgrades

Network Upgrade Overview

⚠️

Read this notice to prepare for Fjord.

This section has information on how to upgrade your Mainnet and Testnet nodes for new network upgrades. The network upgrade naming scheme after the Bedrock upgrade has a geology themed name based on the next letter in the english alphabet.

Activations

Network upgrades are activated by timestamps. Failing to upgrade your node before the timestamp will cause a chain divergence. You will need to resync your node to reconcile the chain. Optimistic activation times refer to times that are pending governance approval.

UpgradeGovernance ApprovalOP Mainnet Activations (opens in a new tab)OP Sepolia Activations (opens in a new tab)
Fjord (opens in a new tab)TBD (opens in a new tab)Optimistically Wed Jul 10 16:00:01 UTC 2024 (1720627201)Wed May 29 16:00:00 UTC 2024 (1716998400)
Ecotone (opens in a new tab)approved (opens in a new tab)Thu Mar 14 00:00:01 UTC 2024 (1710374401)Wed Feb 21 17:00:00 UTC 2024 (1708534800)
Delta (opens in a new tab)approved (opens in a new tab)Thu Feb 22 00:00:00 UTC 2024 (1708560000)Fri Dec 22 00:00:00 UTC 2023 (1703203200)
Canyon (opens in a new tab)approved (opens in a new tab)Thu Jan 11 17:00:01 UTC 2024 (1704992401)Tue Nov 14 17:00:00 UTC 2023 (1699981200)

Summary of Changes

These are the summary of each network upgrade changes order by the most recent activation. These are a reflection of the Superchain Upgrades Specifications (opens in a new tab)

Fjord (opens in a new tab)

The Fjord upgrade includes the RIP-7212 precompile, FastLZ gas pricing, Brotli channel compression, and several protocol parameter changes.

Ecotone (opens in a new tab)

The Ecotone upgrade contains the Dencun upgrade from L1, and adopts EIP-4844 blobs for data-availability.

Cancun (Execution Layer):

Deneb (Consensus Layer): not applicable to L2

Data Availability (DA) upgrade:

Delta (opens in a new tab)

The Delta upgrade consists of a single consensus-layer feature: Span Batches (opens in a new tab).

The Delta upgrade uses a L2 block-timestamp activation-rule, and is specified only in the rollup-node (delta_time).

Canyon (opens in a new tab)

The Canyon upgrade contains the Shapella upgrade from L1 and some minor protocol fixes.

The Canyon upgrade uses a L2 block-timestamp activation-rule, and is specified in both the rollup-node (canyon_time) and execution engine (config.canyonTime). Shanghai time in the execution engine should be set to the same time as the Canyon time.

Upgrade Process

Network upgrades follow this general process in which the features included in the upgrade are put into a release version cut from the develop branch and then the software is deployed on production networks.

"Baking" on a network means the node software has been deployed and is live. Engineers take this time to observe the behavior of the software on production networks.

Node Software Release Timeline

Devnet

  • Devnet Upgrade Notice Period is for core developers to upgrade the node software on an internal devnet prior to the activation timestamp.
  • Upgrade Activates on Devnet
  • Baking on Devnet

Testnet

  • Testnet Upgrade Notice Period is to allow testnet node operators to upgrade the node software on testnet prior to the activation timestamp.
  • Upgrade Activates on Testnet
  • Baking on Testnet

Mainnet

  • Governance Voting Review Period is when the Optimism Collective's governance system reviews proposals, including network upgrade proposals.
  • Governance Voting Period is when the Optimism Collective's governance system votes on proposals.
  • Veto Period is when the Citizens' House of the governance system can veto a protocol upgrade that has been approved by the Token House.
  • Cut Mainnet Release
  • Mainnet Upgrade Notice Period is to allow mainnet node operators to upgrade the node software on mainnet prior to the activation timestamp.
  • Upgrade Activated

More Information

TroubleshootingJSON-RPC API