The Base B20 token standard went live on mainnet at 18:00 UTC on 8 July, giving developers a protocol-level route to issue stablecoins, tokenised real-world assets (RWAs), and other fungible tokens without writing or auditing a custom ERC-20 contract.
The launch is the second activation to come out of the Beryl upgrade cycle. The Beryl upgrade itself activated on 25 June at 18:00 UTC (Unix timestamp 1782410400), requiring nodes to run base-reth-node v1.1.1+ and base-consensus v1.1.1+, according to Base’s official upgrade documentation. B20 token issuance followed nearly two weeks later once the B20 Activation Registry had completed initialisation.
What the Base B20 Token Standard Actually Does
Rather than deploying a token contract, issuers interact with a singleton B20 factory precompile baked into the protocol. Chainstack’s developer documentation describes B20 as a native precompile implementation: there is no contract to write, deploy, or audit.
Two token formats are available. The asset format supports either six or 18 decimal places. The stablecoin format locks decimals at six and requires the issuer to specify a fiat denomination, such as USD or EUR.
Built-in issuer controls cover minting, burning, pausing, transfer restrictions, supply limits, and transaction notes. An Issuer Toolkit adds role-based permissions and optional compliance features, including freeze and seizure controls for regulated issuers. Crucially, admin controls are not simply configurable off: according to Base’s B20 specification, the only path to an admin-less token is calling renounceLastAdmin(), a dedicated function with no other equivalent.
The standard is backward-compatible with ERC-20 and supports ERC-2612 permit functionality, so existing wallets, exchanges, and indexers need no modification.
Beryl Also Tightened the Withdrawal Window and Upgraded Node Storage
Alongside B20, the Beryl upgrade reduced the single-proof dispute game finalisation window from seven days to five days. The dual-proof fast path introduced in the prior Azul upgrade, which uses a combined TEE and ZK proof, remains at its existing one-day finalisation window and was unaffected by Beryl. Crypto Briefing reported the reduction as five hours; Base’s official documentation states five days, and that figure is used here.
Beryl also integrated Reth V2, which Base says cuts node storage requirements while supporting higher block gas targets. Crypto Briefing notes a Cobalt upgrade is already on the roadmap, continuing a cadence that saw Azul ship in May 2026 and Beryl follow roughly four weeks later.
The Sequencer Bugs That Preceded the Launch
B20 is live less than two weeks after back-to-back sequencer outages put Base’s infrastructure under scrutiny.
The first outage began at 11:47am EDT on 25 June and lasted approximately 116 minutes. The second began at 11:28am EDT on 26 June and lasted roughly 20 minutes. An independent post-mortem by Metrika placed the block production halt at block 47806542 at 15:47 UTC on 25 June.
The root cause of both incidents was the same bug, according to Base’s official postmortem. An invalid transaction failed during execution but did not clear the journal state covering accounts and storage slots that had been accessed. The result was a sequenced block carrying an invalid state transition that no other node could accept. The second outage, shorter at 20 minutes, stemmed from a race condition that stopped sequencers from catching up following a system reset.
The first disruption occurred hours before the originally scheduled Beryl activation. Base said the outage was unrelated to the upgrade; the one-day delay that followed was driven by a separate dependency: Crypto.news reported the B20 Activation Registry can take up to one hour to come online after activation, making the additional time necessary before developers could safely deploy native B20 tokens. Base creator Jesse Pollak acknowledged the interruptions were unacceptable for infrastructure intended to support global financial activity, while confirming user funds remained safe throughout.
The more pressing question for issuers is now governance design: once a B20 token goes admin-less via renounceLastAdmin(), there is no reversal. That one-way door will matter a lot when the first regulated stablecoin issuer decides whether to keep the freeze key or burn it.
