GEYSER · gRPC

Yellowstone gRPC streaming for Solana.

Geyser-based gRPC that pushes accounts, slots, and transactions to you the moment the validator processes them - one stream, server-side filters, no polling.

Get started →◢ Join the community

Read the Yellowstone gRPC docs →

◆ OVERVIEW

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.

yellowstone-grpc.scope STREAMING

// live account & transaction stream - illustrative

◆ CAPABILITIES

What it 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.

Tuned for HFT

Performance-optimized nodes co-located with the cluster, so updates reach you with the fewest hops possible.

subscribe.ts
// 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.

01

Co-located by design

Our nodes are racked beside Solana stake clusters and the Jito Block Engine. Fewer hops, less distance, lower latency - physics, not promises.

02

Shreds from many sources

We aggregate shreds across multiple upstreams and serve whichever arrives first - so you never wait on a single point of delay.

03

Tuned for HFT

Every node is performance-optimized for high-frequency streaming - kernel, network stack, and RPC layer, end to end.

◆ 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

◆ RELATED

Frequently asked questions

Why use gRPC over standard RPC or WebSocket?
Standard RPC is pull-based and WebSocket subscriptions don't fan out gracefully to thousands of accounts. A single Yellowstone gRPC stream multiplexes everything with server-side filtering and backpressure, so you react to live state without polling lag.
Is anything faster than Yellowstone gRPC?
Yes - decoding transactions directly from shreds reads one layer further upstream, at the propagation layer, before any block is assembled. Most teams run both: gRPC for live state, shreds for first-seen signal.

◆ GET ACCESS

Put Yellowstone gRPC on your strategy.

Start free, or talk to the infra team to scope a dedicated, co-located setup tuned to your latency and volume.

Get started →◢ Join the community

GEYSER · gRPC

  • Accounts, transactions, slots
  • Server-side filters
  • Backpressure built in
  • Tuned for HFT