Base network experienced a consensus issue on June 25 that halted block production entirely after block 47806542, disrupting mainnet deposits, withdrawals, and client software operations. The Coinbase-incubated Layer 2 network stopped producing new blocks when an invalid block entered the sequencing pipeline, preventing nodes from reconciling and advancing the chain. The incident occurred on the same date Base had scheduled its Beryl network upgrade for mainnet activation, marking one of the most disruptive technical failures the network has faced since launch.
Invalid Block Sequencing Freezes Base Chain at Block 47806542
Base identified a consensus issue that caused an invalid block to enter the sequencing pipeline on June 25. Once that block landed, the network could not produce new blocks beyond block 47806542. Nodes that disagreed on the validity of that block could not reconcile and move forward, effectively freezing the chain's tip. The sequencer, responsible for ordering and submitting transactions to the network, found itself unable to advance past the problematic block.
The Beryl network upgrade — which introduces the B20 native token standard and cuts Ethereum withdrawal delays from seven to five days — had been scheduled for June 25 mainnet activation. The consensus issue hit on that same date, creating a complete halt during what was intended as a milestone moment for the network.
Mainnet Deposits and Withdrawals Disrupted During Outage
Mainnet deposits and withdrawals were disrupted, preventing users from moving funds into or out of the network normally. Block production stopped, freezing on-chain state. Client software was also affected, meaning node operators and developers relying on Base's infrastructure faced compounding issues beyond the chain itself.
Coinbase users reported experiencing transaction delays on the Base network during the incident. The disruption touched deposits, withdrawals, block production, and client software simultaneously, reflecting how a sequencer-level or consensus-level failure can ripple through a Layer 2 stack.
Base Team Reports Partial Sequencer Recovery
The internal sequencer and nodes have partially recovered, stabilizing part of the network's infrastructure. Work to restore complete block propagation was ongoing at the time of reporting. The Base team had not provided a timeline for when the network would return to normal operations.
The root cause of the consensus issue has not been identified. The team confirmed it is actively investigating what triggered the invalid block to enter the sequence. Until that question is answered, the risk of a similar disruption cannot be fully ruled out.
FAQ
What caused Base mainnet block production to stop on June 25?
Base identified a consensus issue that caused an invalid block to be sequenced, which prevented new blocks from being produced after block 47806542.
Which mainnet functions were affected by the Base outage?
The outage disrupted mainnet deposits, withdrawals, block production, and client software operations. Coinbase users reported experiencing transaction delays on the Base network.
Has the Base network fully recovered from the block production halt?
The internal sequencer and nodes have partially recovered, but work is ongoing to restore full block propagation. The root cause of the consensus issue is still under investigation by the Base team.
