Particle.news
Download on the App Store

Base Delays Beryl Upgrade to June 26

The brief postponement gives Base time to bring a newly added activation registry online so native token issuance, protocol issuer controls, faster withdrawals, reduced node storage start safely.

Overview

  • Base moved the Beryl mainnet hard fork to June 26 at 18:00 UTC to allow the B20 Activation Registry up to an hour to finish initializing before native B20 tokens can be deployed.
  • Engineers found a timing dependency during activation that requires the registry to be fully online before B20 feature flags become available, so the schedule change preserves a controlled rollout for protocol-level tokens.
  • Beryl makes B20 a protocol-level token standard implemented as Rust precompiles, and it includes an Issuer Toolkit with role-based permissions, mint and burn controls, transfer limits, optional supply caps, and freeze/seizure functions while remaining compatible with ERC-20 and ERC-2612 tooling.
  • The upgrade shortens the common Base-to-Ethereum withdrawal window from seven days to five days by relying on Multiproofs improvements from the earlier Azul release, and it integrates Reth V2 to cut node storage needs by as much as half and allow higher block gas targets.
  • A nearly two-hour block production outage on June 25 was traced to a separate consensus failure involving an invalid block, Base said production has resumed, user funds were safe, and the team still plans a further upgrade called Cobalt in September to add account abstraction and additional B20 features.