Base Network Stalls After Invalid Block Freezes Sequencer

What Occurred

The incident started at 16:03 UTC on June 25, 2026, when Base engineers detected unhealthy block manufacturing on the community’s mainnet. By 16:52 UTC, the staff had recognized the foundation trigger: a consensus drawback induced the sequencer to supply an invalid block, particularly block #47,806,542, which then interfered with all subsequent block constructing.

In OP Stack terminology, the occasion is assessed as an “unsafe head stall.” Meaning the sequencer stopped advancing new blocks fully. The unsafe head refers back to the newest sequencer-produced blocks that haven’t but been posted to Ethereum’s layer one (L1) for finalization.

Timeline:

• 16:03 UTC: Block manufacturing flagged as unhealthy; investigation begins.
• 16:52 UTC: Engineers establish block #47,806,542 because the problematic supply.
• 17:21 UTC: Consensus problem remoted; inner sequencer and nodes present preliminary restoration.
• 17:51 UTC: Block sequencing resumes; inner nodes start syncing appropriately.
• 17:58 UTC: Blockbuilding confirmed wholesome; community enters monitoring section.

What It Means for Customers

Deposits, withdrawals, and transactions on Base had been delayed in the course of the roughly two-hour stall. Node operators working Base infrastructure might want to restart their nodes to totally get better syncing.

Funds aren’t in danger. Unsafe head stalls happen earlier than blocks are batched and submitted to Ethereum L1, so there is no such thing as a publicity to everlasting loss or significant chain reorganizations.

Beryl Improve Nonetheless on Monitor

The incident coincided with the scheduled Beryl laborious fork, deliberate for an 18:00 UTC activation window on the identical day. Base confirmed the stall is unrelated to the improve.

Beryl introduces B20, a local token commonplace constructed immediately into node software program quite than deployed as a good contract, making token issuance extra environment friendly for stablecoins and real-world asset tasks. The improve additionally reduces withdrawal delays and ships Reth V2 enhancements. Node operators should run base/ node v1.1.1 or later. Most customers and current contracts require no motion.

What Comes Subsequent

Base engineers are persevering with to analyze the foundation reason for the invalid block and plan to publish a full autopsy as soon as the assessment concludes. The standing web page at standing.base.org and block explorer basescan.org stay the first monitoring assets.

Unsafe head stalls of this sort have occurred beforehand on different layer two networks and Optimism mainnet, typically tied to inner infrastructure circumstances, L1 node points, or load-related elements. This incident lasted roughly 115 minutes earlier than sequencing resumed.