Skip to main content

gRPC (Yellowstone)

Standard Yellowstone Dragon’s Mouth gRPC interface. Streams post-replay transaction data with full metadata — balances, logs, inner instructions, execution status. This is the same protocol used by Helius, Triton, and other RPC providers.

How It Works

You get everything: pre/post balances, token balances, logs, inner instructions (CPI trace), compute units consumed, success/failure status.

Connecting

Use any standard Yellowstone gRPC client library:
  • Rust: yellowstone-grpc-client
  • TypeScript: @triton-one/yellowstone-grpc
  • Python: yellowstone-grpc-client-python

Compression

Both gzip and zstd are supported for send and receive. Enable compression on your client for lower bandwidth usage:

Connection Limits

Connect as many clients as you need — there’s no hard connection cap. Per-connection filter limits prevent firehose abuse:
Key limits per connection:
  • Transaction filters: up to 25 filters, each with up to 100 account_include entries
  • Account filters: up to 400 filters, up to 400 accounts each
  • any: false means you must specify at least one filter — no unfiltered firehose
  • TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA (SPL Token program) is blocked as a filter key because it matches nearly every transaction