NEAR dynamic resharding upgrade set for June 2026 lifts NEAR 27%–30%
NEAR Protocol announced dynamic resharding as part of network upgrade 2.13, scheduled for June 2026. The change automatically splits overloaded shards once shard capacity thresholds are hit, reducing the need for manual validator coordination and lengthy governance votes—an evolution of Near’s Nightshade sharding roadmap.
Traders reacted immediately. NEAR jumped about 27%–30% in 24 hours to around $2.24–$2.27, making it a top performer among large-cap tokens. The rally also coincides with demand signals from Bitwise’s Near Staking ETP, which reportedly brought in roughly $7M this week.
Key technical additions: the June release also includes post-quantum-safe signing (quantum-resistant signatures) and supports higher, unpredictable transaction demand via NEAR Intents. Longer-term scaling targets point beyond 70 shards, following prior increases in shard count (6 → 8 in Mar 2025, then to 9 later in 2025).
Risks remain ahead of the upgrade. With execution and testnet risk still unresolved, any timing slip, bug, or rollout delay could trigger profit-taking after the current momentum run.
For positioning, watch NEAR dynamic resharding as the core catalyst, and monitor continued ETP/ETP inflows plus market risk around June upgrade milestones.
Bullish
This news is bullish for NEAR itself because it combines a clear, trader-friendly catalyst (NEAR dynamic resharding in June 2026) with immediate positive price momentum and supportive institutional/ETP flow context. The automatic shard-splitting narrative directly addresses scaling friction, which typically boosts sentiment for Layer-1 ecosystems.
Short-term, the market may continue to reward the upgrade expectation, especially if ETP/ETP inflows persist and the token holds above the recent breakout zone ($2.24–$2.27). Even without the upgrade live yet, traders often “front-run” roadmap milestones when they are concrete and technically specific.
Long-term, post-quantum-safe signing and NEAR Intents reinforce a broader positioning beyond scaling—potentially improving user-security perception and handling of bursty demand. However, because the upgrade is still ahead, there is also a pullback risk if testnet issues or schedule slippage emerge. Overall, the current setup favors continuation bias until the execution risk starts to materialize.