What's available

Supanode gRPC follows the standard Yellowstone gRPC specification. For the full protocol specification, see the official Yellowstone documentation.

Supported streams

Commitment levels

All streams support three commitment levels:

• processed - fastest, can revert.
• confirmed - practical default for trading.
• finalized - adds ~13 seconds of latency, no risk of revert.

Filters

Yellowstone gRPC filters compose like this:

• Different categories in one SubscribeRequest (e.g. accounts plus transactions) - logical AND. The stream emits messages only when filters across categories all match.
• Multiple named filters within the same category (e.g. two named entries inside transactions:) - logical OR. Each named filter is an independent subscription; a transaction matches if any named filter accepts it.
• Multiple values within a single field's array (e.g. several pubkeys in accountInclude) - logical OR.

For complete filter options, see Yellowstone subscription specification.

Common patterns

Subscribe to a specific program's transactions

transactions: {
  myFilter: {
    vote: false,
    failed: false,
    accountInclude: ["YOUR_PROGRAM_ID"],
  }
}

Subscribe to account changes with data slicing

accounts: {
  myAccounts: {
    account: ["YOUR_ACCOUNT_PUBKEY"],
    owner: [],
    filters: []
  }
},
accountsDataSlice: [{ offset: 0, length: 40 }]

Subscribe to slot updates only

slots: {
  mySlots: { filterByCommitment: false }
}

Filter limits

Filter complexity caps depend on your plan. See Limits for the full breakdown.

External references

• Yellowstone gRPC GitHub
• geyser.proto (SubscribeRequest definition)
• Triton One Dragon's Mouth docs
• Solana Geyser plugin documentation

Next steps