Logo Daily Crypto Briefs
Open menu

Base Beryl Upgrade Adds Freeze-and-Seize B20 Tokens June 25

6 min read
Breaking News
Greyscale Base logo token beside a regulated stablecoin and tokenized asset certificate on blue and coral editorial panels.

TL;DR

  • Base will activate the Beryl hard fork on mainnet at 18:00 UTC on June 25 after activating it on Sepolia on June 18.
  • Beryl introduces B20, an ERC-20-compatible native token standard with transfer policies, freeze-and-seize controls, roles, memos and supply caps.
  • The upgrade also cuts the single-proof withdrawal finalization window from seven days to five and moves nodes to Reth V2.
  • Base says Reth V2 can reduce disk use by up to 50% and increase throughput by 33%, while node operators must upgrade before activation.

SAN FRANCISCO, June 19, 2026

Base will activate its Beryl hard fork on June 25 with a new B20 token standard that gives stablecoin and tokenized-asset issuers built-in transfer controls, freeze-and-seize functions and supply limits.

The Coinbase-incubated Ethereum layer 2 scheduled the mainnet activation for 18:00 UTC, one week after Beryl went live on Base Sepolia. The upgrade also shortens one withdrawal route from seven days to five and moves node software to Reth V2.

The rollout lands on a network holding $4.859 billion in stablecoins, up 1.41% over seven days and 2.67% over 30 days, according to DefiLlama’s Base dashboard. USDC represented 86.55% of that supply, while L2BEAT data showed about $4.18 billion in USDC, $2.59 billion in Coinbase Wrapped BTC and $1.57 billion in ether secured on Base.

Ether traded near $1,700 on June 19, down roughly 20% from its May 20 close near $2,130. The ETH-USD market page showed a Friday range of about $1,679 to $1,720 as crypto markets remained under pressure.

Base said in its Beryl technical overview that the release introduces B20 for stablecoins, real-world assets and long-tail tokens, cuts the single-proof withdrawal window, and adds a Reth V2 pipeline delivering up to 50% lower disk use and 33% more throughput.

The upgrade advances Base’s push to become an issuance layer, not only a venue for trading and consumer apps. That makes B20 relevant to the same businesses exploring custom stablecoins on Base, but it also puts issuer control and user expectations at the center of the design.

Ethereum

ETH
May 20 to June 19, 2026
$1,700
-20.2%
May 20 - Jun 19 | High $2,130 Low $1,580

B20 Builds Compliance Into Tokens

B20 is designed as Base’s own version of ERC-20, the standard interface behind most fungible tokens on Ethereum-compatible networks. The difference is that B20 moves common issuer controls into native Rust precompiles instead of requiring every project to assemble them in a separate smart contract.

The B20 specification includes role-based access, transfer policies, minting and burning, supply caps, transaction memos, granular pauses and metadata updates. Base says the interface keeps ERC-20 selector parity, meaning existing wallets and applications should be able to treat B20 as a drop-in token.

There are two variants. The asset version supports configurable decimals, rebasing, onchain announcements and batched issuance. The stablecoin version uses six decimals and lets the issuer declare a fiat currency code.

The compliance functions are the most consequential change. An issuer can connect transfer, minting and receiving actions to allowlists or blocklists. A special burnBlocked function can destroy tokens held by an account that has already been blocked from sending, creating an explicit freeze-and-seize path.

Those controls are optional rather than automatic. The documentation says policy scopes default to ALWAYS_ALLOW, so a B20 token launches with open transfers unless its administrator intentionally applies restrictions. Issuers can also deploy without an administrator or permanently renounce the final admin role.

That distinction matters for users comparing tokenized securities and stablecoins with permissionless crypto assets. The existing tokenized-stock market already depends on issuers, custodians and redemption rules. B20 standardizes more of that control at the chain level, making it easier to inspect but not eliminating counterparty risk.

Base Withdrawals Drop to Five Days

Beryl also changes how quickly capital can exit through Base’s single-proof dispute-game route. The finalization period falls from seven days to five, while the one-day dual-proof path using trusted execution environments and zero-knowledge proofs remains unchanged.

Base says the shorter window should release capital sooner for fast-bridge liquidity providers. In practice, those firms front assets to users before the canonical withdrawal completes, so reducing their lockup can lower financing costs and improve bridge reliability.

The user effect will depend on which bridge and proof route is used. Beryl does not make every withdrawal settle in five days, and third-party bridges can set their own fees, liquidity limits and risk controls.

The change fits a broader competition to make tokenized cash and securities move outside banking hours. The proposed NYSE tokenized-securities platform targets round-the-clock trading and onchain settlement, while Base is building a token format and withdrawal system intended to support similar assets.

B20 itself does not announce a Base network token. It is an issuance standard that other organizations can use. The Beryl documents do not disclose a Base token, snapshot or airdrop, despite market speculation that often follows major network upgrades.

Node Operators Face June 25 Deadline

Base node operators must upgrade before the mainnet fork. The official compatibility table requires base-reth-node, base-consensus or the bundled base/node image at version 1.1.1 or later for mainnet.

Reth V2 is the main infrastructure change. Base says the rewritten state-root pipeline can increase throughput by 33% and reduce disk requirements by as much as 50%, potentially lowering the hardware burden for operators as chain history and state continue to grow.

The Base Standard Library provides Solidity interfaces and mock implementations for the new precompiles. Its public repository includes B20, policy-registry and activation-registry interfaces so developers can integrate and test the native functions before deploying.

The main uncertainty is adoption. Base has not named the first stablecoin, equity or RWA issuer that will launch a production B20 asset, and it has not disclosed a migration path for existing ERC-20 tokens already on the network.

Crypto sentiment remained weak ahead of the upgrade. Alternative.me’s Crypto Fear and Greed Index stood at 14, classified as Extreme Fear, on June 19.

Fear & Greed Index

June 19, 2026
14 Extreme Fear

The next checkpoints are the June 25 activation, node upgrade completion and the first production B20 deployments. Those launches will show whether issuers value chain-native compliance enough to move beyond conventional ERC-20 contracts, and whether users accept the additional controls in exchange for clearer rules and cheaper execution.

Stay up to date

Get the latest crypto insights delivered to your inbox

Fact-checked by: Daily Crypto Briefs Fact-Check Desk

Frequently Asked Questions

When will the Base Beryl upgrade activate?

Base's official documentation schedules Beryl for mainnet activation at 18:00 UTC on June 25, 2026. The Sepolia activation occurred at 18:00 UTC on June 18.

What is the Base B20 token standard?

B20 is an ERC-20-compatible native token standard implemented through Rust precompiles. It is designed for stablecoins, real-world assets, equities and other token issuers.

Can B20 issuers freeze or seize tokens?

Yes, if an issuer intentionally configures those controls. B20 supports allowlists, blocklists and a burnBlocked function for policy-blocked accounts. New deployments default to open transfers unless the issuer changes the policies.

Is B20 a new Base network token?

No. B20 is a token issuance standard, not an announcement of a native Base network token or airdrop. Base has not disclosed a token launch through the Beryl documentation.

How does Beryl change Base withdrawals?

Beryl reduces the single-proof withdrawal finalization window from seven days to five. The one-day dual-proof fast path introduced in the earlier Azul upgrade does not change.

What must Base node operators do before Beryl?

Base says mainnet operators must run base-reth-node, base-consensus or base/node version 1.1.1 or later before the June 25 activation.