Yellowstone gRPC Geyser plugin

• Real-time streaming of transactions, account updates, blocks, and slot changes.
• Uses a standard gRPC interface with protobuf-formatted payloads.
• Accessible from any language supporting gRPC (Python, Go, Rust, JavaScript).
• Ideal for analytics, sniping bots, MEV strategies, data indexing, real-time dashboards, and compliance monitoring.
• from_slot/fromSlot support to replay recent slots and recover events missed during a brief disconnect. For an example, see learning-examples/recover_missed_slots_with_from_slot.py in Solana Geyser Python tutorial. The replay buffer holds a limited number of recent slots, not full history. See Replay depth with from_slot.

​

Replay depth with from_slot

broadcast from <slot> is not available, last available: <slot>

​

Enable the Yellowstone gRPC Geyser plugin

1. Deploy a Solana Global Node
2. Click on your deployed Solana node.
3. Click Add-ons > Yellowstone gRPC Geyser Plugin > Install.

​

Connect to your endpoint

const { default: Client } = require("@triton-one/yellowstone-grpc");

const client = new Client("https://yellowstone-solana-mainnet.core.chainstack.com:443", "YOUR_X_TOKEN");
console.log(await client.getVersion());

import grpc

auth = grpc.metadata_call_credentials(
    lambda ctx, cb: cb((("x-token", "YOUR_X_TOKEN"),), None)
)
creds = grpc.composite_channel_credentials(grpc.ssl_channel_credentials(), auth)
channel = grpc.aio.secure_channel("yellowstone-solana-mainnet.core.chainstack.com:443", creds)

​

Limits

• Unlimited stream events
• 2 concurrent streams available per platform account
• Up to 200 accounts per filter

• Unlimited stream events
• 7 concurrent streams available per platform account
• Up to 200 accounts per filter

• Unlimited stream events
• 25 concurrent streams available per platform account
• Up to 200 accounts per filter

​

Filter limits

• Each public key list in a filter holds up to 200 keys — account and owner in accounts filters; account_include, account_exclude, and account_required in transactions and transactions_status filters; and account_include in blocks filters.
• A subscribe request can include up to 2 accounts_data_slice entries.
• An accounts filter must set account or owner, and a transactions or transactions_status filter must set at least one condition, such as account_include or vote. A filter without conditions, which would stream every update of its type, is rejected.
• The SPL Token Program (TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA) is rejected in the account field of accounts filters and in the account_include field of transactions, transactions_status, and blocks filters.
• The System Program (11111111111111111111111111111111) is rejected in the owner field of accounts filters.

​

Tooling

• Solana Geyser Python tutorial
• Pump fun and Bonk fun sniping bot with Geyser
• Solana: Listening to pump.fun token mint using Geyser
• Solana: Listening to programs using Geyser and Yellowstone gRPC (Node.js)
• Yellowstone repository
• Rust example
• Go example