Layer-2 networks ship upgrades constantly, but Base's June 25 hardfork bundles three changes that touch issuers, bridge users, and node operators at once. The headline most traders will see is a shorter withdrawal window, though that may be the least consequential item in the package.
What Beryl actually changes on June 25
Beryl is a Base mainnet hardfork (a coordinated state transition on the existing chain, not a new network) scheduled for June 25, 2026 at 18:00:00 UTC (Unix timestamp 1782410400) . It is Base's second independent named upgrade, following Azul, and three changes ship together in a single activation.
Those three changes are :
- B20 native token standard: a chain-native token format built as Rust precompiles, aimed at stablecoin, real-world-asset, and long-tail issuers.
- Faster withdrawals: the single-proof Base→Ethereum finalization window drops from 7 days to 5 days.
- Reth V2 / Storage V2: an execution-client overhaul Base says cuts disk usage up to 50% and lifts throughput roughly 33%.
The upgrade already activated on the Base Sepolia testnet on June 18, 2026 at 18:00:00 UTC, putting mainnet exactly one week behind a proven testnet run . The required client release, base/base v1.1.1, was published the same day with Beryl mainnet support .
Node operators carry the only hard deadline. Mainnet requires base-reth-node v1.1.1+ and base-consensus v1.1.1+ before activation; operators who fail to upgrade by June 25 at 18:00:00 UTC risk being forked off the canonical chain . Regular users and traders need take no action for the transition itself.
B20: why a Rust precompile token standard matters for issuers
B20 is Base's native token standard, built as chain-native Rust precompiles that run inside the node software rather than as EVM bytecode deployed by each issuer . That single design choice is the point: token logic bypasses normal contract execution overhead, so transfers and mints run cheaper and faster. For issuers, it reframes a token from "a contract you write and audit" into "a configuration you call."
B20 implements the ERC-20 specification with selector parity . Existing wallets, exchanges, explorers, and indexers treat a B20 token as an ordinary ERC-20 with no integration work, a drop-in for tooling that already exists. The execution layer changes; the developer-facing interface does not.
Base aims this squarely at teams that currently rebuild compliance plumbing themselves: stablecoin issuers, real-world-asset and equity issuers, and long-tail token creators . The launch toolkit ships features most projects code from scratch:
- Role-based access control: separate
MINT_ROLE,BURN_ROLE, andPAUSE_ROLEpermissions . - Granular transfer policies via allowlist/blocklist, plus freeze-and-seize through
burnBlocked. - ERC-2612 permits (signature-based approvals), optional supply caps, and
bytes32memo fields for payment IDs and compliance tracking.
Two variants ship with Beryl :
| Variant | Decimals | Distinct features |
|---|---|---|
| Asset | Configurable 6-18 | Rebasing multiplier, batch minting, onchain announcements, issuer metadata |
| Stablecoin | Fixed 6 | Self-declared fiat currency code (e.g., USD/EUR), not verified against an external registry |
All tokens are created through a singleton B20Factory precompile at 0xB20f000000000000000000000000000000000000 using createB20(variant, salt, params, initCalls), where the salt parameter enables deterministic addressing . Base's quickstart deploys an Asset token, grants a mint role, sets a cap, and mints supply, all without writing or deploying a token contract .
"B20 implements the ERC-20 specification with selector parity, so existing tooling can treat B20 tokens as ERC-20s." Base describes the standard as an issuance template with built-in compliance and administration features (source: Base).
One clarification on expectations: the headline efficiency gains (roughly 50% cheaper transfers and doubled throughput) are tied to Cobalt, targeted for September 2026, not Beryl itself . Beryl delivers the standard and its compliance scaffolding; the deeper cost reductions arrive later, and Base flags such forward-looking items as subject to change.
Withdrawals, node performance, and what traders actually feel
For most traders, Beryl's tangible win is a shorter exit window. The standard single-proof withdrawal delay for canonical Base→Ethereum bridge exits drops from 7 days to 5 days . That two-day cut applies automatically once the upgrade activates. No action is required from users moving funds through the native bridge.
The dual-proof fast path introduced with Azul, where a TEE proof and a ZK proof agree, stays at 1 day and is unchanged by Beryl . Base frames the shorter delay as a product of its multiproof model: finalization now requires a positive proof, so the residual wait is mainly the time to detect and disable a faulty prover before settlement.
"Finalization now requires a positive proof, so the remaining delay is principally the time needed to detect and disable a faulty prover before finalization." (Base, on the Beryl withdrawal change; source: Base)
The group that gains most is fast-bridge liquidity providers. When the canonical exit shortens by two days, capital fronted on third-party bridges recycles sooner, which tightens LP economics and can improve quoted rates for everyone using those routes .
Under the hood, Beryl also ships Reth V2 with a rewritten state-root pipeline and new storage layout. Base docs cite up to 50% lower disk usage and roughly 33% higher throughput; mainnet operators must run base-reth-node v1.1.1+ and base-consensus v1.1.1+ before activation . This is invisible to end users but matters to RPC providers and indexers carrying Base load.
What is not in Beryl is worth pinning down. Base lists these for Cobalt, targeted September 2026 :
- Paying gas in a B20 token
- Roughly 50% cheaper transfers and doubled transfer throughput
- Native account abstraction
- A unified node binary
So the immediate trader-facing payoff is narrow but real: faster, cheaper exits and a leaner node stack. The deeper efficiency gains stay on the roadmap, and Base flags such forward-looking items as subject to change.
What to watch after June 25
The activation date is fixed, but the signals worth tracking arrive afterward. Beryl is the foundation; the next few weeks tell you whether issuers, bridges, and Base's own roadmap deliver on it. Three signals are worth watching once the hardfork activates at 18:00:00 UTC on June 25, 2026 .
- First B20 issuers. Watch which stablecoin and real-world-asset projects announce B20 deployments in the days after activation. Early adopters are the clearest read on institutional appetite for the built-in compliance toolkit: role-based access, transfer policies, and freeze-and-seize controls .
- Native Base token speculation. One report cited prediction-market odds of about 28.5% for a Base network token by December 31, 2026, down from roughly 34% . That is a third-party data point, not confirmation. Base has announced no network token. Still, issuance-layer upgrades historically precede tokenomics news, so the chatter is worth noting without overweighting it.
- Bridge liquidity. The single-proof withdrawal window drops from 7 days to 5 days . A shorter finalization period may compress fast-bridge premiums slightly as provider capital recycles sooner. Monitor fee spreads on major third-party bridges in the first week post-activation.
The bigger calendar item is Cobalt, targeted for September 2026 . That upgrade is slated to add gas payment in a B20 token, roughly 50% cheaper transfers, doubled throughput, native account abstraction, and a unified node binary . Base labels those as forward-looking and subject to change.
Beryl delivers a real but narrow set of gains: a faster exit, a leaner node, a drop-in token standard. The performance unlock most traders are waiting for lands with Cobalt. Treat June 25 as the setup, not the payoff.
Frequently asked questions
What is the Base Beryl upgrade and when does it activate?
Beryl is Base's second independent named network upgrade, shipping as a hardfork on the existing Base mainnet, not a new chain. It activates at June 25, 2026 at 18:00:00 UTC, after going live on the Base Sepolia testnet on June 18, 2026. It bundles three changes: the B20 native token standard, a shorter single-proof withdrawal window, and a Reth V2 node upgrade.
What is the B20 token standard and how is it different from ERC-20?
B20 is Base's native token standard, implemented as chain-native Rust precompiles that run inside the node software rather than as EVM bytecode deployed per issuer (source: Base, 2026-06). It implements the ERC-20 specification with selector parity, so existing wallets, exchanges, and explorers treat B20 tokens as ERC-20s with no special integration. The difference is built-in issuer tooling: role-based access, transfer policies, freeze-and-seize, and memos, plus cheaper, higher-throughput execution (source: CryptoBriefing, 2026-06).
Do I need to do anything as a Base user for the Beryl upgrade?
No. Regular users and traders need to take no action; the hardfork applies automatically at activation. Only node operators must act: mainnet requires base-reth-node v1.1.1+ and base-consensus v1.1.1+, and the upgrade must be completed before June 25 at 18:00 UTC (source: Base node releases, 2026-06).
How does Beryl change Base withdrawal times?
Beryl reduces the standard single-proof finalization window for Base→Ethereum exits from 7 days to 5 days. The dual-proof fast path introduced with Azul, where TEE and ZK proofs agree, stays at 1 day. Third-party fast bridges run on their own liquidity and are unaffected by this protocol change, though their providers may benefit as canonical-bridge capital recycles two days sooner (source: Chainstack, 2026-06).
Will Beryl launch a Base native token?
No. Beryl adds token issuance infrastructure through B20, not a Base network token, and Base has made no such announcement (source: Base, 2026-06). The upgrade has renewed speculation: one report cited prediction-market odds of about 28.5% for a Base token launch by December 31, 2026, down from roughly 34%. That is a speculative third-party figure, not an official statement.
