A bug within Coinbase’s Base froze a critical part of its network infrastructure. This raises new questions regarding the resilience of Ethereum’s ever-growing Layer 2 ecosystem. However, this issue did not prevent users from submitting transactions or interacting with applications on Base.
Blocks reportedly continued to be produced and the network appeared to be functioning normally. However, behind the scenes, a critical component responsible for updating the state of Base on Ether went down for more than 30 hours. This event was noticed after the developer flagged that state updates and withdrawals to Ether were stopped.
Base 30-hour outage raises layer 2 concerns
Developer donnoh.eth addressed this issue in an X post. He noted that the outage went unnoticed because Base’s withdrawal already requires a seven-day challenge period.
He said, “It’s kind of crazy that base state updates have been down for over 30 hours due to a bug related to a recent upgrade. No one noticed, just because withdrawals take 7 days anyway.”
According to the Base status page, the issue was traced to the network’s Trusted Execution Environment (TEE) enclave. This malfunction prevented the proposed system from generating the state updates needed to anchor Base’s activity to Ethereum.
The chain continued processing and moving transactions successfully. Meanwhile, Base State has effectively halted updates until the issue is resolved.
For rollups like Base, the transition is performed at L2 before the compressed state commitment is periodically posted back to Ether. TEE helps generate encryption certificates. This helps prove that the state transitions were calculated correctly.
This suggests that users can continue trading at Layer 2 even if the system stops working. Meanwhile, the payments pipeline that connects the network to Ethereum could be down.
There was no loss of funds, and the outage did not expose any user assets to theft. However, one of the most critical infrastructure supporting the rollup was still temporarily frozen. This is significant because it happened just a few days after Base rolled out the Azul upgrade. It is reportedly designed to improve scalability and increase throughput to 5,000 transactions per second.
Nevertheless, the network found itself struggling.
Base and Sui face different failure modes
Earlier this year, Base experienced periods of transaction delays during periods of high network activity. However, these issues did not interrupt the settlement. However, as usage continued to increase, capacity constraints became apparent.
Base is not alone in facing this problem. Sui reported a consensus failure in January that disrupted transaction processing for about six hours. The network experienced multiple outages related to software bugs that occurred during protocol upgrades. Temporarily freeze money transfers, DeFi activities, and NFT transactions.
The technologies involved behind these incidents vary widely. A base outage occurred with a TEE-supported proof mechanism. On the other hand, Sui’s problems arose from validator consensus and gas accounting logic.
