Base has flipped the switch on its long‑anticipated B20 native token standard on mainnet, opening the door for developers and issuers to mint stablecoins, tokenized equities, real‑world assets (RWAs) and other fungible tokens without deploying standalone ERC‑20 contracts.
Key facts
- Activation: B20 went live on July 8, 2026 at 18:00 UTC under the protocol‑level framework introduced by the Beryl upgrade.
- Compatibility: B20 remains compatible with the ERC‑20 spec and supports ERC‑2612 permit functionality, so existing wallets, exchanges and indexers should continue working without modification.
- Token formats: Two formats are supported — an asset token format (issuer can choose six or 18 decimal places) and a stablecoin format (fixed six decimals, issuer must declare a fiat denomination such as USD or EUR).
- Issuer controls and compliance: The standard includes built‑in controls for minting, burning, pausing, transfer restrictions, supply limits and transaction notes. An Issuer Toolkit provides role‑based permissions and optional compliance features such as freeze and seizure controls for regulated issuers.
Why it matters
By making B20 a native protocol feature, Base lets issuers create and manage fungible tokens directly through the chain’s infrastructure instead of designing, deploying and auditing custom ERC‑20 contracts. That should streamline token issuance and reduce operational overhead for projects that want to launch stablecoins or tokenized real‑world assets on Base.
Context: Beryl upgrade and network changes
B20 was rolled out as part of the Beryl upgrade, which reached mainnet on June 26. The Beryl rollout also shortened Base→Ethereum withdrawals from seven days to five and integrated Reth V2 to reduce node storage requirements while supporting higher block gas targets. Base had previously delayed part of the upgrade by one day to allow the B20 Activation Registry to finish initializing before native token deployments began.
Recent outages and reliability notes
The B20 rollout comes less than two weeks after Base reported two sequencer‑related outages: a roughly 116‑minute incident on June 25 caused by an invalid block entering the sequencing pipeline, and a roughly 20‑minute outage on June 26 caused by a race condition after a system reset. Base said the first disruption occurred hours before the originally planned Beryl activation and characterized the outage as unrelated to the upgrade. Base creator Jesse Pollak emphasized that user funds were safe while acknowledging that service interruptions are unacceptable for infrastructure designed to support global financial activity.
What’s next
With B20 live, developers and regulated issuers can begin building native stablecoins and tokenized asset products on Base under a standardized framework that balances developer ergonomics, wallet/exchange compatibility and optional compliance controls. Observers will be watching how quickly projects adopt B20 and whether the network maintains stability as native tokens come online.
Read more AI-generated news on: undefined/news
