The status update for the Base TEE enclave fault has been stalled for over 30 hours, causing delays in withdrawals.

Deep Tide TechFlow News, May 30th, according to developer donnoh's disclosure, due to vulnerabilities that appeared during recent upgrades, the status update of the Base network has been halted for over 30 hours. However, since withdrawals from Base to the Ethereum mainnet require a roughly 7-day challenge period, most ordinary users have not noticeably perceived this anomaly.

Subsequently, the official Base status page released an announcement confirming that the issue was caused by a fault related to TEE (Trusted Execution Environment) enclave, leading to a disruption in the network proposal process, which in turn affected the status update process.

The official stated that currently, the withdrawal function on the Base mainnet has experienced delays, and the team is actively working on a fix. Aside from the withdrawal process, other core network components have not been directly affected.

This incident has once again sparked community discussions about the stability of Layer 2 infrastructure and the risks associated with TEE dependency. Since Base uses an Optimistic Rollup architecture, even if status updates encounter anomalies, the security mechanisms for user assets and the challenge period design can still provide a buffer to some extent.