Yellowstone gRPC

The Yellowstone client you already use works here unchanged: this is the upstream geyser.Geyser API, served from the same regional hosts as JSON-RPC and WebSocket. Point it at a regional endpoint.

http://<region>.corvus-labs.io:10101

<region> is fra, ams, lon, nyc or tyo; Falcon, aRPC and Shredstream reach all nine metros (Regions).

Authentication

Your registered public egress IP is the credential; dedicated deployments take x-token gRPC metadata instead. The tokenized URL path that dedicated HTTP and WebSocket resources use is never applied to gRPC. Access & authentication has the setup.

Commitment

Every SubscribeRequest carries a single commitment, and it covers every filter in that request.

Subscription model

• Subscribe runs both ways: you write subscription requests, the server streams updates back.
• You name your own filters, and those names come back attached to matching updates, so you can route on them.
• Each request replaces the active configuration rather than adding to it. Build the complete state you want and send it in one go.
• A reconnect starts a fresh subscription with no filters carried over. Pass from_slot on the new request to replay what the server retains from that slot on (replay on reconnect), or backfill through JSON-RPC.
• The server sends ping updates down the stream. Echo them back.

For exact request fields and message shapes, the upstream Yellowstone proto is the reference.

Yellowstone gRPC or aRPC?

Watching accounts or program state? Stay here: account updates only exist after execution, and this is the earliest stream that carries them. Need transactions before they execute? Take aRPC.

If you'd rather have raw Solana shreds pushed at you over UDP than a typed stream, that's Shredstream.