The primary keyword is Celo op-reth node migration. Radar focuses on canonical-chain continuity, node bootstrap and dapp or indexer compatibility rather than the CELO market.
What Happened
Bybit's official July 21, 2026 notice scheduled a Celo network upgrade for 4:00 p.m. UTC that day and suspended Celo deposits and withdrawals from 3:30 p.m. UTC while leaving trading available. Celo's official forum says mainnet moves from op-geth to op-reth on July 22, 2026 and warns node operators that op-geth will not follow the canonical chain at activation.
The event and source dates were checked on July 22, 2026 UTC against the cited official pages.
Why It Matters
Radar readers operating nodes, bridges, indexers or tracing-dependent dapps need to test the client boundary. Celo says the old op-geth data directory does not carry over and calls for a fresh op-reth bootstrap from a published snapshot, while non-standard RPC consumers require explicit testing.
This is decision context, not a pick, prediction or financial recommendation. Betting, margin and crypto exposure can cause loss; incomplete confirmation is a reason to wait or pass.
Keep an audit note with the source URL, UTC check time, live condition and pass trigger. Do not substitute a later interface state for the original evidence.
What To Watch Next
Watch canonical head agreement, snapshot provenance, peer and sync health, archive completeness, debug and tracing RPC behavior, bridge relayers, indexer lag and incident channels. Keep rollback and traffic-shift plans until independent nodes agree.
Recheck the official source and live surface before acting because probable starters, lineups, service state, wallet routes and protocol state can change after publication.
The editorial filter is chain updates. Treat this as decision context, not as a prediction, recommendation or promotional note.
Date discipline matters: published and updated timestamps are generated at publish time in UTC, while event dates in the body come from the cited source.
Risk reminder: betting and crypto decisions can cause financial loss. Use official sources, keep stakes or position sizes controlled, and avoid treating one update as a complete strategy.
Before acting on the update, compare the official notice with the live product, market or protocol surface. If contract specs, fee terms, route availability, lineup status or governance details differ, the live source should override the older assumption.
The practical output is a watchlist, not a verdict. Readers should know which timestamp, rule, venue field or protocol dependency must be checked next before the update has any operational value.
Continue this cluster
Continue this cluster through owner-fit primary-source checks.
