⚡Solana gRPC Docs

gRPC geyser 101: Low-Latency Streaming of Solana Transactions, Accounts, and Blocks

A geyser plugin on Solana allows you to push real-time updates from a Solana RPC node to an external source. Yellowstone gRPC is one such high-performance Solana Geyser plugin that allows you to stream real-time blockchain data via gRPC interfaces. This powerful tool enables developers to:

• Monitor on-chain activities: Track token mints, program interactions, and state changes.

• Stream account states: Efficiently retrieve account information.

• Stream transactions: Monitor transactions with minimal latency.

• Indexers: Build indexing pipelines

In short, this can be used to build applications that can respond quickly to changes on the blockchain.

Resources and Replits on Shyft gRPCs

We have developed multiple sample code covering top use cases for gRPC. They run out of the box, are in multiple languages (Typescript, Rust and python) and help you get started quickly. You can explore them here

• Shyft GitHub

• Shyft Replit

• Shyft Blogs

You can also join Shyft's discord for support and more resources.

Unlike regular RPCs which are used to interact with the Solana blockchain by sending HTTP POST requests, gRPCs are only used for streaming real-time updates on Solana with minimum latency.

Authentication

There are two ways to authenticate your server or connection when connecting to Shyft’s gRPC network:

1. Using X-Token:

x-token is available in the gRPC section of the dashboard

After purchasing the gRPC service on Shyft, you can find your x-token in the gRPC section of your Shyft dashboard. This token is used to establish a gRPC connection through the Yellowstone client. The advantage of this method is that it doesn’t require IP whitelisting.

const client = new Client(
  <YOUR-GRPC-ENDPOINT>,
  <YOUR-X-TOKEN>,
  undefined
); //initializing yellowstone client

1. By Whitelisting Your IP:

We recommend using token for authentication. Use IP whitelisting only when you cant use token authentication.

In certain scenarios, like when setting up bots, you may need to connect directly to the gRPC network via the gRPC URL without x-token. In such cases, you’ll need to whitelist your server’s IP address (the one used to receive streamed data). Once the IP is whitelisted, you can connect directly using the URL without needing an x-token. IP whitelisting can be easily managed through the gRPC section of the dashboard.

Whitelist your server IP to directly use without X-TOKEN

Please note, gRPC connections can be made from any IP address using x-token. Once an IP address is whitelisted, x-tokens are no longer required for connection from that IP.

What are gRPC Subscribe Requests?

Real-time updates in Solana’s Yellowstone gRPC plugins rely on Subscription streams. These streams let you receive updates like account changes, transactions, new blocks, or slot updates directly to your backend. To keep things focused and avoid unnecessary data, a subscription request lets you specify different kind of filters. using these filters you can specify exactly what type of updates you need.

Subscribe requests on gRPC look somewhat like this.

import { CommitmentLevel } from "@triton-one/yellowstone-grpc";

const req: SubscribeRequest = {
  accounts: {},
  slots: {},
  transactions: {},
  transactionsStatus: {},
  entry: {},
  blocks: {},
  blocksMeta: {},
  accountsDataSlice: [],
  ping: undefined,
  commitment: CommitmentLevel.CONFIRMED,
};

Most of the request parameters here are self-explanatory, working exactly with what they are named,

• accounts: You can subscribe to specific accounts (e.g., SOL-USDC OpenBook) by specifying this parameter and receive updates based on commitment levels (processed, confirmed, finalized).

• accountDataSlice: This field helps you to filter your gRPC stream, so that you receive only the relevant portion of streamed data. For example you are streaming accounts, for which the data size is 200bytes, but you only need 40 bytes after a certain offset. This field can help you filter those 40 bytes for every update in the stream.

• transactions & transactionsStatus: You can receive updates on all transactions or filter them based on specific criteria (vote/failed transactions, including/excluding accounts). Programs can also be monitored using this.

• slots, blocks & blocksMeta : Stay informed about new blocks and slots being produced on the blockchain.

• commitment: This specifies the commit level for any update, either processed, confirmed or finalized.

FAQ

How is Solana gRPC different from Websockets?

WebSockets transmit JSON over HTTP and are easier to implement for quick integrations, while gRPC streams use Solana’s Geyser plugin system to push real-time transactions, accounts, and blocks with minimal overhead. This makes gRPC ideal for high-throughput performance applications like trading bots, market makers, and analytics platforms, whereas WebSockets are better suited for lighter, less latency-sensitive use cases.

How do I connect to a Yellowstone gRPC endpoint?

To connect to a Yellowstone gRPC endpoint, you need:

1. A gRPC endpoint URL – This is the address your client will connect to.

2. A Yellowstone-compatible gRPC client – Choose one in your preferred programming language (Rust, Node.js, etc.).

For Shyft Yellowstone gRPC, you’ll also need an x-token for authentication. The connection URL and x-Token are included in any gRPC-enabled Shyft plan.

Please refer to our connections and authentication docs here.

What data can I stream using Solana gRPC?

With Solana gRPC, you can subscribe to:

• Transactions – Detailed transaction data, including instructions, logs, and status.

• Accounts – Live updates on account state changes.

• Blocks – Newly produced blocks with transaction metadata.

  These streams are ideal for bots, trading engines, real-time dashboards, and analytics platforms.

How do I parse raw Solana transaction data from Yellowstone gRPC?

Raw transaction data streamed from Solana Yellowstone gRPC is typically in a base64 or binary-encoded format. To convert this into human-readable form, you can use the corresponding program’s IDL (Interface Definition Language) or a custom parser to decode the instructions, accounts, and logs.

Our developer documentation and GitHub examples cover step-by-step methods for:

• Decoding transactions using Anchor IDLs.

• Parsing data from popular Solana programs such as System Program, Token Program, and Associated Token Program.

• Extracting structured data from DEX trades, DeFi protocols, and custom programs.

Explore examples: Visit our Docs and GitHub repository for complete code samples on receiving and parsing Solana transactions via Yellowstone gRPC.

Are there any rate limits for Solana Yellowstone gRPC streaming?

Yes. Shyft Yellowstone gRPC offers different subscription tiers, each with its own rate limits for streaming transactions, accounts, and blocks from Solana in real time. Higher tiers provide increased throughput, concurrent streams, and data retention options to support enterprise-grade workloads. Also certain high load programs, (such as the token program) is only allowed on Dedicated Nodes.

Check our pricing and rate limit documentation to choose the plan that matches your Solana data streaming needs.

How are Dedicated gRPC Nodes better than Shared gRPC plans?

Solana Dedicated Nodes deliver a latency advantage of 5–10ms over shared nodes, making them ideal for high-frequency trading, real-time analytics, and low-latency DeFi applications. Unlike shared nodes, they are exclusively allocated to you, with no rate limits and no access restrictions on high-load Solana addresses. Each dedicated node is load-balanced across a cluster of backup nodes, ensuring 99.99%+ uptime and uninterrupted access to the Solana blockchain. Learn More.

Why am I getting Maximum IP limit reached for token error?

• Base $199/mo subscription gives you access to connect from one IP. If you connect from multiple IPs, you will get this error.

• You can also get this when you change your server and the connection was not gracefully shutdown. In those cases you can clear your previous connection through this link https://grpc.ams.shyft.to/clear-connections?xtoken=your-token Add your token in the end, grpc region doesnt matter.

Why is lag building up over time with gRPC?

If you notice that over time ag starts to build up, then there are two possible reasons.

• Your server is far away from the gRPC region you are connecting to. For example, if you are connecting to grpc.ams.shyft.to, your server should also be in the same region i.e Ams. We have seen cases where lag starts to build up over time if the server is far away. Its acceptable if ping < 10ms, although some users would want it to be less than 1ms.

• Another reason is that typescript sometimes is not able to keep up with gRPC speed. We suggest using Rust gRPC client for fastest processing. We have some sample codes in our Github repo and Replit.

• Don't use VPNs.

• At anytime you can verify the current slot of all our regions here.

Why am I getting the following error message, “PermissionDenied, message: "Maximum connection count reached for IP address”?

This indicates you have the grpc rate limits for your plan, please checkout the details here.

How do I check if any gRPC region is lagging or not?

We have a public dashboard where you can see lag of all gRPC regions in our network. We compare it against Solana mainnet-beta. You can access it here.