Solana Foundation Announces RPC 2.0
The Solana Foundation is working on RPC 2.0 — a new read layer for the Solana RPC interface. Standardization of many previous provider extensions is being pursued.
What the Solana Foundation Announced
The Solana Foundation has announced RPC 2.0 as a focus area for the coming months. RPC stands for Remote Procedure Call — the interface through which wallets, dApps, indexers, and bots communicate with the Solana network.
Source: @SolanaFndn on X. A concrete technical specification has not yet been published.
What RPC 2.0 Aims to Address
According to the Foundation announcement, three areas are in focus:
- Latency — faster responses on standard queries
- Cost — more efficient data delivery for RPC providers
- Query expressiveness — bundling complex queries that previously required multiple calls into one request
Which concrete endpoints or methods will be changed is still open.
Context of the Current RPC Ecosystem
Several RPC providers have built their own “Enhanced APIs” over recent years because standard RPC has not been sufficient for modern applications. The largest:
- Helius — Enhanced Transactions, DAS API, Webhooks
- Triton One — RPC with Stake-Weighted QoS
- QuickNode — RPC with additional indexing features
RPC 2.0 could standardize parts of these provider extensions at the protocol level.
What to Watch
- When the Solana Foundation publishes a detailed RFC or SIMD
- How RPC providers respond to standardization (competition or adoption of the new APIs)
- Whether RPC 2.0 ships with the Anza/Agave release cycle or as a Foundation-driven spec
Source
- Solana Foundation on X — @SolanaFndn
- Solana Improvement Documents (SIMDs) — github.com/solana-foundation/solana-improvement-documents