The Ethereum layer-2 network, Base, which receives backing from Coinbase, is slated to introduce its B20 token standard on the mainnet this Wednesday. This launch will establish a native framework specifically designed for issuing stablecoins, tokenized real-world assets (RWAs), and various other fungible tokens.

According to information provided in the Base documentation, the B20 standard's deployment is scheduled for 6 pm UTC on the mainnet. This activation will permit developers to commence the creation of tokens utilizing this new standard.

Implementing this standard allows developers to construct stablecoins, RWAs, tokenized equities, and other fungible tokens directly within Base's native system. Consequently, developers will no longer be required to build and undertake the necessary audits for their own custom ERC-20 contracts.

B20 encompasses two distinct variants: one for general assets and another for stablecoins. The asset variant permits developers to configure decimals anywhere between six and eighteen. Conversely, the stablecoin variant necessitates fixed six-decimal formatting and mandates that issuers explicitly declare the fiat currency they are denominating against, such as the US dollar or the euro.

The introduction of B20 was integrated as a component of the network’s broader Beryl upgrade, which became operational on June 26. That upgrade also reduced the obligatory waiting period for withdrawals from seven days down to just five days, alongside incorporating technical modifications aimed at boosting overall network performance.

Base has asserted that tokens conforming to the B20 standard maintain compatibility with existing ERC-20 tokens. However, B20 tokens feature integrated controls available to the issuer. These integrated capabilities include the ability to set supply limits, define transfer rules, and manage minting, burning, pausing functions, and the inclusion of transaction notes.

This B20 activation follows a period marked by consecutive service interruptions that were linked to the network's sequencer infrastructure.

On June 25, Base experienced an outage traced back to a consensus anomaly. At that time, the network communicated that a sequencing error involving an invalid block had halted the creation of subsequent new blocks. Block generation recommenced later the same day, following a nearly two-hour suspension of service.

In a subsequent post-mortem analysis, Base determined that a bug present in the sequencer was responsible for the back-to-back outages occurring on both June 25 and June 26. The initial downtime lasted approximately 116 minutes. A subsequent, shorter outage, lasting about 20 minutes, occurred because a race condition prevented the sequencers from synchronizing after a necessary system reset.

It is notable that the first service interruption took place just hours before the planned Beryl upgrade was intended to go live. The Beryl upgrade itself had to be postponed by a single day due to a distinct timing issue related to the B20 activation registry process.