[Base Status Update Stalled for Over 30 Hours Due to TEE Enclave Malfunction, Withdrawal Delays Reported] According to Deep Tide TechFlow on May 30, developer donnoh disclosed that a vulnerability during a recent upgrade has caused the Base network's status updates to stall for over 30 hours. However, since withdrawals from Base to the Ethereum mainnet inherently require an approximately 7-day challenge period, most regular users have not yet noticeably experienced the anomaly. Subsequently, Base's official status page released an announcement confirming that the issue stems from a malfunction related to the TEE (Trusted Execution Environment) enclave, which disrupted the network proposal process and, in turn, affected the status update progress. The official statement noted that withdrawal functionality on the Base mainnet is currently experiencing delays, and the team is actively working on a fix. Aside from the withdrawal process, other core network components have not been directly impacted for now. This incident has once again sparked community discussions about the stability of Layer 2 infrastructure and the risks associated with TEE dependency. Since Base employs an Optimistic Rollup architecture, even in the event of status update anomalies, the user asset security mechanisms and challenge period design can still provide a certain degree of buffer.