Solana gRPC (Yellowstone Geyser Plugin) FAQs

What is Solana gRPC?

Solana gRPC (Yellowstone-compatible Geyser gRPC) unlocks gRPC access to Solana's Geyser plugin. It enables high-performance, real-time data streaming for transactions, accounts, blocks, and other blockchain state changes. It provides a structured, low-latency alternative to traditional WebSocket and JSON-RPC API queries.

Quicknode previously enabled this feature only as the Yellowstone gRPC Geyser add-on. Since June 1, 2026 it is included with Scale and Business plans (See How do I get access to Solana gRPC? below).

How does Solana gRPC improve performance compared to standard Solana WebSockets?

Unlike traditional WebSockets, which require multiple subscriptions for different data types, Solana gRPC provides structured, batched streaming from a Geyser-enabled node. It uses HTTP/2 multiplexing for lower latency and optional zstd compression to reduce bandwidth usage, making real-time Solana data faster and more efficient. Additionally, Solana gRPC offers advanced server-side filtering, allowing users to limit unwanted response data and receive only the most relevant updates, further optimizing performance and reducing unnecessary data processing. For details on enabling zstd compression, see the zstd Compression documentation.

How fast does Solana gRPC deliver data?

The response time depends on network propagation between the leader validator (which sets the block timestamp) and the Geyser node. Since Solana uses a leader-based slot production system, the data is available on a Geyser node as soon as it propagates from the leader. In practice, this results in low-latency data streaming, but exact times vary depending on network conditions.

What kind of data can I access using Solana gRPC?

With Solana gRPC, you can access:

• Transaction Streams – Real-time updates for executed transactions as they are processed by the network.

• Block Updates – Notifications for new blocks, including their commitment status (Processed, Confirmed, or Finalized).

• Account Updates – State changes for specific accounts as they occur.

• Program Events – Logs emitted from on-chain programs during execution.

Is Solana gRPC better than using Solana WebSockets?

Solana gRPC offers more efficient data streaming, reduces connection overhead, and supports structured responses. Unlike WebSockets, which require separate subscriptions for different data types, Solana gRPC delivers batched updates within a slot, providing multiple account updates in real-time. WebSockets deliver a single update at the end of the slot.

However, WebSockets may still be suitable for simpler use cases, existing integrations that don't require high-performance data ingestion, or web applications that do not support gRPC.

Does this improve the reliability of my Solana data streams?

Yes. Solana gRPC benefits from structured gRPC streams that are inherently more stable than WebSockets, which can suffer from dropped connections and require reconnections. The structured nature of gRPC also improves efficiency for large-scale data consumers.

Who should use Solana gRPC?

Solana gRPC is ideal for developers and enterprises needing:

• High-performance real-time data ingestion.

• Structured, scalable data streaming.

• Low-latency transaction and account updates for trading, analytics, or dApps.

How do I get access to Solana gRPC?

Access depends on your Quicknode plan. This changed on June 1, 2026.

• Scale and Business: Solana gRPC is included at no add-on cost. It installs on your account automatically. Do not install the paid add-on.

• Build and Accelerate: Solana gRPC is not enabled by default. You must purchase the Solana gRPC add-on before you can stream. Upgrading to Scale is better value, because Scale includes gRPC, more credits and a higher RPS limit.

• Free trial: Solana gRPC is not available on any terms. Upgrade to Build or higher.

• Enterprise: your contract sets your limits. Contact your account manager.

You can read more about the product on the Solana gRPC page. For endpoint and token setup, see the Solana gRPC documentation.

Solana gRPC Limits by Plan

On Build and Accelerate, your paid add-on tier sets your limits. Manage the add-on from the Add-ons page in your Quicknode dashboard.

Is Solana gRPC free on Scale and Business?

The subscription is free. The data usage is not.

Scale and Business customers pay no add-on charge. You still pay for the data that you stream, at the metered rate of 10 API credits per 0.1 MB. This rate did not change on June 1, 2026.

I am on Scale or Business and I still pay for the add-on. What do I do?

Quicknode does not migrate you automatically. This protects your current setup from an unintended change.

1. Open your Quicknode dashboard.

2. Uninstall the Solana gRPC add-on.

3. The included version installs automatically.

Your service does not stop. The endpoint, your code and the regions stay the same. Only the billing line item changes.

Important: Contact Quicknode support before you uninstall if you subscribe to the $699 Velocity add-on tier. Uninstalling reduces your limits to 10 concurrent streams and 10 accounts per stream. Move to the Business plan first to keep your current limits.

Does this replace standard Solana RPC methods?

No. Solana gRPC is an enhancement, not a replacement. Traditional RPC methods remain available and useful for various applications. However, if you require faster, more structured, and scalable data streaming, gRPC is the recommended option.

What is the expected latency when subscribing to new block data?

When subscribing to new block data, the response time can vary between 0 milliseconds and 1.2 seconds due to network propagation. This delay occurs as the block is gossiped through the validator network before reaching all nodes, including those subscribed to real-time data streams.

The commitment level used in the subscription also affects response time:

• Processed: Fastest response time, up to 1.5s

• Confirmed: Moderate response time, between 3s to 5s

• Finalized: Longest response time, requires 32 blocks, average 15s

Why is using the gRPC block response timestamp for latency calculation not feasible?

Many people attempt to calculate latency by subtracting the block metadata timestamp from the gRPC block response timestamp. However, this approach is not feasible because the block timestamp is set by the leader validator node, and network propagation delays can introduce inconsistencies in response time. A more accurate approach is to measure network latency directly through alternative methods.