Developing. Some claims here are not yet confirmed, and they are listed apart from the confirmed facts. Ketju publishes a new version when the primary evidence changes.
Affects: Base canonical bridge (protocol)
What happened
Base reported slower transaction inclusion on November 2, 2026, and announced a fix at 14:55 UTC.
What changed
Base users could wait longer for transactions to enter a block or receive preconfirmation. Base deployed optimizations while investigating the degradation.
What did not change
Base reported continued normal block production. Its notice establishes no bridge exploit, asset loss or change to withdrawal rules.
Confirmed
- Base began reporting the incident at 13:36 UTC on November 2, 2026.
- Base identified performance degradation and reported optimizations at 14:36 UTC.
- Base reported deploying a fix at 14:55 UTC while continuing to assess results.
Still open
- Base’s supplied notice contains no final resolution or confirmed recovery time.
- Base did not quantify the transaction delays or identify their effect on individual bridge withdrawals.
- Base did not establish censorship or a breach of the documented forced-inclusion window.
What it means for an advisor
- Ketju should track resolution against the Base bridge memo’s operational assumptions.
- Advisors should confirm transaction inclusion when evaluating the timing of a holder’s bridge withdrawal.
Sources
- Delayed transaction inclusion on Base Mainnet · Base · · effective
Version 1, published . We check this event again on . Educational research. Not investment advice.