Base restores mainnet withdrawals after a TEE enclave issue halted proposals

What happened

Base reported that a TEE enclave issue halted proposals and delayed Base mainnet withdrawals beginning May 29. The first-party status record marked the incident resolved on May 31.

What changed

The canonical exit path experienced a temporary operational delay because state proposals needed for withdrawal progression stopped advancing.

What did not change

The notice reported no bridge-contract exploit, fund loss, change to the seven-day challenge period, change to upgrade authority, or permanent withdrawal-mechanism modification.

Confirmed

• Base identified the incident on May 29, 2026 at 15:55 UTC.
• Base attributed the withdrawal delay to a TEE enclave issue that halted proposals.
• The incident affected Base mainnet withdrawals.
• Base marked the incident resolved on May 31, 2026 at 03:38 UTC.

Still open

• The root cause of the TEE enclave failure and the exact remediation deployed.
• The number and value of withdrawals delayed and their maximum additional completion time.
• Whether alternative proposer or proof paths were available and tested during the incident.
• The recurrence risk and any subsequent changes to proposer failover or monitoring.

What it means for an advisor

• Add proposer and TEE-enclave availability to the Base bridge operational-dependency review.
• Review withdrawal monitoring and contingency procedures for a proposal halt lasting longer than one day.
• Because Base reported recovery, the historical incident does not by itself justify a current restriction, but it requires memo and operating-runbook review.