# Base recovers from consecutive mainnet chain stalls

> The incident established a realized chain-availability failure affecting deposits, withdrawals, block production, and client software. Node operators were required to restart affected nodes to resume syncing, and the halt recurred the following day.

- URL: https://riadefi.com/on-chain/2026-06-25-coinbase-bridge-base-mainnet-chain-stall/
- Type: Market stress
- Stage: Recovery reported
- Evidence: confirmed
- Materiality: material
- Event date: 2026-06-25
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Advisor-relevant: yes
- Affects: Base canonical bridge (protocol)

## What happened

Base mainnet block production stalled on June 25 after a consensus problem allowed a problematic block to interfere with subsequent block building. A similar chain halt recurred on June 26 before Base reported block production progressing and the incident resolved.

## What changed

The incident established a realized chain-availability failure affecting deposits, withdrawals, block production, and client software. Node operators were required to restart affected nodes to resume syncing, and the halt recurred the following day.

## What did not change

The status record did not report a canonical-bridge contract exploit, asset loss, or chain reorganization. It did not include the promised detailed postmortem or enough evidence to verify that the root cause could not recur.

## Confirmed

- The June 25 disruption prevented new blocks after block 47,806,542.
- Base identified a consensus problem involving an invalid or problematic block.
- Sequencing resumed, but affected ecosystem nodes required restart and resynchronization.
- A similar chain halt occurred on June 26.
- The incident record lists deposits, withdrawals, block production, and client software as affected and reports final resolution on June 26.

## Still open

- The complete technical root cause and the mechanism behind the next-day recurrence.
- The permanent remediation, deployment evidence, and testing showing the fault cannot recur.
- The duration and transaction-level impact of deposit and withdrawal unavailability.
- Whether any nodes, indexers, or bridge-dependent services remained impaired after the status page was resolved.

## What it means for an advisor

- Review the Base canonical-bridge memo's chain-availability and withdrawal-access assumptions against two realized stalls.
- Record that deposits and withdrawals can become temporarily unavailable during Base sequencing failures even without a bridge-contract exploit.
- Obtain the promised postmortem and verify permanent remediation before treating recovery as evidence of reduced operational risk.

## Sources

1. [Base Mainnet Chain Stall](https://status.base.org/incidents/5c4gm1wzbjs4) · Base · 2026-06-26


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.