Solana Yellowstone gRPC streaming

A persistent feed for your backend

Yellowstone exposes subscriptions for Solana data through a Geyser-compatible interface. Account, transaction, and slot subscriptions let a consumer focus on relevant updates rather than repeatedly asking whether something changed.

The protocol and feed mode matter. A gRPC connection describes how data is transported; it does not, by itself, promise finality or a particular pre-execution signal. Check the fields and subscription types supported by your endpoint.

Match the endpoint, token, and client

In Lumios, open Endpoints and find Yellowstone DM under Streaming. Use the target and token from the same location; the token belongs in x-token request metadata. Review Concurrent streams and Accounts across filters in Limits.

Use a client compatible with the endpoint’s Yellowstone protobuf definitions. Start with one supported filter and confirm that updates arrive before expanding the subscription.

The current backend documentation describes plaintext HTTP/2 targets. Use a trusted private connection or an encrypted tunnel as documented; do not assume the channel encrypts your token.

Measure the consumer, not just the connection

A connected socket can still have a stalled consumer. Include the event-to-storage path in monitoring, and test it with the filtering and database writes your application will actually use.

• Record the last handled slot and detect periods without progress.
• Bound queues and define what happens when processing falls behind.
• Exercise disconnects and restore subscriptions after reconnecting.
• Use durable checkpoints and RPC reconciliation for data your application cannot afford to miss.

Common questions