Base network halts block production in 'Unsafe Head Stall'
Tech & Launches ·
The Coinbase-incubated layer-2 network suffered an interruption that stalled block production and delayed deposits, withdrawals, and transaction confirmations.
Base, the layer-2 blockchain incubated by Coinbase, experienced what its status page described as an "Unsafe Head Stall," an event that halted block production and left users unable to reliably move funds. According to The Block, deposits and withdrawals were affected while transactions were delayed or stalled during the incident.
The disruption is not an isolated event for Base. The network has recorded multiple block-production outages in recent periods, including one lasting over one hour and separate incidents lasting more than two hours, several of which occurred ahead of a planned network upgrade. Decrypt reported that Base recovered after one such block-production issue, underscoring a pattern of stalls tied to the network's upgrade cycle.
That upgrade cycle centers on Beryl, which The Block reported was targeted for a June 25 mainnet launch alongside a new B20 token standard. The repeated stalls preceding this rollout raise questions about the stability of Base's infrastructure during periods of active protocol change, though the material does not specify a direct causal link between the Beryl upgrade work and the Unsafe Head Stall itself.
The disruptions have occurred against a backdrop of broader activity on Base, including Sophon's decision to shut down its native ZK layer-2 and pivot to Base, transitioning into SOPH as it builds a consumer app studio launching a product called Pyre in early July. That migration signals continued ecosystem interest in Base even as the network has faced recurring uptime issues.
Onchain data for the network remains publicly viewable via basescan.org, though the material provided does not detail the specific duration or root cause of the Unsafe Head Stall, nor confirm whether it has been fully resolved. What remains unresolved is whether these repeated stalls reflect a systemic issue in Base's block-production mechanism or a series of unrelated incidents coinciding with the network's upgrade schedule. It is also not yet known what remediation steps, if any, Base's operators have committed to following this latest disruption.