Skip to main content
Azul activated on mainnet on May 28, 2026 18:00 UTC (1779991200). See the required software versions and full activation timestamps on the Azul overview.
Only base-reth-node (EL) and base-consensus (CL) support Azul. Nodes running op-node, op-geth, op-reth, nethermind, or kona must be migrated using the instructions below.
Both clients are available from the base/node repository, where most configuration is preconfigured and can be overridden via environment variables. See the .env.mainnet and .env.sepolia files for the full list of configurable options.If you build from the base/base repository directly, you will need to update your base-consensus configuration to use the new BASE_NODE_* environment variables. For base-reth-node, you can continue to use all existing Reth tooling and configuration as before.

​
Migrating Execution Layer

​
Migrating from OP Reth

If you are already running OP Reth via base/node, update to the latest version and your node will automatically use base-reth-node. Your existing ./reth-data directory is fully compatible — no re-sync or snapshot restore is needed.
  1. Stop your node:
  2. Update to the latest version of base/node:
  3. Start your node:
  4. Verify client version: web3_clientVersion should include base in the version string (e.g. reth/v1.11.3-.../base/v0.9.0)

​
Migrating from another client

op-geth and nethermind are no longer supported. You will need to start fresh with base-reth-node.
  1. Stop your node:
  2. Update to the latest version of base/node:
  3. Remove your old data directory (e.g. ./geth-data or ./nethermind-data).
  4. Edit the .env.mainnet or .env.sepolia file to match your preferences.
  5. Bootstrap from a Reth snapshot to avoid a full sync.
  6. Start your node:

​
Migrating Consensus Layer

Replace op-node with base-consensus by updating your environment variables.
  1. Set USE_BASE_CONSENSUS=true in your .env file.
  2. Update your .env file with the new BASE_NODE_* environment variables (see tables below).
  3. Restart your node:
  4. Verify:
    • Check consensus logs: docker compose logs -f node
    • Confirm sync status: optimism_syncStatus continues to work

​
Environment Variable Mapping

If you use base/node, most variables are already set in .env.mainnet and .env.sepolia. If you build from base/base, use the table below to map your op-node environment variables to base-consensus. Most are optional. Run base-consensus node --help for the full list.

​
FAQ

  • Do I need to re-sync? Not if you are already running OP Reth. Existing data is compatible.
  • What if I’m on op-geth or nethermind? You need to switch to base-reth-node. Use a Reth snapshot to bootstrap.
  • Do OP namespace RPCs still work? Yes, all existing RPCs are supported.