Base Post-Mortem: Sequencer Block Building Logic Bug Caused Two Outages, User Funds Safe

Base Post-Mortem: Sequencer Block Building Logic Bug Caused Two Outages, User Funds Safe

N
News Editor
2026-06-27 23:54:59
On June 25–26, the Base mainnet experienced two consecutive block production outages totaling over 136 minutes. Base’s engineering team published a post-mortem report identifying the root cause as a vulnerability in the sequencer’s block building logic that failed to clear stale log state after an invalid transaction validation, leading to gas accounting mismatches and invalid blocks that halted the chain. No chain integrity or user funds were affected. A patch has been deployed, and Base will enhance protocol fuzz testing and load testing to prevent recurrence.
Baseoutagesequencer bugL2block productionfund safetyLayer 2

Outage Overview: Two Block Production Interruptions

Between June 25 and 26, the Base mainnet — a Layer 2 network incubated by Coinbase — suffered two separate block production outages. According to the post-mortem published by Base engineering on June 27, the first incident occurred at 11:47 AM ET on June 25 and lasted 116 minutes; the second began at 11:28 AM ET on June 26 and lasted 20 minutes. Both outages shared the same root cause, and the chain’s integrity and all user funds remained secure throughout the events.

Root Cause and Remediation

The investigation revealed that the root cause was a vulnerability in the sequencer’s block building logic. When a transaction failed validation, the system did not properly clear its stale log state (which includes accessed accounts and storage slots). As a result, a subsequent valid transaction was executed against the uncleared log state, causing a mismatch in gas accounting. This produced a sequenced block containing an invalid state transition, which other nodes could not accept, bringing the chain to a complete halt. During the incident, Base was unable to produce new L2 blocks, and both the sequencer and validator nodes were stuck, preventing new transactions from being posted on-chain. The team deployed a patch to ensure the log state is correctly updated during execution, thus fixing the bug. Going forward, Base will strengthen its protocol fuzz testing and load testing tools to better identify adversarial transaction patterns that could expose similar vulnerabilities, and will continue to improve operational and monitoring capabilities.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
300

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.