Base has delayed the Beryl mainnet improve by at some point to make sure the B20 activation registry is totally operational earlier than the arduous fork goes reside.
Base introduced that Beryl will probably be activated on mainnet on June twenty sixth at 18:00 UTC, as a substitute of the beforehand scheduled June twenty fifth launch.
Supply: basedocs.
The Ethereum Layer 2 Community attributed the delay to timing dependencies associated to the B20 activation registry, which requires builders to finish initialization earlier than deploying native B20 tokens.
The community defined that the activation registry will management whether or not the B20 function flag turns into obtainable after a tough fork. Base added that it could actually take as much as an hour for the registry to come back on-line after activation, requiring an extra delay earlier than continuing with the improve.
B20 deployment and withdrawal adjustments
Beryl is Base’s second impartial community improve, following Azul, which reached mainnet in Might. This launch introduces B20, a protocol-level token normal that enables issuers to create stablecoins and real-world asset tokens instantly inside Base’s Node software program as a substitute of deploying conventional ERC 20 sensible contracts.
Base beforehand said that B20 will preserve compatibility with the ERC 20 specification and help ERC 2612 permission options, permitting present wallets, exchanges, and indexers to work with out modification. The protocol additionally consists of an issuer toolkit that gives role-based permissions, mint and write controls, switch limits, optionally available provide limits, and freeze and foreclosures capabilities for regulated issuers.
The arduous fork will even scale back the usual withdrawal interval from Base to Ethereum from 7 days to five days, a route utilized by most bridge suppliers. Base beforehand attributed this lower to enhancements launched via Azul’s Multiproofs framework that diminished reliance on the unique faultproof problem window.
Beryl has additionally built-in Reth V2, which the community says can scale back node storage necessities by as much as 50% and help larger block fuel objectives.
An outage occurred earlier than a deliberate activation
Base initially scheduled Beryl for June 25, however on that day the community skilled a block manufacturing outage that lasted practically two hours. The engineering crew recognized the consensus concern after an invalid block entered the sequencing pipeline, quickly halting the creation of recent blocks.
Engineers restored regular block manufacturing later that day, however the base confirmed that the incident was unrelated to the deliberate Beryl improve.
We’ve confirmed that the blocks are efficiently generated and are extensively recovered throughout the ecosystem.
The remaining caught base node will get better upon reboot and synchronization.
Now that the crew has found the foundation reason behind this outage, we plan to share a full autopsy primarily based on what we realized.
— Base Construct (@buildonbase) June 2026 25
Base creator Jesse Pollack additionally acknowledged {that a} community outage was unacceptable for an infrastructure meant to help international monetary exercise, however stated customers’ funds remained secure throughout the outage.
Base is planning its subsequent community improve, Cobalt, in September. The corporate expects this launch to introduce native account abstraction, protocol-level sensible accounts, fuel sponsorship, transaction batching, extra B20 options, and an integration node binary that mixes consensus and execution shoppers.
