Deep Dive
1. Q4 2026 Core Infrastructure Upgrades
Overview: NEAR’s roadmap lists external contract calls, a 21-operator multi-party computation (MPC) network, networking changes, post–quantum account features, and trusted execution environment (TEE) enforcement for Q4 2026. MPC lets multiple operators jointly produce a signature; TEEs isolate computation. The timeline marks some items underway and others not started, so delivery by quarter-end is not assured.
What this means: This is bullish for NEAR because these upgrades could improve connectivity, resilience, and privacy for applications. Delays or security issues could limit those benefits.
2. SPICE and Heterogeneous TEE Launches (Q1 2027)
Overview: The roadmap targets SPICE V1 mainnet and heterogeneous TEEs in Q1 2027 (roadmap). SPICE is a planned protocol upgrade; heterogeneous TEEs allow different trusted hardware environments to support confidential computing. These could help users and developers access faster or more private services, but the listed timeline is a target, not a guarantee.
What this means: This is bullish for NEAR because successful delivery could strengthen performance and privacy use cases. Adoption will depend on reliability, developer support, and real usage.
3. Single-Block Cross-Shard Transactions (Q2 2027)
Overview: NEAR lists single-block cross-shard transactions for Q2 2027 (roadmap). Shards are parallel parts of the network; completing transactions across them in one block could simplify multi-part actions and reduce waiting. The roadmap does not establish a guaranteed release date.
What this means: This is bullish for NEAR because smoother cross-shard activity could improve the user experience and application composability. Technical complexity and safe deployment remain key risks.
Conclusion
NEAR’s stated priorities move from infrastructure and security work in Q4 2026 toward confidential computing and faster cross-shard activity in 2027; delivery and adoption will determine their impact. Which milestone would you like to examine in more detail?