add beryl versions, update azul pages for consistency

docs/base-chain/specs/upgrades/azul/node-upgrade.mdx

@@ -4,16 +4,11 @@ sidebarTitle: "Node Upgrade Guide"
 description: "Migrate your Base node to base-reth-node and base-consensus for Azul."
 ---
 
-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.**
+<Check>
+Azul activated on mainnet on **May 28, 2026 18:00 UTC** (`1779991200`). See the [required software versions](/base-chain/specs/upgrades/azul/overview#required-software) and [full activation timestamps](/base-chain/specs/upgrades/azul/overview#activation-timestamps) on the Azul overview.
+</Check>
 
-Azul activated on mainnet on **May 28, 2026 18:00 UTC** (`1779991200`). See the [Azul overview](/base-chain/specs/upgrades/azul/overview#activation-timestamps) for the full activation timestamp table.
-
-## Required Software
-
-| Layer | Software | Mainnet | Testnet |
-|-------|----------|---------|-------------------|
-| Execution (EL) | `base-reth-node` | [v0.9.0+](https://github.com/base/base/releases/tag/v0.9.0) | [v0.7.0+](https://github.com/base/base/releases/tag/v0.7.0) |
-| Consensus (CL) | `base-consensus` | [v0.9.0+](https://github.com/base/base/releases/tag/v0.9.0) | [v0.7.0+](https://github.com/base/base/releases/tag/v0.7.0) |
+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.
 
 <Note>
 Both clients are available from the [base/node](https://github.com/base/node/releases) 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.

docs/base-chain/specs/upgrades/azul/overview.mdx

@@ -21,6 +21,16 @@ Only `base-consensus` and `base-reth-node` will support the Base Azul hardfork.
 | `mainnet` | `1779991200` | 2026-05-28 18:00:00 UTC |
 | `sepolia` | `1776708000` | 2026-04-20 18:00:00 UTC |
 
+## Required Software
+
+| Layer | Software | Mainnet | Sepolia |
+|-------|----------|---------|---------|
+| Execution (EL) | `base-reth-node` | [v0.9.0+](https://github.com/base/base/releases/tag/v0.9.0) | [v0.7.0+](https://github.com/base/base/releases/tag/v0.7.0) |
+| Consensus (CL) | `base-consensus` | [v0.9.0+](https://github.com/base/base/releases/tag/v0.9.0) | [v0.7.0+](https://github.com/base/base/releases/tag/v0.7.0) |
+| - | `base/node` | [v0.16.0+](https://github.com/base/node/releases/tag/v0.16.0) | [v0.15.0+](https://github.com/base/node/releases/tag/v0.15.0) |
+
+See the [Node Upgrade Guide](/base-chain/specs/upgrades/azul/node-upgrade) for full migration instructions.
+
 ## Execution Layer
 
 - [EIP-7823: Upper-Bound MODEXP](/base-chain/specs/upgrades/azul/exec-engine#upper-bound-modexp)

docs/base-chain/specs/upgrades/beryl/b20.mdx

@@ -237,19 +237,3 @@ The fixed-decimals, fiat-backed carveout. Decimals are hard-wired to `6` and are
 
 Adds `currency()`, which returns an ISO-style currency code string (e.g. `"USD"`, `"EUR"`). The code is set once at creation via `B20StablecoinCreateParams.currency`, restricted to characters `A`-`Z` only. It is self-declared and not verified against any external registry.
 
-## Roadmap
-
-Because B20 tokens execute in Rust outside the EVM, the node has advanced control over their behavior. The following capabilities are planned for future upgrades:
-
-### Frontier Features
-
-- **Pay transaction fees with B20** - enables transacting using only a custom asset, with no ETH required.
-- **Virtual addresses** - create unique deposit addresses that forward to a shared account.
-- **Indexed data** - Base Node RPCs serve aggregated balances, transfer history, and token metadata directly, with no external indexer required.
-
-### Performance Optimizations
-
-- **Lower fees** - approximately 50% cheaper transfers compared to ERC-20 contracts.
-- **Higher throughput** - approximately 2× the transfers per block compared to ERC-20 contracts.
-
-Further optimizations are planned for trading and payments use cases specifically.

docs/base-chain/specs/upgrades/beryl/overview.mdx

@@ -7,7 +7,7 @@ description: "Overview of the Beryl hardfork, introducing the B20 native token s
 
 - Introduce [B20](/base-chain/specs/upgrades/beryl/b20): Base's native token standard for stablecoin, real-world asset (RWA), and long-tail token issuers
 - Reduce the single-proof withdrawal finalization period from 7 days to 5 days for increased capital efficiency
-- [Reth V2](/base-chain/specs/upgrades/beryl/reth-v2): up to 50% disk reduction and a rewritten state root pipeline delivering +33% throughput
+- Reth V2: up to 50% disk reduction and a rewritten state root pipeline delivering +33% throughput
 
 ## Activation Timestamps
 
@@ -16,8 +16,16 @@ description: "Overview of the Beryl hardfork, introducing the B20 native token s
 | `mainnet` | `1782410400` | 2026-06-25 18:00:00 UTC |
 | `sepolia` | `1781805600` | 2026-06-18 18:00:00 UTC |
 
+## Required Software
+
+| Layer | Software | Mainnet | Sepolia |
+|-------|----------|---------|---------|
+| Execution (EL) | `base-reth-node` | TBA | [v1.1.0+](https://github.com/base/base/releases/tag/v1.1.0) |
+| Consensus (CL) | `base-consensus` | TBA | [v1.1.0+](https://github.com/base/base/releases/tag/v1.1.0) |
+| - | `base/node` | TBA | [v1.1.0+](https://github.com/base/node/releases/tag/v1.1.0) |
+
 <Warning>
-Action required before activation. Upgrade to the latest `base-reth-node` release on both Sepolia and Mainnet before their respective activation dates above. Required software versions will be published here ahead of activation.
+Action required before activation. Upgrade to the required version before each network's activation date above.
 </Warning>
 
 ## B20: Native Token Standard
@@ -38,8 +46,3 @@ The single-proof dispute game finalization window is reduced from 7 days to 5 da
 
 Shortening the single-proof window frees capital for fast-bridge liquidity providers sooner, reducing fees and improving reliability for users who bridge through third-party partners.
 
-## Reth V2
-
-- [Reth V2 Overview](/base-chain/specs/upgrades/beryl/reth-v2)
-- [Storage V2](/base-chain/specs/upgrades/beryl/reth-v2#storage-v2)
-- [State Root Computation](/base-chain/specs/upgrades/beryl/reth-v2#state-root-computation)

docs/docs.json

@@ -259,8 +259,7 @@
                     "group": "Beryl",
                     "pages": [
                       "base-chain/specs/upgrades/beryl/overview",
-                      "base-chain/specs/upgrades/beryl/b20",
-                      "base-chain/specs/upgrades/beryl/reth-v2"
+                      "base-chain/specs/upgrades/beryl/b20"
                     ]
                   },
                   {

docs/llms-full.txt

@@ -209,7 +209,6 @@ const client = createPublicClient({ chain: base, transport: http() })
 - [Node Upgrade Guide](https://docs.base.org/base-chain/specs/upgrades/azul/node-upgrade): Migrate your Base node to base-reth-node and base-consensus for Azul.
 - [Proof System](https://docs.base.org/base-chain/specs/upgrades/azul/proofs): Specification of the Azul multi-proof system, replacing the single output proposer with an AggregateVerifier contract for L2 checkpoint security.
 - [B20 Native Token Standard](https://docs.base.org/base-chain/specs/upgrades/beryl/b20): B20 is Base's native token standard - designed for stablecoin issuers, real-world asset (RWA) and equity issuers, and long-tail token creators.
-- [Reth V2](https://docs.base.org/base-chain/specs/upgrades/beryl/reth-v2): Reth V2 reduces node disk usage by up to 50% and delivers a rewritten state root pipeline with significantly higher throughput and lower block-execution latency.
 - [Span-batches](https://docs.base.org/base-chain/specs/upgrades/delta/span-batches): Specification of span batches introduced in Delta, a new batch format that compresses sequences of L2 blocks for more efficient L1 data posting.
 - [Derivation](https://docs.base.org/base-chain/specs/upgrades/ecotone/derivation): Derivation changes in the Ecotone upgrade, extending the retrieval stage to support EIP-4844 blobs as an additional data availability source.
 - [Ecotone L1 Attributes](https://docs.base.org/base-chain/specs/upgrades/ecotone/l1-attributes): L1 attributes transaction changes in the Ecotone upgrade, updating calldata format to support the new blob-based fee calculation model.

docs/llms.txt

@@ -121,7 +121,6 @@
 - [Node Upgrade Guide](https://docs.base.org/base-chain/specs/upgrades/azul/node-upgrade): Migrate your Base node to base-reth-node and base-consensus for Azul.
 - [Proof System](https://docs.base.org/base-chain/specs/upgrades/azul/proofs): Specification of the Azul multi-proof system, replacing the single output proposer with an AggregateVerifier contract for L2 checkpoint security.
 - [B20 Native Token Standard](https://docs.base.org/base-chain/specs/upgrades/beryl/b20): B20 is Base's native token standard - designed for stablecoin issuers, real-world asset (RWA) and equity issuers, and long-tail token creators.
-- [Reth V2](https://docs.base.org/base-chain/specs/upgrades/beryl/reth-v2): Reth V2 reduces node disk usage by up to 50% and delivers a rewritten state root pipeline with significantly higher throughput and lower block-execution latency.
 - [Span-batches](https://docs.base.org/base-chain/specs/upgrades/delta/span-batches): Specification of span batches introduced in Delta, a new batch format that compresses sequences of L2 blocks for more efficient L1 data posting.
 - [Derivation](https://docs.base.org/base-chain/specs/upgrades/ecotone/derivation): Derivation changes in the Ecotone upgrade, extending the retrieval stage to support EIP-4844 blobs as an additional data availability source.
 - [Ecotone L1 Attributes](https://docs.base.org/base-chain/specs/upgrades/ecotone/l1-attributes): L1 attributes transaction changes in the Ecotone upgrade, updating calldata format to support the new blob-based fee calculation model.