Base plans to activate B20 standards for stablecoins and real-world assets

Coinbase-backed Layer-2 Network Base is preparing to launch its new B20 token standard on the mainnet, which aims to provide developers with a native way to issue stablecoins and other homogeneous assets, such as tokenized real-world assets (RWAs). Base said the standard will be activated at 6 p.m. UTC, and once it is online, developers can start creating B20 tokens. This release marks a shift away from building and auditing custom token contracts. Instead, the B20 provides an on-chain framework that supports issuer control functions-features Base says are designed to simplify the creation of stablecoins and asset-class tokens, without developers having to implement their own token logic from scratch.

Key Points

According to Base documentation, Base will enable the B20 token standard on the main network at 6 pm UTC.

B20 includes two variants: asset format (configurable decimal places) and stablecoin format (fixed six decimal places precision).

This standard aims to reduce developer workload by avoiding building and auditing custom ERC-20 contracts for common token functions.

Base stated that the B20 token remains compatible with the ERC-20 while adding issuer control features such as supply restrictions and casting/destruction rights.

This release follows recent outages at Base due to sorter infrastructure issues, including incidents on June 25 and June 26.

B20 changes to Base\'s previous currency issuance

Base\'s B20 standard introduces a built-in token framework designed to standardize how homogeneous assets are created and managed on the network. In Base\'s documentation on the \"Launch B20 Tokens\" process, the network describes B20 as a native mechanism that developers can use to issue tokens for scenarios such as stablecoins, real-world assets (RWA), and tokenized equity.

Base also outlines two variants supported by the B20: the asset variant allows decimal places between 6 and 18; the stablecoin variant requires a fixed six-digit decimal format and requires the issuer to specify a legal tender denomination (such as U.S. dollars or euros).

Base says that developers can start creating B20 tokens after standard activation. The goal is not only convenience, but also operational consistency: rather than having each project write its own token contract and test it, the B20 aims to package common token behavior into a standardized structure.

Built-in control features replace custom ERC-20 logic

In addition to simple compatibility, Base means that the B20 token is also designed with issuer control features that typically require custom contract logic in many token deployments. According to Base, B20 tokens are compatible with standard ERC-20 tokens, but include additional mechanisms that issuers can configure and manage.

Base lists the functions under its issuer control framework, including: supply restrictions, transfer rules, casting and destruction, suspension, and transaction notes.

For developers, the practical significance is that the B20 can simplify token deployment in application scenarios that require permissions and operational guarantees-especially stablecoin issuance and regulated or semi-regulated asset tokenization models. Standardized issuer control behavior also makes it easier for users to understand how tokens are managed, although specific implementation details still depend on the parameters selected by each issuer.

B20 is associated with Beryl upgrade

The B20 was introduced as part of Base\'s Beryl upgrade, which Base said was launched on June 26. Base\'s documentation attributes the introduction of B20 to this upgrade cycle and views it as part of larger network changes.

In addition to enabling the B20 feature, the Beryl upgrade reportedly shortened the withdrawal waiting period from seven days to five days. Base also noted that as part of the same upgrade, technical changes were also made to improve network performance.

This context is important because the B20 is not an isolated feature release-it comes with changes designed to affect the user experience (cash withdrawal) and developer/build conditions (network behavior and token standard availability). In other words, the release of the B20 is related to a larger upgrade narrative rather than a stand-alone deployment.

Release timing after the Base Sorter Event

The point in time for the B20 mainnet activation was after Base experienced an operational outage, including downtime related to the sorter infrastructure.

On June 25, Base reported an outage caused by a consensus issue. At the time, the network stated that an invalid block was sorted, making it impossible to create a new block. After a nearly two-hour pause, Base resumed block production the same day.

In a post-mortem analysis, Base attributed consecutive outages on June 25 and 26 to a sorter bug that triggered the first outage and then caused the second outage due to reset related race conditions. The first event lasted about 116 minutes, and the second lasted about 20 minutes after the sorter failed to keep up with the reset pace.

These events are also intertwined with upgrade timing points. Base said the first outage occurred hours before the planned Beryl upgrade. The Beryl upgrade was subsequently delayed for one day due to a timing issue with the B20 activating the registry, indicating that there was already B20-related coordination during this release window.

The key issue for participants concerned about the Base ecosystem is how token standard activation and network reliability interact during upgrades. The release of the B20 marks a push for functional expansion, but recent outages have highlighted that the underlying sequencer infrastructure and operating processes surrounding upgrades remain key factors for stability.

As B20 will be activated at 6 p.m. UTC, developers and token issuers will be focusing on the speed at which real stablecoins and RWA-related products adopt the standard, and whether Base\'s recent sequencer events remain isolated events as more activities migrate to the new framework.