Solana Yellowstone gRPC
Live Solana state — accounts, txns, slots, blocks — over Triton-compatible Yellowstone gRPC. p99 ~3.8 ms from Frankfurt.
- Triton/Yellowstone-compatible (same protobuf + subscribe API)
- Accounts · txns · slots · blocks, server-side filters
- Unlimited, unmetered throughput
- Per-stream filter caps scale with tier
- Full Block Streaming add-on
- gRPC p99 latency
- 3.8 ms (60-min, Frankfurt)
- Region
- Frankfurt — NTT FRA2 on DE-CIX
- Concurrent connections by tier
- FOCUS 1 → PROFESSIONAL 50
- account_max per stream
- FOCUS 50 → PROFESSIONAL 2,000
- Throughput
- unlimited, unmetered
- Re-subscribe rate
- up to 10 / second
- Full Block add-on
- optional, on any gRPC bundle
Is Supanode gRPC compatible with existing Yellowstone clients?
Yes. It is a drop-in replacement for Triton clients — same protobuf schemas, same subscribe API. Point your existing SDK at our endpoint and keep your code.
How is gRPC throughput billed?
Throughput is unlimited and unmetered — there is no per-MB or per-credit billing. The bundle tier sets your concurrent connections and per-stream filter width; data volume on top of that is not metered.
How many gRPC connections can I run?
Concurrent connections scale by tier: FOCUS 1, BUILD 10, GROW 20, PROFESSIONAL 50, Dedicated unlimited. The STARTER plan does not include gRPC.
What is Yellowstone gRPC?
The streaming interface for Solana built on the Geyser plugin: instead of polling RPC, you open a stream and the node pushes account updates, transactions, slots, and blocks to you as protobuf messages over HTTP/2. It is the standard way to consume live Solana state at production volume.
When should I use gRPC instead of JSON-RPC?
Use gRPC when you watch state continuously — prices, pools, wallets, programs — because the node pushes every matching update with no polling gap. JSON-RPC stays the right tool for on-demand reads and transaction submission; most trading systems run both side by side.
What can I subscribe to, and how do filters work?
Streams cover accounts, transactions, slots, blocks, block metadata, and entries. Every stream carries a server-side filter — there is no unfiltered firehose — and a new SubscribeRequest fully replaces the old one, so you can rewrite a live subscription on the fly, up to 10 re-subscribes per second.
How many accounts can I watch at once?
A single stream matches up to account_max addresses: 50 on FOCUS, 500 on BUILD, 1,200 on GROW, 2,000 on PROFESSIONAL. Total reach is roughly account_max × connections — up to 24,000 accounts on GROW across 20 parallel streams — and Dedicated removes the caps entirely.
Can I use gRPC and JSON-RPC at the same time?
Yes — every Bundle from FOCUS up includes both, and most clients run them together: gRPC for the live feed, RPC for lookups and transaction submission. Both draw from the same RPS budget, measured over a 10-second sliding window.
What is the Full Block Streaming add-on?
An optional add-on, available on any gRPC Bundle, that streams complete block payloads instead of filtered slices. Regular filtered subscriptions stay unlimited and unmetered; full-block volume is the one stream gated behind the add-on.
Get Solana Yellowstone gRPC.
Set up over Telegram with an engineer — endpoint, allowlist, tuning.