Skip to content

docs: update B20 activation status to reflect mainnet delay #1669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roethke merged 5 commits into from
Jun 26, 2026
+11 −2
Merged

docs: update B20 activation status to reflect mainnet delay #1669

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
184ac46
docs: update B20 activation status to reflect mainnet delay
roethke Jun 26, 2026
d76dcff
docs: use brand blue for B20 delay banner
roethke Jun 26, 2026
0070dc6
Update docs/docs.json
roethke Jun 26, 2026
a557082
docs: remove stale timing language from B20 activation callouts
roethke Jun 26, 2026
11425dc
docs: soften B20 delay messaging, emphasize Sepolia/Vibenet unaffected
roethke Jun 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/base-chain/specs/upgrades/beryl/b20.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<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.
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.
Comment thread
roethke marked this conversation as resolved.
Outdated
</Warning>

B20 supports two variants:
Expand Down
9 changes: 9 additions & 0 deletions docs/docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,15 @@
"$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)",
Comment thread
roethke marked this conversation as resolved.
Outdated
"type": "info",
"dismissible": true,
"color": {
"light": "#578BFA",
"dark": "#578BFA"
}
},
"colors": {
"primary": "#0000ff",
"light": "#578BFA",
Expand Down
2 changes: 1 addition & 1 deletion docs/get-started/launch-b20-token.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.** 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:
Comment thread
roethke marked this conversation as resolved.
Outdated
</Warning>

```bash Terminal theme={null}
Expand Down
Loading