From 9933be4f10b5e672496c7f244ea6496b3339cd62 Mon Sep 17 00:00:00 2001 From: roethke Date: Thu, 25 Jun 2026 14:14:11 -0700 Subject: [PATCH 1/2] update b20 activation timeline, add callout --- docs/base-chain/specs/upgrades/beryl/b20.mdx | 4 ++++ docs/get-started/launch-b20-token.mdx | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx index f408d7fd1..bb3c1b931 100644 --- a/docs/base-chain/specs/upgrades/beryl/b20.mdx +++ b/docs/base-chain/specs/upgrades/beryl/b20.mdx @@ -7,6 +7,10 @@ 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 after Beryl activates. [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: | Variant | Decimals | Additional Features | diff --git a/docs/get-started/launch-b20-token.mdx b/docs/get-started/launch-b20-token.mdx index 88af2d713..eee14b187 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.** After the Beryl hardfork 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 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: ```bash Terminal theme={null} From 7dc4c80698dd877b236db39f16e7e26f4314e1c7 Mon Sep 17 00:00:00 2001 From: roethke Date: Thu, 25 Jun 2026 14:16:49 -0700 Subject: [PATCH 2/2] remove outdated language --- docs/base-chain/specs/upgrades/beryl/b20.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx index bb3c1b931..52e63b224 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 after Beryl activates. [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 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 supports two variants: