Base recovers from a batching-related safe-head delay

What happened

Base reported that mainnet safe head trailed unsafe head because of batching-performance problems. Deposits and withdrawals were affected before batches resumed and the incident was resolved.

What changed

Safe-head progression and timely L1-backed confirmation were impaired from 14:40 UTC until resolution at 18:09 UTC.

What did not change

Base reported no asset loss, bridge exploit, custody change, role change, or modification to withdrawal and fault-proof rules.

Confirmed

• Base identified batching performance as the cause.
• Deposits and withdrawals were listed as affected.
• Safe-head advancement recovered the same day.

Still open

• The number and duration of delayed bridge transactions.
• The precise root cause and durable remediation.
• Recurrence risk after a separate May 21 safe-head lag.

What it means for an advisor

• Review batching and safe-head assumptions in the Base bridge memo.
• Retain fee, retry, alternate-RPC, and confirmation-monitoring procedures.