Base has postponed the Beryl mainnet upgrade by one day to ensure the B20 activation registry is fully operational before the hard fork goes live.
Base has announced that Beryl will now activate on Mainnet on June 26 at 6:00 PM UTC instead of the previously planned June 25 launch.
Source: basedocs.
The Ethereum Layer 2 network attributes the delay to a timing dependency involving the B20 activation registry, which must complete initialization before developers can deploy native B20 tokens.
The network explained that the activation registry determines whether B20 feature flags become available after the hard fork. Base added that it can take up to an hour for the registry to come online after activation, requiring the additional delay for the upgrade to go through.
Changes to the rollout and withdrawal of B20
Beryl is Base’s second independent network upgrade after Azul, which hit the mainnet in May. The release introduces B20, a protocol-level token standard that allows issuers to create stablecoins and real-world asset tokens directly in Base’s node software instead of deploying conventional ERC 20 smart contracts.
Base previously said that B20 remains compatible with the ERC 20 specification and supports ERC 2612 licensing functionality, allowing existing wallets, exchanges and indexers to work without modifications. The protocol also includes an Issuer Toolkit that provides role-based permissions, mint and burn controls, transfer restrictions, optional supply limits, and freeze and seizure functions for regulated issuers.
The hard fork also shortens the standard withdrawal period from Base to Ethereum from seven days to five days for the route used by most bridge providers. Base previously attributed the reduction to improvements introduced through Azul’s Multiproofs framework, which reduced reliance on the original error-proof challenge window.
Beryl also integrates Reth V2, which the network claims reduces node storage requirements by up to 50% while supporting higher block gas targets.
An outage occurred before the scheduled activation
Base originally scheduled Beryl for June 25, the same day the network suffered a block production outage that lasted nearly two hours. The engineering team identified a consensus issue after an invalid block entered the sequencing pipeline and temporarily stopped creating new blocks.
Engineers restored normal block production later that day, while Base confirmed the incident was not related to the planned Beryl upgrade.
Blocks are being produced normally and we have seen widespread recovery in the ecosystem.
Any remaining stuck base nodes will recover upon restart and sync.
The team has found the cause of this stop and we will share a full post-mortem based on our learnings and…
— Basisbouw (@buildonbase) June 25, 2026
Basic creator Jesse Pollak also stated that user funds remained safe during the outage, while acknowledging that network outages were unacceptable for infrastructure intended to support global financial activity.
Base has its next network upgrade, Cobalt, scheduled for September. The company expects this release to introduce native account abstraction, protocol-level smart accounts, gas sponsorship, transaction batching, additional B20 capabilities, and a unified binary node that combines consensus and execution clients.