Intro

This is the upgrade guide to the Canyon network upgrade and synced protocol-version upgrades.

<aside> 🚨 The Canyon mainnet network upgrade is scheduled for January 11th at 17:00:00 UTC 2024.

</aside>

About the ProtocolVersions contract

You must upgrade your nodes to the following versions prior to January 11 2024

• Upgrade your op-node to version: v1.3.2. Available as this GitHub release.
• Upgrade your op-geth to version v1.101304.2. Available as this GitHub release.

Recommended configuration

Note: this configuration path uses the protocol-version functionalities described above.

1. Setting the network flags:

   • On op-geth specify --op-network with a pre-configured OP Stack network.
   • On op-node specify --network with a pre-configured OP Stack network.

   The following are the supported options:

   options: base-goerli, base-mainnet, base-sepolia, op-goerli, op-labs-chaosnet-0-goerli-dev-0, op-labs-devnet-0-goerli-dev-0, op-mainnet, op-sepolia, pgn-mainnet, pgn-sepolia, zora-goerli, zora-mainnet
   

2. Loading and reporting protocol versions from the Superchain:

   • On op-node set --rollup.load-protocol-versions to true.

3. Optionally, enabling halting your node on breaking changes:

   1. On op-geth specify --rollup.halt=major
   • On op-node specify --rollup.halt=major

   This does not shut down your node, but stops syncing once it detects an incompatible protocol version.

   Your node defaults to not halting, but we recommend setting this to at least major so your node does not produce diverging state.

Example node configuration values

Verifying your configuration on Mainnet

You can verify your node is configured correctly with the following:

• Both op-node and op-geth log their configuration at startup