diff --git a/docs/base-chain/specs/upgrades/beryl/b20.mdx b/docs/base-chain/specs/upgrades/beryl/b20.mdx
index f408d7fd1..52e63b224 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.
 
+<Warning>
+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.
+</Warning>
+
 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
 
 <Warning>
-**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:
 </Warning>
 
 ```bash Terminal theme={null}