After a pair of delays and a brief but notable chain halt, Base has officially activated its B20 token standard on mainnet on July 8, marking the launch of the Layer 2’s own version of ERC-20 that runs as a native precompile instead of a regular smart contract. The standard, introduced by Jesse Pollak in mid-June, is now live as part of Base’s Beryl hard fork, with the B20 Activation Registry fully operational and enabling developers to deploy B20 tokens.

What Is B20?

B20 is not a separate token; it is a protocol-level token standard that behaves like ERC-20 but is built deeper into Base’s node software using Rust precompiles. In practical terms, this means:base+1

1. Lower fees and faster execution: Token logic is handled at the protocol level, reducing gas costs and improving transfer speed compared to traditional ERC-20 contracts.bitget+1

2. Built-in compliance tooling: B20 ships with role-based access controls, transfer policies, allow/block lists, and freeze-and-seize capabilities, making it especially attractive for stablecoin and real-world asset (RWA) issuers who need regulatory controls.base+1

3. ERC-20 compatibility: Existing wallets and dApps that already support ERC-20 can interact with B20 tokens without needing major changes, easing adoption.

For Base, B20 is a strategic move to position the chain as the go-to Layer 2 for regulated financial instruments, not just DeFi experiments.

From Testnet to Mainnet

The rollout has been a story of ambition and caution:

1. Announcement: Jesse Pollak revealed B20 on June 16, 2026, describing it as a native standard purpose-built for stablecoins and RWAs.

2. Testnet deployment: The B20 standard was deployed on Sepolia around June 18–19, 2026, giving developers a sandbox to experiment.

3. First mainnet slip: The initial mainnet activation was planned for June 25 but was delayed by 24 hours after the B20 Activation Registry required extra time to become fully operational.

4. Chain halt complications: Base suffered a roughly two-hour block production outage on June 25 and a second, shorter interruption on June 26, prompting the team to pause the B20 Activation Registry’s debut again.

5. Go-live: The standard finally activated on June 26 at 18:00 UTC, with the registry fully live and developers able to launch B20 tokens.

Despite the turbulence, the network confirmed that user funds remained secure at all times and that testnets continued on schedule.

Immediate Ecosystem Impact

The day after B20 went live, several notable developments emerged:

1. Binance Wallet support: Binance Wallet announced it will support B20 token trading at rollout, signalling that a major exchange-integrated wallet is ready to handle the new standard.

2. Stablecoin and RWA pilots: Projects planning to issue stablecoins or tokenized assets on Base are now able to deploy B20 variants with built-in compliance, rather than relying on external contracts.

3. Developer momentum: Base documentation now includes a dedicated “Launch a B20 Token” guide, instructing developers to call the B20 Factory precompile instead of deploying custom ERC-20 contracts.

What’s Next for B20?

While the standard is live, the ecosystem is still in early adoption mode. The community is watching for the first stablecoin or RWA project to fully launch using B20, which will test its compliance tooling in real-world conditions. Wallets, explorers, and SDKs will need to surface B20-specific features (like memos and policy flags) more visibly to end users. Base has already reduced the single-proof withdrawal delay from 7 days to 5 days as part of Beryl, freeing up latency for users moving assets between Base and Ethereum. For developers, the message is clear: if you’re building tokens that need regulatory controls, stablecoin behaviour, or RWA-like semantics on Base, B20 is now the default path forward.