Yellowstone gRPC streaming for Solana.
Yellowstone gRPC is the Geyser-based stream that pushes accounts, slots, and transactions to you the moment the validator processes them - one stream, server-side filters, no polling. rpc edge subscribes to the actual geyser port, not a downstream fanout.
50% OFFLaunch offer on Trader, from $249/mo. Paid onboarding support on request.
◆ OVERVIEW
Yellowstone gRPC is a streaming interface built on Solana's Geyser plugin port. Rather than polling an RPC endpoint, you open one long-lived gRPC stream and the validator pushes accounts, transactions, slots, and blocks as it processes them, filtered server-side.
Yellowstone is the widely-used gRPC implementation of Solana's Geyser plugin interface. Instead of polling an RPC endpoint, you open one long-lived stream, describe what you care about with filters, and updates arrive as the validator processes them.
rpc edge runs Yellowstone gRPC on nodes tuned for high-frequency streaming, co-located with the cluster - so you get live account and transaction state with minimal serialization overhead and proper backpressure under load.
Available on Trader from $249/mo.
◆ CAPABILITIES
What Yellowstone gRPC does.
Accounts, transactions, slots
Multiplex everything you need on one stream - account writes, transactions, slot transitions, and block metadata.
Server-side filters
Filter by owner program, account key, account inclusion, and more, so you receive only what's relevant - the work happens next to the data.
Backpressure built in
A streaming protocol that handles flow control properly, so bursts don't silently drop or buffer unboundedly.
Thousands of accounts, one connection
Subscribe to entire programs without the WebSocket fan-out that buckles past a few hundred subscriptions - one stream covers them all.
// one stream, server-side filters, processed commitment
const stream = await rpcedge.subscribe({
source: "geyser",
accounts: { amm: { owner: [RAYDIUM_AMM] } },
transactions: { swaps: { accountInclude: [RAYDIUM_AMM] } },
commitment: "processed",
});
for await (const update of stream) {
strategy.onUpdate(update); // pushed, not polled
}◆ WHY rpc edge
Latency is a location problem.
Subscribe instead of polling
Yellowstone gRPC pushes filtered account, slot, and transaction updates over one persistent stream, so your bot does not need to rebuild the same polling loop.
Choose the data your workload needs
Use standard RPC for state and history, Yellowstone gRPC for live validator updates, or preprocessed transactions when earlier intent matters to the strategy.
Start shared, move dedicated
Launch on a self-serve plan with included bandwidth. Move to private bare metal, regional placement, and an SLA when traffic or latency requirements justify it.
◆ USE CASES
- Market makers tracking live pool and account state
- Copy-trading and liquidation bots reacting in real time
- Indexers that need scale beyond WebSocket fan-out
Frequently asked questions
What is Yellowstone gRPC?
Why use gRPC over standard RPC or WebSocket?
Is anything faster than Yellowstone gRPC?
◆ GET ACCESS
Stream live Solana state, no polling.
Pick a plan and point your client at a scoped endpoint, or talk to the infra team to scope a dedicated, co-located node tuned to your latency and volume.
50% OFFLaunch offer on Trader, from $249/mo. Paid onboarding support on request.
GEYSER · gRPC
- Accounts, transactions, slots
- Server-side filters
- Backpressure built in
- Thousands of accounts, one connection