Coinbase-backed Ethereum layer-2 network Base is preparing to launch the B20 standard on its mainnet, designed for stablecoins, tokenized real-world assets, and other fungible tokens. According to network documentation, the activation is scheduled to begin at 18:00 UTC.
B20 introduces native token framework
The new standard will allow developers to create tokens on Base without having to write their own custom ERC20 contracts or seek additional audits. This covers not just stablecoins, but also tokenized real-world assets, digitized shares, and other interchangeable digital assets.
Base, as an Ethereum layer-2, is built to enable faster and more affordable transactions. The B20 standard is intended to make the issuance processes of tokens more streamlined and structured within this ecosystem.
Base has stated that B20 tokens will remain compatible with standard ERC20 tokens while providing issuers with built-in tools such as supply caps, transfer rules, minting, burning, pausing, and transaction memos.
There are two versions of the B20 standard. The asset-focused variant allows issuers to adjust the number of decimal places between six and eighteen. The stablecoin version fixes decimals at six, and requires issuers to define a fiat currency like the US dollar or euro as the basis.
Mini glossary: “Real-world assets” refers to representing off-chain assets—such as bonds, stocks, commodities, or real estate—on the blockchain in tokenized form. A stablecoin is a digital asset that aims to maintain its value against a fiat currency, typically the US dollar or euro.
| B20 variant | Feature |
|---|---|
| Asset | Number of decimals adjustable between 6 and 18 |
| Stablecoin | 6 decimals fixed, requires definition of a fiat currency |
Rollout linked to Beryl upgrade
B20 was introduced as part of the Beryl upgrade, which went live on June 26. With this update, Base reduced withdrawal wait times from seven days to five and implemented other technical changes aimed at strengthening network performance.
However, the B20 mainnet activation comes on the heels of recent infrastructure disruptions within Base. On June 25, the network experienced an outage caused by a consensus issue. During this time, Base reported an invalid block had been sequenced, preventing the creation of new blocks. Block production resumed after a roughly two-hour interruption.
Back-to-back outages draw attention
A technical review released by Base indicated that successive outages on June 25 and 26 were due to a software bug in the sequencer infrastructure. The first incident lasted about 116 minutes. The second, which followed a system reset, resulted from a race condition that left sequencers unable to sync properly, lasting approximately 20 minutes.
The first outage occurred just hours before the scheduled Beryl upgrade. Due to a separate issue in the B20 activation log timing, the upgrade itself was postponed by one day.
These developments highlight Base’s efforts to not only simplify the developer experience with its new token standard, but also to move beyond the recent technical setbacks affecting its network infrastructure.
