diff --git a/docs/base-chain/specs/upgrades/overview.mdx b/docs/base-chain/specs/upgrades/overview.mdx
index 2753edf05..be62e5f23 100644
--- a/docs/base-chain/specs/upgrades/overview.mdx
+++ b/docs/base-chain/specs/upgrades/overview.mdx
@@ -1,18 +1,16 @@
---
title: "Upgrades"
-description: "Base evolves through named hardforks. Each hardfork introduces protocol changes, new features, or parameter updates that take effect at a specific activation block. This tab tracks what changed, when, and how to migrate."
+description: "Track Base network upgrades and their activation status across Base Sepolia and Mainnet."
+mode: "wide"
---
-## Base Upgrades
+import { UpgradesOverview } from "/snippets/UpgradesOverview.jsx";
-| Upgrade | Status | Activation |
-|----------|--------|------------|
-| [Denim](/base-chain/specs/upgrades/denim/200ms-blocks) | Planning | TBD |
-| [Cobalt](/base-chain/specs/upgrades/cobalt/overview) | Upcoming | Sep 2026 |
-| [Beryl](/base-chain/specs/upgrades/beryl/overview) | Live | Jun 25, 2026 |
-| [Azul](/base-chain/specs/upgrades/azul/overview) | Live | May 28, 2026 |
+Base evolves through named network upgrades. Each upgrade introduces protocol changes, new features, or parameter updates that take effect at a specific activation time. This tab tracks what changed, when, and how to migrate.
-## Upstream (OP Stack) Hardforks
+
+
+## Upstream OP Stack Hardforks
Base inherits upstream OP Stack hardforks. Each entry documents the changes Base adopted.
@@ -29,4 +27,4 @@ Base inherits upstream OP Stack hardforks. Each entry documents the changes Base
## Other Changes
-The [configuration changelog](/base-chain/network-information/configuration-changelog) tracks network parameter changes that don't belong to a specific hardfork.
+The [configuration changelog](/base-chain/network-information/configuration-changelog) tracks network parameter changes that don't belong to a specific upgrade.
diff --git a/docs/images/upgrades/azul-illo.svg b/docs/images/upgrades/azul-illo.svg
new file mode 100644
index 000000000..aa5960b2a
--- /dev/null
+++ b/docs/images/upgrades/azul-illo.svg
@@ -0,0 +1,23 @@
+
diff --git a/docs/images/upgrades/beryl-illo.svg b/docs/images/upgrades/beryl-illo.svg
new file mode 100644
index 000000000..4c704ae35
--- /dev/null
+++ b/docs/images/upgrades/beryl-illo.svg
@@ -0,0 +1,10 @@
+
diff --git a/docs/images/upgrades/cobalt-illo.svg b/docs/images/upgrades/cobalt-illo.svg
new file mode 100644
index 000000000..df62f51cd
--- /dev/null
+++ b/docs/images/upgrades/cobalt-illo.svg
@@ -0,0 +1,43 @@
+
diff --git a/docs/images/upgrades/denim-illo.svg b/docs/images/upgrades/denim-illo.svg
new file mode 100644
index 000000000..2513697cf
--- /dev/null
+++ b/docs/images/upgrades/denim-illo.svg
@@ -0,0 +1,31 @@
+
diff --git a/docs/llms-full.txt b/docs/llms-full.txt
index ef528684a..036430ac9 100644
--- a/docs/llms-full.txt
+++ b/docs/llms-full.txt
@@ -87,7 +87,7 @@ const client = createPublicClient({ chain: base, transport: http() })
- [SDKs & APIs](https://docs.base.org/get-started/sdks-and-apis): Choose the Base SDK, API, CLI, or MCP integration that matches what you are building.
## Base Chain
-- [Overview](https://docs.base.org/base-chain/overview): Base protocol specifications, core primitives, and network systems.
+- [Overview](https://docs.base.org/base-chain/overview): Base protocol specifications — tokens, bridging, transactions, consensus, execution, and proofs.
- [Overview](https://docs.base.org/base-chain/specs/overview): Technical specification of the Base Chain protocol, covering block derivation, execution, transaction propagation, and state verification.
- [Specification](https://docs.base.org/base-chain/specs/protocol/consensus/index): Specification of the Base rollup node, describing its components and role in L2 block derivation and consensus.
- [L2 Execution Engine](https://docs.base.org/base-chain/specs/protocol/execution/index): Specification of the L2 execution engine, detailing EIP-1559 parameters, fee vaults, Engine API usage, and execution layer behavior.
@@ -106,7 +106,7 @@ const client = createPublicClient({ chain: base, transport: http() })
- [Holocene](https://docs.base.org/base-chain/specs/upgrades/holocene/overview): Overview of the Holocene hardfork, introducing dynamic EIP-1559 parameters configurable via SystemConfig and stricter block derivation rules.
- [Isthmus](https://docs.base.org/base-chain/specs/upgrades/isthmus/overview): Overview of the Isthmus hardfork, incorporating Ethereum Pectra EIPs and introducing the operator fee mechanism for sequencer revenue.
- [Jovian](https://docs.base.org/base-chain/specs/upgrades/jovian/overview): Overview of the Jovian hardfork, introducing a configurable minimum base fee and a DA footprint gas scalar for improved fee market stability.
-- [Upgrades](https://docs.base.org/base-chain/specs/upgrades/overview): Base evolves through named hardforks. Each hardfork introduces protocol changes, new features, or parameter updates that take effect at a specific activation block. This tab tracks what changed, when, and how to migrate.
+- [Upgrades](https://docs.base.org/base-chain/specs/upgrades/overview): Track Base network upgrades and their activation status across Base Sepolia and Mainnet.
- [debug_traceBlockByHash](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceBlockByHash): Returns EVM execution traces for all transactions in a block by block hash.
- [debug_traceBlockByNumber](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceBlockByNumber): Returns EVM execution traces for all transactions in a block by block number.
- [debug_traceTransaction](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceTransaction): Returns the full EVM execution trace for a transaction. Requires a node with debug APIs enabled.
@@ -168,10 +168,10 @@ const client = createPublicClient({ chain: base, transport: http() })
- [Security Council for Base](https://docs.base.org/base-chain/security/security-council): This page outlines the purpose, goals, structure, and responsibilities of the Security Council for Base.
- [Native Account Abstraction](https://docs.base.org/base-chain/specs/native-account-abstraction): EIP-8130 reference for Base: vibenet chain details, client setup, transaction structure, account configuration, authenticators, and payers.
- [Batcher](https://docs.base.org/base-chain/specs/protocol/batcher): Specification of the batcher (batch submitter), the component responsible for posting L2 sequencer data to L1 for data availability.
-- [Standard Bridges](https://docs.base.org/base-chain/specs/protocol/bridging/bridges): Specification of the standard bridges enabling cross-domain ETH and ERC20 token transfers between L1 and L2 on Base.
-- [Deposits](https://docs.base.org/base-chain/specs/protocol/bridging/deposits): Specification of the deposit mechanism for Base, detailing how L1 transactions are converted into L2 deposit transactions.
+- [Standard Bridges](https://docs.base.org/base-chain/specs/protocol/bridging/bridges): Specification of the standard bridge contracts enabling cross-domain ETH and ERC-20 token transfers between L1 and L2 on Base.
+- [Deposits](https://docs.base.org/base-chain/specs/protocol/bridging/deposits): How deposits work on Base — from user experience to the protocol-level deposit transaction type and guaranteed gas market.
- [Cross Domain Messengers](https://docs.base.org/base-chain/specs/protocol/bridging/messengers): Specification of the cross-domain messenger contracts, providing a higher-level API for sending messages between L1 and L2 on Base.
-- [Withdrawals](https://docs.base.org/base-chain/specs/protocol/bridging/withdrawals): Specification of the withdrawal mechanism for Base, describing how L2 state is proven on L1 and funds are released from the bridge.
+- [Withdrawals](https://docs.base.org/base-chain/specs/protocol/bridging/withdrawals): How withdrawals work on Base — the standard 3-step flow, the 7-day challenge period, faster options, and the full protocol specification.
- [Derivation](https://docs.base.org/base-chain/specs/protocol/consensus/derivation): Specification of the L2 chain derivation pipeline, describing how L2 blocks are deterministically derived from L1 data and sequencer batches.
- [P2P](https://docs.base.org/base-chain/specs/protocol/consensus/p2p): Specification of the rollup node peer-to-peer network, covering node discovery, gossip protocol, and unsafe block propagation.
- [RPC](https://docs.base.org/base-chain/specs/protocol/consensus/rpc): Specification of the rollup node RPC interface, including the optimism_outputAtBlock method for retrieving L2 output roots.
@@ -314,7 +314,7 @@ const client = createPublicClient({ chain: base, transport: http() })
- [Dynamic Upgrades](https://docs.base.org/base-chain/specs/upgrades/cobalt/dynamic-upgrades): An Ethereum smart contract stores upgrade timestamps for Base nodes, allowing forks to activate at the scheduled time with no client restart.
- [Native Account Abstraction](https://docs.base.org/base-chain/specs/upgrades/cobalt/eip-8130): Build with native account abstraction on Base. EIP-8130 smart accounts send ordinary transactions, with no bundlers or relays.
- [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.
-- [200ms native blocks](https://docs.base.org/base-chain/specs/upgrades/denim/200ms-blocks): Specification for Denim's canonical 200ms blocks, including BaseTime, derivation, validation, and RPC behavior.
+- [200ms Native Blocks](https://docs.base.org/base-chain/specs/upgrades/denim/200ms-blocks): Specification for Denim's canonical 200ms blocks, including BaseTime, derivation, validation, and RPC behavior.
- [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.
- [Fjord L2 Chain Derivation Changes](https://docs.base.org/base-chain/specs/upgrades/fjord/derivation): Derivation changes in the Fjord upgrade, updating protocol parameters for max sequencer drift, channel bank size, and adding brotli compression support.
diff --git a/docs/llms.txt b/docs/llms.txt
index c242f7cf1..e6ab6a27b 100644
--- a/docs/llms.txt
+++ b/docs/llms.txt
@@ -21,7 +21,7 @@
- [SDKs & APIs](https://docs.base.org/get-started/sdks-and-apis): Choose the Base SDK, API, CLI, or MCP integration that matches what you are building.
## Base Chain
-- [Overview](https://docs.base.org/base-chain/overview): Base protocol specifications, core primitives, and network systems.
+- [Overview](https://docs.base.org/base-chain/overview): Base protocol specifications — tokens, bridging, transactions, consensus, execution, and proofs.
- [Overview](https://docs.base.org/base-chain/specs/overview): Technical specification of the Base Chain protocol, covering block derivation, execution, transaction propagation, and state verification.
- [Specification](https://docs.base.org/base-chain/specs/protocol/consensus/index): Specification of the Base rollup node, describing its components and role in L2 block derivation and consensus.
- [L2 Execution Engine](https://docs.base.org/base-chain/specs/protocol/execution/index): Specification of the L2 execution engine, detailing EIP-1559 parameters, fee vaults, Engine API usage, and execution layer behavior.
@@ -40,7 +40,7 @@
- [Holocene](https://docs.base.org/base-chain/specs/upgrades/holocene/overview): Overview of the Holocene hardfork, introducing dynamic EIP-1559 parameters configurable via SystemConfig and stricter block derivation rules.
- [Isthmus](https://docs.base.org/base-chain/specs/upgrades/isthmus/overview): Overview of the Isthmus hardfork, incorporating Ethereum Pectra EIPs and introducing the operator fee mechanism for sequencer revenue.
- [Jovian](https://docs.base.org/base-chain/specs/upgrades/jovian/overview): Overview of the Jovian hardfork, introducing a configurable minimum base fee and a DA footprint gas scalar for improved fee market stability.
-- [Upgrades](https://docs.base.org/base-chain/specs/upgrades/overview): Base evolves through named hardforks. Each hardfork introduces protocol changes, new features, or parameter updates that take effect at a specific activation block. This tab tracks what changed, when, and how to migrate.
+- [Upgrades](https://docs.base.org/base-chain/specs/upgrades/overview): Track Base network upgrades and their activation status across Base Sepolia and Mainnet.
- [debug_traceBlockByHash](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceBlockByHash): Returns EVM execution traces for all transactions in a block by block hash.
- [debug_traceBlockByNumber](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceBlockByNumber): Returns EVM execution traces for all transactions in a block by block number.
- [debug_traceTransaction](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceTransaction): Returns the full EVM execution trace for a transaction. Requires a node with debug APIs enabled.
@@ -102,10 +102,10 @@
- [Security Council for Base](https://docs.base.org/base-chain/security/security-council): This page outlines the purpose, goals, structure, and responsibilities of the Security Council for Base.
- [Native Account Abstraction](https://docs.base.org/base-chain/specs/native-account-abstraction): EIP-8130 reference for Base: vibenet chain details, client setup, transaction structure, account configuration, authenticators, and payers.
- [Batcher](https://docs.base.org/base-chain/specs/protocol/batcher): Specification of the batcher (batch submitter), the component responsible for posting L2 sequencer data to L1 for data availability.
-- [Standard Bridges](https://docs.base.org/base-chain/specs/protocol/bridging/bridges): Specification of the standard bridges enabling cross-domain ETH and ERC20 token transfers between L1 and L2 on Base.
-- [Deposits](https://docs.base.org/base-chain/specs/protocol/bridging/deposits): Specification of the deposit mechanism for Base, detailing how L1 transactions are converted into L2 deposit transactions.
+- [Standard Bridges](https://docs.base.org/base-chain/specs/protocol/bridging/bridges): Specification of the standard bridge contracts enabling cross-domain ETH and ERC-20 token transfers between L1 and L2 on Base.
+- [Deposits](https://docs.base.org/base-chain/specs/protocol/bridging/deposits): How deposits work on Base — from user experience to the protocol-level deposit transaction type and guaranteed gas market.
- [Cross Domain Messengers](https://docs.base.org/base-chain/specs/protocol/bridging/messengers): Specification of the cross-domain messenger contracts, providing a higher-level API for sending messages between L1 and L2 on Base.
-- [Withdrawals](https://docs.base.org/base-chain/specs/protocol/bridging/withdrawals): Specification of the withdrawal mechanism for Base, describing how L2 state is proven on L1 and funds are released from the bridge.
+- [Withdrawals](https://docs.base.org/base-chain/specs/protocol/bridging/withdrawals): How withdrawals work on Base — the standard 3-step flow, the 7-day challenge period, faster options, and the full protocol specification.
- [Derivation](https://docs.base.org/base-chain/specs/protocol/consensus/derivation): Specification of the L2 chain derivation pipeline, describing how L2 blocks are deterministically derived from L1 data and sequencer batches.
- [P2P](https://docs.base.org/base-chain/specs/protocol/consensus/p2p): Specification of the rollup node peer-to-peer network, covering node discovery, gossip protocol, and unsafe block propagation.
- [RPC](https://docs.base.org/base-chain/specs/protocol/consensus/rpc): Specification of the rollup node RPC interface, including the optimism_outputAtBlock method for retrieving L2 output roots.
@@ -248,7 +248,7 @@
- [Dynamic Upgrades](https://docs.base.org/base-chain/specs/upgrades/cobalt/dynamic-upgrades): An Ethereum smart contract stores upgrade timestamps for Base nodes, allowing forks to activate at the scheduled time with no client restart.
- [Native Account Abstraction](https://docs.base.org/base-chain/specs/upgrades/cobalt/eip-8130): Build with native account abstraction on Base. EIP-8130 smart accounts send ordinary transactions, with no bundlers or relays.
- [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.
-- [200ms native blocks](https://docs.base.org/base-chain/specs/upgrades/denim/200ms-blocks): Specification for Denim's canonical 200ms blocks, including BaseTime, derivation, validation, and RPC behavior.
+- [200ms Native Blocks](https://docs.base.org/base-chain/specs/upgrades/denim/200ms-blocks): Specification for Denim's canonical 200ms blocks, including BaseTime, derivation, validation, and RPC behavior.
- [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.
- [Fjord L2 Chain Derivation Changes](https://docs.base.org/base-chain/specs/upgrades/fjord/derivation): Derivation changes in the Fjord upgrade, updating protocol parameters for max sequencer drift, channel bank size, and adding brotli compression support.
diff --git a/docs/snippets/UpgradesOverview.jsx b/docs/snippets/UpgradesOverview.jsx
new file mode 100644
index 000000000..a9c307fd9
--- /dev/null
+++ b/docs/snippets/UpgradesOverview.jsx
@@ -0,0 +1,492 @@
+// Docs port of the Upgrades page at https://chain.base.org/upgrades
+// (source: github.com/base/ui, app/upgrades). Same data model — an upgrade
+// carries a per-network lifecycle that is either a confirmed timestamp or a
+// coarse estimate — so status is derived at render time and never goes stale.
+//
+// Two Mintlify constraints shape this file:
+// 1. Only the imported export is in scope, so data and helpers shared by the
+// two views live inside the component rather than at module level.
+// 2. Tailwind classes are rewritten to a `mint-` prefixed subset, and any
+// utility outside that subset silently no-ops (emerald and amber, for
+// instance). Styling therefore goes through the token +
+
+