From 78d5cf5a2f8edc876c5bd234c180358074306937 Mon Sep 17 00:00:00 2001 From: roethke Date: Mon, 11 May 2026 16:51:20 -0700 Subject: [PATCH] add activation timeline note and include mainnet release versions --- .../node-operators/base-v1-upgrade.mdx | 18 +++++++++++++----- .../specs/upgrades/azul/overview.mdx | 10 +++++++--- 2 files changed, 20 insertions(+), 8 deletions(-) diff --git a/docs/base-chain/node-operators/base-v1-upgrade.mdx b/docs/base-chain/node-operators/base-v1-upgrade.mdx index 56efdae6a..a555eff75 100644 --- a/docs/base-chain/node-operators/base-v1-upgrade.mdx +++ b/docs/base-chain/node-operators/base-v1-upgrade.mdx @@ -15,15 +15,23 @@ For full details on what's included, see the [Azul specification](/base-chain/sp | Network | Date | Timestamp | |---------|------|-----------| +| Mainnet | ~May 21, 2026 18:00 UTC | `1779386400` | | Sepolia | April 20, 2026 18:00 UTC | `1776708000` | -| Mainnet | May 21, 2026 18:00 UTC | `1779386400` | + + +The mainnet activation date is tentative and subject to change. Follow [@buildonbase](https://x.com/buildonbase) for the latest updates before upgrading. + ## Required Software -| Layer | Software | Version | -|-------|----------|---------| -| Execution (EL) | [`base-reth-node`](https://github.com/base/base/releases/tag/v0.7.0) | v0.7.0+ | -| Consensus (CL) | [`base-consensus`](https://github.com/base/base/releases/tag/v0.7.0) | v0.7.0+ | +| Layer | Software | Mainnet | Testnet | +|-------|----------|---------|-------------------| +| Execution (EL) | `base-reth-node` | v0.9.0+ *(coming soon)* | [v0.7.0+](https://github.com/base/base/releases/tag/v0.7.0) | +| Consensus (CL) | `base-consensus` | v0.9.0+ *(coming soon)* | [v0.7.0+](https://github.com/base/base/releases/tag/v0.7.0) | + + +Release links for v0.9.0 will be added once published to [base/base releases](https://github.com/base/base/releases). + 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. diff --git a/docs/base-chain/specs/upgrades/azul/overview.mdx b/docs/base-chain/specs/upgrades/azul/overview.mdx index f7106eb01..417c0a80b 100644 --- a/docs/base-chain/specs/upgrades/azul/overview.mdx +++ b/docs/base-chain/specs/upgrades/azul/overview.mdx @@ -16,11 +16,15 @@ Only `base-consensus` and `base-reth-node` will support the Base Azul hardfork. ## Activation Timestamps -| Network | Activation timestamp | -| --------- | -------------------------------------- | -| `mainnet` | `1779386400` (2026-05-21 18:00:00 UTC) | +| Network | Activation timestamp | +|---------|----------------------| +| `mainnet` | `1779386400` (~2026-05-21 18:00:00 UTC) | | `sepolia` | `1776708000` (2026-04-20 18:00:00 UTC) | + +The mainnet activation date is tentative and subject to change. Follow [@buildonbase](https://x.com/buildonbase) for the latest updates. + + ## Execution Layer - [EIP-7823: Upper-Bound MODEXP](/base-chain/specs/upgrades/azul/exec-engine#upper-bound-modexp)