Almost every token you have swapped on Base is an ERC-20, the same standard used across Ethereum since 2015. In June 2026, Base's Beryl upgrade introduced something different: a native token standard called B20. It is not a replacement for ERC-20, and most tokens you already trade are unaffected by it. But it is worth understanding, because it changes what "just a token" can mean on Base going forward.
A token built into the network, not on top of it
An ordinary ERC-20 token is a smart contract. Someone writes it in a language like Solidity, deploys it as bytecode that runs on the Ethereum Virtual Machine, and every transfer executes that bytecode. A B20 token skips that layer entirely. Its logic is written in Rust and runs as a precompile inside Base's own node software, the same category of low level function normally reserved for cryptographic operations the chain needs to be fast at.
That difference is not just technical trivia. Because a B20 transfer never executes EVM bytecode, it is reported to be roughly half the cost of an equivalent ERC-20 transfer and capable of close to double the throughput. B20 tokens also get deterministic addresses and gasless approvals through a permit style signature built in by default, rather than bolted on as an optional extension the way permit signatures work for ERC-20 tokens today.
Two variants, aimed at issuers
B20 ships with two token types. Asset tokens support configurable decimals and rebasing, which suits tokenized funds or yield bearing instruments where the balance itself needs to change over time. Stablecoin tokens use a fixed six decimals and carry a self declared currency code, mirroring how USDC and other stablecoins already behave.
Neither variant is something an average person deploys on a whim. Base built B20 with stablecoin issuers and tokenized asset platforms in mind, and the timing lines up with Coinbase's broader 2026 push into tokenized stocks and other regulated onchain assets on Base.
The part that matters most: controls built into the standard itself
This is where B20 differs most from a typical token you swap today. Every B20 token ships with role based permissions for minting, burning, pausing, and metadata changes, along with allowlists and blocklists and a policy registry that lets an issuer define transfer rules for specific addresses. B20 also includes a freeze and seize function, meaning an issuer can block or reclaim tokens held at a specific address without needing the holder's cooperation.
None of this is new in concept. Some existing ERC-20 tokens already carry owner controlled mint, pause, or blacklist functions written in by their deployer, and Circle has publicly disclosed freezing USDC addresses under narrow, specific circumstances. What B20 does is turn that from an optional pattern a project might add into a standardized feature of the token type itself, aimed squarely at issuers who are legally required to have it, such as regulated stablecoin issuers and platforms offering tokenized securities.
What this means if you swap tokens rather than issue them
For most Simple Base Swap users, the immediate impact is small. The long tail of tokens on Base, including the ones you are most likely to research and swap, remain ordinary ERC-20 contracts, and B20 is currently positioned for regulated stablecoins and tokenized assets rather than general purpose tokens.
If you do end up holding a B20 stablecoin or tokenized asset, though, it is worth treating it the way you would already treat a centralized stablecoin: as an asset whose issuer retains real control over it. A freeze and seize function tied to a policy registry is a meaningful difference from a fully permissionless bearer asset, even though both can sit in the same self custody wallet. The tradeoff is not automatically bad, since it is often the reason a regulated issuer can offer that asset onchain at all, but it is a tradeoff worth knowing about before you hold a large balance.
One practical wrinkle: because a B20 token runs as a precompile instead of a deployed contract, tools built around reading ordinary Solidity contracts, like Basescan's Read Contract tab, may not surface the same information you are used to checking for a standard ERC-20. Until tooling catches up, the more reliable source for what controls a specific B20 token carries is the issuer's own disclosure, the same way you would look to Circle's own documentation to understand USDC's freeze policy rather than trying to infer it from the contract alone.
The short version
B20 is a new, network level token standard on Base that trades the flexibility of arbitrary Solidity code for lower fees, faster transfers, and compliance features issuers can turn on by default. It is built for stablecoins and tokenized assets, not for the average token you might swap on a given afternoon. If you come across one, the useful question is not whether the standard itself is safe, but who the issuer is and what their disclosed policy for freezing or seizing funds actually says.
Sources
- Introducing Base Beryl, Base Engineering Blog
- Base Activates Beryl Upgrade June 25 as B20 Token Standard Goes Live, Bitcoin.com News
- Coinbase's Base Launches a Native Token Standard With Freeze-and-Seize Built In, Unchained
- Base Beryl Upgrade: B20 Token Standard, Faster Withdrawals, and Reth V2 Explained, thirdweb
- Coinbase's Base unveils strategy to focus on tokenized markets, stablecoins and developers, CoinDesk