Loading prices…
🩸BEARISH

Base Mainnet Stalls as Consensus Bug Halts Block Production

The invalid block stopped production at height 47806542, taking deposits, withdrawals, and client software offline before partial sequencer recovery.

Base identified a consensus issue that caused an invalid block to be sequenced, halting new block production at height 47806542 and disrupting mainnet deposits, withdrawals, block production, and client software. The Base team confirmed internal sequencer and nodes had preliminarily recovered as engineers worked to restore full block propagation and continue root cause analysis.

Why it matters

A consensus-layer stall on a top-five L2 by TVL is not a routine node hiccup. If the sequencer accepts an invalid state transition, downstream reorg risk, withdrawal finality delays, and bridge attestation mismatches all enter the picture until a coordinated fix ships. The incident also surfaced the structural fragility of a single-sequencer architecture: when the sequencer goes dark, deposits and withdrawals freeze across every app built on top.

Market impact

Base activity grinds to a crawl during stalls like this, dragging DEX volume, bridging flows, and on-chain settlement into queue. Until full block propagation resumes and the root cause lands in a post-mortem, the market will read every delayed withdrawal as a tail-risk reminder of how centralized L2 execution really is.

Source: [Base Mainnet Chain Stall](http://status.base.org/incidents/5c4gm1wzbjs4)

Related tokens
$ETH

Frequently asked questions

  1. What caused the Base mainnet stall?

    Base identified a consensus issue that caused an invalid block to be sequenced, which halted new block production at block height 47806542.

  2. When did Base block production resume?

    Internal sequencer and nodes have preliminarily recovered, but block propagation was still being restored at the time of the update.

  3. Did deposits and withdrawals go down on Base?

    Yes. The stall disrupted mainnet deposits, withdrawals, block production, and client software until partial recovery.

  4. Is Base a centralized L2?

    Base runs a single-sequencer architecture, which keeps execution fast but means a sequencer-level consensus bug can freeze activity across the entire L2.

  5. What happens next for Base?

    Engineers are restoring full block propagation and continuing root cause analysis, with a post-mortem expected once the fix ships.

Source attribution
Aggregated from WuBlockchain · Verified · Last refreshed 1h ago
Open original →