Base’s Jesse Pollak unveils B20 token standard for stablecoins and RWAs

Jesse Pollak, the creator of Base, just introduced something that could reshape how stablecoins and tokenized assets actually work on Coinbase’s Layer 2 network. It’s called B20, a native token standard purpose-built for regulated financial instruments, and it’s arriving with Base’s Beryl hard fork later this month.

The standard is ERC-20 compatible, meaning existing wallets and dApps won’t need to reinvent the wheel. But under the hood, B20 runs on Rust precompiles instead of traditional Solidity smart contracts, a design choice aimed at squeezing out better execution speed and lower costs.

What B20 actually does

The standard ships with a built-in compliance toolkit that includes granular role assignments for minting and burning tokens. It also features policy-driven allow and block lists, which let issuers control exactly who can hold or transfer their tokens.

B20 also supports transaction memos, optional supply caps, and distinct configurations for what Base is calling its “Asset” and “Stablecoin” variants.

The Sepolia testnet deployment is scheduled for approximately June 18-19, with the mainnet activation following on June 25-26.

The Beryl hard fork brings more than tokens

The withdrawal finality window, the time users currently wait to move assets from Base back to Ethereum mainnet, drops from 7 days to 5 days. That’s a 29% reduction in the single most annoying friction point for Layer 2 users.

Base is also upgrading to Reth V2 infrastructure for its node architecture. The numbers are notable: 50% reduced disk usage and 33% increased throughput.

Why compliance at the protocol layer matters

Pollak’s approach with B20 is to push compliance tooling down into Base’s protocol layer itself. The allow/blocklist functionality, the role-based access controls, the supply caps: these are features that regulated issuers currently pay specialized firms to build and audit as custom smart contracts.

There’s a legitimate question about whether embedding compliance at the protocol level introduces centralization risks that undermine the point of building on a blockchain in the first place. Allow/blocklists are powerful tools. In the hands of a stablecoin issuer managing sanctions compliance, they’re necessary. In theory, they could also be used to restrict users in ways that the broader crypto community would find objectionable.