Base Beryl Upgrade Explained: B20 Token Standard, Faster Withdrawals, and Reth V2
Base Beryl activates June 25, bringing the B20 native token standard for compliant issuance, faster 5-day withdrawals, and Reth V2 with dramatically improved performance. Everything builders need to know.
Base, Coinbase's Layer 2 network built on the OP Stack, is about to ship its most significant upgrade yet. Beryl activates on Base mainnet on June 25, 2026, and it bundles three changes that touch every layer of the stack: a new native token standard called B20, a shorter withdrawal window from 7 days to 5, and a full execution-client overhaul with Reth V2.
For builders deploying tokens, bridging liquidity, or running infrastructure on Base, Beryl is not a minor patch. It reshapes how tokens are issued, how capital moves between L1 and L2, and how much headroom node operators have to scale. Here is everything you need to know before activation day.
B20: A Native Token Standard Built for Issuers
The headline feature of Beryl is B20, Base's own token standard. Unlike traditional ERC-20 tokens that deploy as standalone smart contracts and require separate audits for each compliance feature, B20 tokens run as Rust precompiles baked directly into Base's node software. The token logic executes at the protocol level rather than through EVM bytecode, which makes transfers cheaper and higher-throughput while maintaining full ERC-20 compatibility.
B20 ships with a built-in compliance toolkit that would normally take months to build and audit from scratch. Transfer policies, freeze-and-seize capabilities, role-based access control, memos, supply caps, and EIP-2612 permit support are all included out of the box. Issuers create a fully configured token in a single transaction by calling the singleton B20 Factory precompile.
The standard launches with two variants. The Asset variant handles general token issuance with configurable decimals, issuer metadata, event announcements, and rebasing support. The Stablecoin variant is purpose-built for fiat-backed assets, using six-decimal precision with an issuer-selected currency code. Both variants are designed so that stablecoin issuers, real-world asset tokenizers, and long-tail token creators can launch compliant tokens without writing custom Solidity for each compliance requirement.
This matters for the broader ecosystem because it lowers the barrier to regulated token issuance on L2. Projects that previously needed expensive audits for custom compliance logic can now rely on battle-tested, protocol-level primitives. For RWA builders especially, B20 removes one of the biggest friction points in bringing traditional assets onchain.
Faster Withdrawals: 7 Days Down to 5
Beryl also shortens the single-proof withdrawal finalization period from 7 days to 5 days. If you withdraw through Base's canonical L1 bridge, you will wait two fewer days to finalize your transaction on Ethereum mainnet. No user action is required — the improvement applies automatically after activation.
Two days may not sound dramatic, but the impact on capital efficiency is real. Bridging providers and liquidity protocols that lock capital during the finalization window can now redeploy those funds 29 percent faster. For users moving large amounts between Base and Ethereum, the reduced wait time makes the canonical bridge a more practical option compared to third-party fast bridges that charge fees for instant finality.
This change reflects a broader trend across the OP Stack ecosystem: L2s are steadily compressing their trust assumptions and settlement times as fault-proof systems mature. Base's move from 7 to 5 days signals confidence in their dispute resolution mechanism and sets the stage for further reductions down the line.
Reth V2: 50 Percent Less Disk, 33 Percent More Throughput
Under the hood, Beryl ships Reth V2, a major overhaul of Base's execution client. Reth, originally built by Paradigm, is a high-performance Ethereum execution client written in Rust. Version 2.0 achieves 1.7 gigagas per second performance while cutting disk usage roughly in half.
The key improvement is a completely rewritten state-root pipeline and storage layout. Saving a standard block now takes an average of 40 milliseconds, and even a massive gigagas-sized block persists in just 400 milliseconds — a roughly 20x speedup over the previous storage engine. Block execution latency drops by about 25 percent on average.
For end users, Reth V2 is invisible. For node operators, RPC providers, and indexers carrying Base's growing transaction load, it provides critical headroom. The 33 percent throughput increase and 50 percent disk reduction mean that running Base infrastructure costs less and handles more, which is important as Base pushes toward its stated goal of 1 gigagas per second on mainnet.
Node operators running OP Reth via base-reth-node can update to the latest version without re-syncing. Existing data directories are fully compatible. Operators still on op-geth or Nethermind will need to switch to base-reth-node and bootstrap from a Reth snapshot before activation.
What Builders Should Do Before June 25
Beryl is already live on Base Sepolia for testing. If you are deploying tokens on Base, now is the time to evaluate whether B20 fits your use case. The B20 Factory is available on testnet, and the full interface specifications are published in the Base Standard Library repository. For stablecoin or RWA projects, the built-in compliance primitives could eliminate weeks of custom development.
If you run Base infrastructure, make sure your nodes are on base-reth-node v1.1.1 or later and base-consensus v1.1.1 or later before June 25. The upgrade is not optional for node operators — nodes that have not updated will fall out of consensus at the activation timestamp.
For application developers building on Base, the withdrawal time reduction requires no code changes. Your users will simply experience faster finalization when bridging back to Ethereum. If your application surfaces bridge status or estimated completion times, update those UI elements to reflect the new 5-day window.
The Bigger Picture: L2s Are Becoming Issuance Platforms
Beryl is significant not just for what it ships, but for what it signals. By building a native token standard with institutional-grade compliance features directly into the protocol, Base is positioning itself as a first-class issuance platform — not just a scaling solution. The B20 standard is a direct play for the stablecoin and RWA market, which has grown into one of the most active sectors in crypto during 2026.
Combined with faster withdrawals and a more efficient execution layer, Beryl makes Base meaningfully more competitive for the types of high-value, compliance-sensitive applications that traditional finance is exploring onchain. For builders evaluating where to deploy their next token or financial product, this upgrade makes Base a much stronger candidate.
Whether you are building token infrastructure, bridging solutions, or onchain applications, the tools available to developers on L2s are getting more powerful with each upgrade cycle. If you are looking for a development platform that scales with the complexity of modern onchain products, thirdweb offers flexible developer plans designed for exactly this kind of work — explore options at thirdweb.com/pricing.
Key Takeaways
Base Beryl activates on mainnet June 25, 2026, bringing three major changes: the B20 native token standard for compliant token issuance, a withdrawal window reduction from 7 to 5 days, and Reth V2 with dramatically improved node performance. The testnet is live now for builders who want to start integrating. For anyone building in the L2 ecosystem, this is one of the most consequential upgrades of the year.