From 3f8da3c4d1f77ff88636592a8abce75e5739ddf9 Mon Sep 17 00:00:00 2001 From: Matt Beuttenmuller Date: Fri, 17 Apr 2026 12:28:59 -0400 Subject: [PATCH] Fix: v1 refs changed to Azul --- docs/base-chain/node-operators/base-v1-upgrade.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/base-chain/node-operators/base-v1-upgrade.mdx b/docs/base-chain/node-operators/base-v1-upgrade.mdx index 2bd6444a2..0620dbb64 100644 --- a/docs/base-chain/node-operators/base-v1-upgrade.mdx +++ b/docs/base-chain/node-operators/base-v1-upgrade.mdx @@ -1,15 +1,15 @@ --- -title: "Base V1 Upgrade" -description: "Migrate your Base node to base-reth-node and base-consensus for V1." +title: "Base Azul Upgrade" +description: "Migrate your Base node to base-reth-node and base-consensus for Azul." --- -Base V1 is an upgrade that introduces Osaka features on Base and TEE/ZK proof systems. It requires migrating to Base-native clients. +Base Azul is an upgrade that introduces Osaka features on Base and TEE/ZK proof systems. It requires migrating to Base-native clients. -Only `base-reth-node` (EL) and `base-consensus` (CL) support V1. **Nodes running `op-node`, `op-geth`, `op-reth`, `nethermind`, or `kona` will not support the network upgrade and must be migrated before activation.** +Only `base-reth-node` (EL) and `base-consensus` (CL) support Azul. **Nodes running `op-node`, `op-geth`, `op-reth`, `nethermind`, or `kona` will not support the network upgrade and must be migrated before activation.** -For full details on what's included, see the [V1 specification](https://specs.base.org/upgrades/v1/overview). +For full details on what's included, see the [Azul specification](https://specs.base.org/upgrades/azul/overview). ## Activation Timeline