Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
FollowingBase Network is about to activate the B20 token standard
Coinbase-supported Ethereum Layer 2 network Base is about to activate its B20 token standard on the main network, introducing a native framework for stablecoins, tokenized real-world assets (RWAs) and other interchangeable tokens. According to Base documentation, B20 is scheduled to go online on the main network at 6 p.m. UTC, allowing developers to start creating tokens based on the new standard.
This activation will enable developers to use Base\'s native token standards to create stablecoins, RWAs, tokenized stocks and other interchangeable tokens without having to build and audit custom ERC-20 contracts. The standard supports two variants: asset variants and stablecoin variants. Asset variants can be configured with decimal places between 6 and 18, while stablecoin variants use a fixed six-digit format and require the issuer to specify a fiat currency denomination, such as U.S. dollars or euros.
B20 was introduced as part of the network Beryl upgrade, which went online on June 26. The upgrade shortens the withdrawal waiting time from seven days to five days and adds technical improvements aimed at improving network performance. Base stated that the B20 token is compatible with standard ERC-20 token, but has built-in issuer control functions, including supply restrictions, transfer rules, casting, destruction, suspension, and transaction notes.
Before the B20 was activated, the Base network experienced continuous failures. On June 25, Base encountered a failure due to consensus issues. At the time, the network stated that an invalid block was serialized, making it impossible to create a new block. Nearly two hours after stopping block production, Base resumed block production that day. In post-mortem analysis, Base stated that a sequencer vulnerability caused consecutive failures on June 25 and 26. The first failure lasted about 116 minutes, and the second failure lasted about 20 minutes. The reason was that a race condition occurred after the system reset, which prevented the sequencer from keeping up with progress. The first failure occurred hours before the scheduled Beryl upgrade, which was delayed by a day due to another B20 activation registration time issue.
