Base has pushed its Beryl mainnet upgrade back by one day to ensure a critical component—the B20 Activation Registry—is fully initialized before the hard fork goes live. The network now plans to activate Beryl on June 26 at 18:00 UTC, instead of the originally scheduled June 25, according to Base’s documentation.
Why the delay
- Base says the B20 Activation Registry must complete initialization before developers can deploy native B20 tokens. The registry controls whether B20 feature flags are available after the hard fork and can take up to an hour to come online after activation. The one-day slip gives the team confidence the registry and dependent systems will be ready when the hard fork executes.
What Beryl delivers
Beryl is Base’s second independent upgrade after Azul (which reached mainnet in May). Key changes in this release include:
- B20 token standard: A protocol-level token standard that enables issuers to create stablecoins and real-world-asset tokens directly in Base’s node software instead of deploying ERC-20 smart contracts. B20 remains compatible with the ERC-20 spec and supports ERC-2612 permit functionality so existing wallets, exchanges, and indexers should work without modification.
- Issuer Toolkit: Role-based permissions, mint/burn controls, transfer restrictions, optional supply caps, and freeze/seizure features designed for regulated issuers.
- Faster withdrawals: The standard withdrawal period from Base to Ethereum (for the route used by most bridging providers) is shortened from seven days to five days. Base attributes this reduction to Azul’s Multiproofs framework, which reduces reliance on the original fault-proof challenge window.
- Reth V2 integration: Node storage requirements are reduced by up to 50% and higher block gas targets are supported.
Recent network outage and safety
Base experienced a nearly two-hour block production outage on June 25 after an invalid block entered the sequencing pipeline; engineers identified a consensus issue and temporarily halted block production. Production was restored later that day. The team confirmed the incident was unrelated to the planned Beryl upgrade, that user funds remained safe, and that any stuck nodes will recover after restart and syncing. Base said it has found the halt’s root cause and will publish a full post‑mortem.
What’s next
Base has scheduled its next upgrade, Cobalt, for September. The team expects Cobalt to introduce native account abstraction (protocol-level smart accounts), gas sponsorship, transaction batching, additional B20 capabilities, and a unified node binary combining consensus and execution clients.
Source: Base documentation.
Read more AI-generated news on: undefined/news
