From 184ac469fc438b46513b46a1e6deb0a50eba5026 Mon Sep 17 00:00:00 2001 From: roethke Date: Fri, 26 Jun 2026 10:38:51 -0700 Subject: [PATCH 1/5] docs: update B20 activation status to reflect mainnet delay Add site-wide banner and update callouts to reflect that B20 mainnet activation has been delayed pending incident resolution. Generated with Claude Code Co-Authored-By: Claude --- docs/base-chain/specs/upgrades/beryl/b20.mdx | 2 +- docs/docs.json | 5 +++++ docs/get-started/launch-b20-token.mdx | 2 +- 3 files changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx index 52e63b224..45d05c8b3 100644 --- a/docs/base-chain/specs/upgrades/beryl/b20.mdx +++ b/docs/base-chain/specs/upgrades/beryl/b20.mdx @@ -8,7 +8,7 @@ B20 is the Base ecosystem's own version of [ERC-20](https://eips.ethereum.org/EI To deploy your first B20 token, see the [Launch a B20 Token](/get-started/launch-b20-token) quickstart. -B20 activation on mainnet is anticipated on **June 26, 2026 at 6pm UTC**. The Activation Registry can take up to ~1 hour to be fully enabled. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy. +B20 activation on mainnet has been delayed — a revised date will be announced shortly. The Activation Registry can take up to ~1 hour to be fully enabled. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy. B20 supports two variants: diff --git a/docs/docs.json b/docs/docs.json index 10d4e9b06..eb16d4912 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -2,6 +2,11 @@ "$schema": "https://mintlify.com/docs.json", "theme": "aspen", "name": "Base Documentation", + "banner": { + "content": "B20 mainnet activation has been delayed due to a stability incident. A revised date will be announced shortly. [Check activation status](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled)", + "type": "warning", + "dismissible": true + }, "colors": { "primary": "#0000ff", "light": "#578BFA", diff --git a/docs/get-started/launch-b20-token.mdx b/docs/get-started/launch-b20-token.mdx index eee14b187..33bd89ddd 100644 --- a/docs/get-started/launch-b20-token.mdx +++ b/docs/get-started/launch-b20-token.mdx @@ -25,7 +25,7 @@ You need **Base's Foundry build** (`base-forge`, `base-cast`, [`base-anvil`](htt ## Verify the Activation Registry is enabled -**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet is anticipated on **June 26, 2026 at 6pm UTC**. After Beryl activates, the Activation Registry can take up to ~1 hour to be fully enabled. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding: +**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet has been delayed — a revised date will be announced shortly. After activation, the Activation Registry can take up to ~1 hour to be fully enabled. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding: ```bash Terminal theme={null} From d76dcfffff576a5430cbd37227e5c42769fa2cb8 Mon Sep 17 00:00:00 2001 From: roethke Date: Fri, 26 Jun 2026 10:42:58 -0700 Subject: [PATCH 2/5] docs: use brand blue for B20 delay banner Generated with Claude Code Co-Authored-By: Claude --- docs/docs.json | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/docs.json b/docs/docs.json index eb16d4912..bbfc32221 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -4,8 +4,12 @@ "name": "Base Documentation", "banner": { "content": "B20 mainnet activation has been delayed due to a stability incident. A revised date will be announced shortly. [Check activation status](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled)", - "type": "warning", - "dismissible": true + "type": "info", + "dismissible": true, + "color": { + "light": "#578BFA", + "dark": "#578BFA" + } }, "colors": { "primary": "#0000ff", From 0070dc61ef14e59456d7eabf92cbcd3e71352cf8 Mon Sep 17 00:00:00 2001 From: Jon Roethke Date: Fri, 26 Jun 2026 11:07:47 -0700 Subject: [PATCH 3/5] Update docs/docs.json Co-authored-by: Conner Swenberg --- docs/docs.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs.json b/docs/docs.json index bbfc32221..cd74bfe65 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -3,7 +3,7 @@ "theme": "aspen", "name": "Base Documentation", "banner": { - "content": "B20 mainnet activation has been delayed due to a stability incident. A revised date will be announced shortly. [Check activation status](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled)", + "content": "B20 mainnet activation has been delayed due to an unrelated stability incident. A revised date will be announced shortly. [Check activation status](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled)", "type": "info", "dismissible": true, "color": { From a557082d23ea8c20356753d93d02524b5d76edef Mon Sep 17 00:00:00 2001 From: roethke Date: Fri, 26 Jun 2026 11:08:42 -0700 Subject: [PATCH 4/5] docs: remove stale timing language from B20 activation callouts Generated with Claude Code Co-Authored-By: Claude --- docs/base-chain/specs/upgrades/beryl/b20.mdx | 2 +- docs/get-started/launch-b20-token.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx index 45d05c8b3..1ff036adc 100644 --- a/docs/base-chain/specs/upgrades/beryl/b20.mdx +++ b/docs/base-chain/specs/upgrades/beryl/b20.mdx @@ -8,7 +8,7 @@ B20 is the Base ecosystem's own version of [ERC-20](https://eips.ethereum.org/EI To deploy your first B20 token, see the [Launch a B20 Token](/get-started/launch-b20-token) quickstart. -B20 activation on mainnet has been delayed — a revised date will be announced shortly. The Activation Registry can take up to ~1 hour to be fully enabled. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy. +B20 activation on mainnet has been delayed — a revised date will be announced shortly. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy. B20 supports two variants: diff --git a/docs/get-started/launch-b20-token.mdx b/docs/get-started/launch-b20-token.mdx index 33bd89ddd..1fdbe19d2 100644 --- a/docs/get-started/launch-b20-token.mdx +++ b/docs/get-started/launch-b20-token.mdx @@ -25,7 +25,7 @@ You need **Base's Foundry build** (`base-forge`, `base-cast`, [`base-anvil`](htt ## Verify the Activation Registry is enabled -**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet has been delayed — a revised date will be announced shortly. After activation, the Activation Registry can take up to ~1 hour to be fully enabled. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding: +**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet has been delayed — a revised date will be announced shortly. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding: ```bash Terminal theme={null} From 11425dc477b98106fb1aabe8d1a8184a1254396d Mon Sep 17 00:00:00 2001 From: roethke Date: Fri, 26 Jun 2026 11:18:57 -0700 Subject: [PATCH 5/5] docs: soften B20 delay messaging, emphasize Sepolia/Vibenet unaffected Generated with Claude Code Co-Authored-By: Claude --- docs/base-chain/specs/upgrades/beryl/b20.mdx | 2 +- docs/get-started/launch-b20-token.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx index 1ff036adc..05497b181 100644 --- a/docs/base-chain/specs/upgrades/beryl/b20.mdx +++ b/docs/base-chain/specs/upgrades/beryl/b20.mdx @@ -8,7 +8,7 @@ B20 is the Base ecosystem's own version of [ERC-20](https://eips.ethereum.org/EI To deploy your first B20 token, see the [Launch a B20 Token](/get-started/launch-b20-token) quickstart. -B20 activation on mainnet has been delayed — a revised date will be announced shortly. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy. +B20 mainnet activation has been delayed due to an unrelated stability incident. We're pushing back the Activation Registry enablement to ensure a smooth rollout — Sepolia and Vibenet remain on track. We'll share a revised date shortly. [Verify the Activation Registry is enabled](/get-started/launch-b20-token#verify-the-activation-registry-is-enabled) before attempting to deploy. B20 supports two variants: diff --git a/docs/get-started/launch-b20-token.mdx b/docs/get-started/launch-b20-token.mdx index 1fdbe19d2..85055c95d 100644 --- a/docs/get-started/launch-b20-token.mdx +++ b/docs/get-started/launch-b20-token.mdx @@ -25,7 +25,7 @@ You need **Base's Foundry build** (`base-forge`, `base-cast`, [`base-anvil`](htt ## Verify the Activation Registry is enabled -**The Activation Registry must be enabled before you can deploy.** B20 activation on mainnet has been delayed — a revised date will be announced shortly. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding: +**B20 mainnet activation has been delayed due to an unrelated stability incident.** We're pushing back the Activation Registry enablement to ensure a smooth rollout — Sepolia and Vibenet remain on track. We'll share a revised date shortly. Attempting to deploy before it's ready will revert with `FeatureNotActivated`. Run the check for the variant you plan to deploy and confirm it returns `true` before proceeding: ```bash Terminal theme={null}