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
- Owner-program filters scale with tier
- Unfiltered block streaming (PROFESSIONAL tier)
- gRPC p99 latency
- 3.8 ms (60-min, Frankfurt)
- Region
- Frankfurt (FRA) only — NTT FRA2 on DE-CIX
- Concurrent subscriptions by tier
- FOCUS 1 → PROFESSIONAL 50
- Node caps (all tiers)
- 2,000 addresses per filter · 10 filters per subscription
- Throughput
- unlimited, unmetered
- Filter updates
- 30 / min on every tier
- Unfiltered block streaming
- included in PROFESSIONAL
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 total addresses watched; data volume on top of that is not metered.
How many gRPC subscriptions can I run at once?
Concurrent subscriptions scale by tier: FOCUS 1, BUILD 10, GROW 20, PROFESSIONAL 50, Dedicated unlimited. The quota counts Subscribe streams, not TCP connections — one connection can carry all of them. 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 (the unfiltered full-block firehose is a PROFESSIONAL-tier feature), and a new SubscribeRequest fully replaces the old one, so you can rewrite a live subscription on the fly, up to 30 filter updates per minute on every tier.
How many accounts can I watch at once?
Your plan sets a total ceiling across all streams: 100 on FOCUS, 5,000 on BUILD, 24,000 on GROW, 100,000 on PROFESSIONAL. There is no separate per-stream address cap, so you can spread those addresses across your streams however you like; Dedicated removes the ceiling 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 unfiltered block streaming?
The full blocks stream with an empty account_include filter — every transaction in every block, instead of filtered slices. Included in the PROFESSIONAL tier (not a paid add-on); lower tiers use regular filtered gRPC, which stays unlimited and unmetered.
Get Solana Yellowstone gRPC.
Set up over Telegram with an engineer — endpoint, token, tuning.