USDBase Mainnet Stalls Again After Beryl Rollout Delay
Network Recovery Required Node Restarts After Brief Chain Halt
TL;DR
- Base suffered another mainnet block production issue after an earlier outage and Beryl hard fork delay.
- Base said block production resumed and told node operators to restart mainnet nodes.
- Beryl introduced the B20 token standard, shorter withdrawal delays and Reth V2 storage improvements.
Trade smarter on Jupiter, Solana’s leading DEX built for fast execution and deep liquidity.
Swap tokens at competitive rates, route across multiple liquidity sources automatically, and access perpetuals, DCA, and advanced trading tools — all in one place!
Base, the Ethereum Layer 2 network incubated by Coinbase, suffered a second mainnet stall in two days after a difficult Beryl upgrade window that included a delayed hard fork, a separate consensus-related outage and another short-lived chain halt-style incident.
The latest issue was flagged on June 26, 2026, when an alert said Base Mainnet was experiencing a chain halt with “similar symptoms.” Base later said, “Block production is resumed,” and told node operators, “Node operators will need to restart their Base Mainnet nodes in order to resume syncing.”
Base’s communications lead was contacted for comment regarding the second mainnet stall, but no response was included in the provided information. The incident appeared shorter than the prior day’s outage, though the exact technical root cause of the second event was not fully explained.
Beryl Delay Came Before Mainnet Production Issues
Base’s Beryl hard fork was delayed to June 26, 2026, at 18:00 UTC, rather than its original June 25 schedule, because Base wanted the hard fork’s underlying B20 Activation Registry to be fully operational before activation.
The delay was described as a timing dependency rather than a security emergency or failed upgrade. Base’s team said developers cannot deploy tokens using the new native B20 standard until the Activation Registry is live, because the registry controls whether B20’s feature flags are active.
The B20 Activation Registry may take up to one hour after the hard fork activates to become fully operational. That timing issue was the stated reason for delaying the hard fork instead of launching into a state where the new B20 functionality was not fully ready.
Beryl was Base’s second independent network upgrade after Azul, which activated on mainnet in May 2026. Beryl introduced the B20 token standard, a protocol-level token standard aimed at stablecoin issuers and real-world asset issuers.
B20 tokens run as Rust precompiles inside Base’s node software rather than as deployed smart contracts. The standard includes role-based access, transfer policies and freeze-and-seize controls, placing its design focus on regulated asset issuance.
Beryl also reduced Base’s standard single-proof withdrawal delay from Base to Ethereum from 7 days to 5 days. The upgrade integrated Reth V2, which Base says can reduce node storage overhead by up to 50%.
Base’s next upgrade, Cobalt, is targeted for September 2026. Expected features include native account abstraction and additional B20 capabilities.
We’ve launched the all-new COIN360 Perp DEX, built for traders who move fast!
Trade 130+ assets with up to 100× leverage, enjoy instant order placement and low-slippage swaps, and earn USDC passive yield while climbing the leaderboard. Your trades deserve more than speed — they deserve mastery.
Earlier Outage Was Tied to Consensus Failure
The prior Base mainnet outage occurred on June 25, 2026, when a consensus failure caused an invalid block to enter the sequencing pipeline. Base’s team said that outage was unrelated to the planned Beryl upgrade.
Block production stopped after the invalid block affected the sequencer after block 47,806,542. No user funds were reported to be at risk, but withdrawals were interrupted during the outage.
Healthy block production resumed after roughly two hours, according to Base’s status page. After that incident, node operators were directed to restart, indicating that infrastructure-side intervention was part of the recovery process.
The second mainnet stall came after that outage and carried similar operational symptoms, based on Base’s alert wording. The provided information does not state that user funds were at risk during the second incident or that withdrawals were interrupted again.
FAQ
What caused the first Base outage?
A consensus failure allowed an invalid block into the sequencing pipeline.
Did Base link the first outage to Beryl?
No. Base’s team said it was unrelated to the planned Beryl upgrade.
What did node operators need to do?
Base told node operators to restart Base Mainnet nodes to resume syncing.
What remains unclear?
The exact technical root cause of the second stall was not fully explained.
This article has been refined and enhanced by ChatGPT.
