TL;DR:
- A technical glitch in Base’s infrastructure froze its state updates on the Ethereum mainnet for more than 30 hours.
- Internal transaction processing and block creation within the layer-2 did not suffer disruptions during the incident.
- The vulnerability originated in the Trusted Execution Environment (TEE) enclave following the implementation of the recent Azul upgrade.
The layer-2 network Base suffered a long outage in its critical infrastructure that affected data synchronization with the Ethereum mainnet, an incident that went unnoticed by most users over the weekend.
An infrastructure glitch in layer 2
Block production on the network continued normally and users maintained the ability to send transactions and interact with decentralized applications. However, the component responsible for consolidating Base’s state within Ethereum remained inactive for more than 30 hours. The developer known as donnoh.eth noted on his X account that the event did not raise immediate alarms because fund withdrawals on this type of scalability network already involve a mandatory seven-day challenge period.
According to Base’s official status page, the source of the problem was located in the Trusted Execution Environment (TEE) enclave. This section of the system is responsible for generating the cryptographic attestations that prove the correct computation of transactions in the second layer. Official protocol documentation indicates that the failure in this module temporarily prevented the proposal system from anchoring Base’s activity to the mainnet.
The platform confirmed that no funds were compromised and no user assets were exposed to potential theft during the incident. The halt in state updates occurred just a few days after Base developers implemented the Azul upgrade. According to the firm’s previous technical reports, this structural modification aimed to optimize the ecosystem’s scalability and raise the theoretical processing capacity up to 5,000 transactions per second.
Vulnerability patterns in blockchain networks
Previously, Base had recorded delays in transaction processing during peaks of high activity in the first quarter of the year. Those previous episodes exposed capacity limitations in the face of increased user flow, although on none of those occasions was the final settlement of blocks halted.
Base’s technological situation shows different dynamics compared to the consensus problems experienced by other networks in the sector. For instance, the Sui blockchain reported a failure in its consensus mechanism that paralyzed transaction processing for nearly six hours in January. Reports from that network attributed the crash to software bugs introduced into the gas-accounting code during a validator upgrade.
Industry analysts associate Base’s stagnation with the inherent challenges of TEE-assisted proving mechanisms in rollups. When these secure environments fail, internal processing on layer 2 can remain active while the settlement channel with the base network grinds to a complete halt. The Base development team is scheduled to publish a detailed post-mortem report to analyze validator resilience metrics during the deployment of emergency patches.
