No one realized that Base’s state update system had failed.

crypthub

about 3 hours ago

Base Outage Overview

A bug in Coinbase’s Base roll‑up halted the component that updates the L2 state on Ethereum for over 30 hours. Transactions and app interactions continued, and blocks were still produced, but state updates and withdrawals to Ether stopped. Developers noticed the issue after flagging the missing withdrawals, which are subject to a seven‑day challenge period.

Technical Cause and Impact

The failure traced to Base’s Trusted Execution Environment (TEE) enclave, which halted the proposal system that generates cryptographic attestations for state commitments. While the L2 kept processing transactions, the settlement pipeline to Ethereum was frozen. No funds were lost and user assets remained safe, but a vital infrastructure piece was temporarily inoperative.

Broader L2 Implications

The incident raises concerns about the resilience of Ethereum’s growing Layer‑2 ecosystem, especially after Base’s recent “Azul” upgrade aimed at 5,000 tps scalability. Earlier delays during high traffic showed capacity limits, but this bug highlighted a different failure mode that can pause finality without halting user activity.

Comparison with Sui

Sui experienced a six‑hour consensus failure in January, stemming from validator and gas‑accounting bugs, which also froze transfers, DeFi, and NFT transactions. Unlike Base’s TEE‑related issue, Sui’s outage was a consensus problem, illustrating varied technical risks across blockchain platforms.