TLDR
- Base launches B20 for native stablecoins, RWAs, and tokenized assets.
- B20 lets developers issue tokens without custom ERC-20 contracts.
- Base adds issuer controls for minting, burning, pausing, and limits.
- B20 keeps ERC-20 compatibility for wallets, exchanges, and indexers.
- Launch follows recent Base sequencer outages and the Beryl upgrade.
Base has launched B20 on mainnet, giving developers a native path for stablecoins, RWAs, and fungible tokens. The standard removes the need to deploy custom ERC-20 contracts. It also adds issuer controls while keeping ERC-20 compatibility.
B20 Brings Native Token Issuance to Base
Base activated B20 at 6:00 pm UTC through its mainnet infrastructure. Developers can now issue tokens through a protocol-level framework. The move supports stablecoins, tokenized equities, RWAs and other fungible assets.
The B20 standard includes two token formats for different issuer needs. The asset format supports six to 18 decimal places. The stablecoin format uses six decimals and requires a fiat denomination.
Base built B20 to work with current ERC-20 tools and services. Therefore, wallets, exchanges, and indexers can support tokens without major changes. The standard also supports ERC-2612 permit functionality.
B20 Adds Issuer Controls and Compliance Tools
The B20 framework gives issuers direct controls over token operations. These include minting, burning, pausing, supply limits, transfer rules, and transaction notes. As a result, issuers can manage assets through Base’s native system.
Earlier Base documentation also outlined an Issuer Toolkit for regulated token issuers. The toolkit includes role-based permissions and optional compliance tools. It also supports freeze and seizure controls where legal rules require them.
Base introduced B20 through the Beryl upgrade, which reached mainnet on June 26. The upgrade also cut Base-to-Ethereum withdrawals from seven days to five days. In addition, it integrated Reth V2 to reduce node storage needs.
Launch Follows Base Sequencer Disruptions
The B20 launch follows two recent outages tied to Base’s sequencer infrastructure. On June 25, an invalid block stopped new block production. The incident lasted about 116 minutes before Base restored normal activity.
A second outage occurred on June 26 after a system reset created a race condition. That issue stopped sequencers from catching up and lasted about 20 minutes. Base later linked both incidents to sequencer bugs.
The initial outage happened hours before the planned Beryl upgrade. However, Base delayed the upgrade by one day because of a separate B20 activation registry timing issue. Base said the outage did not relate to the upgrade.
