The primary keyword is NEAR 2.13.0 protocol upgrade. Radar frames the release as node, consensus and dapp-operations discovery rather than exchange trading news.
What Happened
The official nearcore 2.13.0 release notes mark a protocol and database upgrade and say protocol-version 86 voting starts Monday, July 20 at 00:00 UTC. They instruct consensus participants to upgrade beforehand, remove support for centralized external-storage state sync, stabilize gas keys and dynamic resharding, and document additional protocol changes. Bybit's July 17 support notice independently schedules its NEAR deposit and withdrawal suspension for July 19 at 11:30 p.m. UTC.
The event and source dates were checked on July 19, 2026 UTC. The cited primary source controls the schedule, contract action or protocol release.
Why It Matters
Radar readers need to distinguish release availability from successful protocol voting and activation. Validators using the retired ExternalStorage state-sync mode can fail on startup, while indexers, wallets and dapps should test receipt, gas-key, resharding and archival-query assumptions against the new node behavior.
This page provides decision context, not a pick, prediction or financial recommendation. Betting 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 price, lineup or interface state for the original evidence.
What To Watch Next
Watch validator adoption before the vote, protocol-version 86 voting, the expected activation epoch, node startup errors, state-sync configuration, RPC compatibility and exchange deposit/withdrawal restoration. Treat venue suspension as an operational signal, not proof that chain activation completed.
Recheck the official source and live surface before acting because probable starters, lineups, liquidity, venue support 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 source checks.
