finds.dev← search

// the find

rpcpool/yellowstone-grpc

★ 976 · Rust · AGPL-3.0 · updated Jun 2026

Triton's Dragon's Mouth Yellowstone gRPC service for high-performance Solana streaming

Yellowstone is a Geyser plugin that exposes Solana validator state changes (accounts, transactions, blocks, slots) over gRPC streams. It's the de facto standard for anyone who needs real-time Solana data without polling RPC — MEV bots, indexers, wallets tracking specific accounts. Maintained by Triton One, who also run a commercial hosted version.

The filter model is well thought out: per-stream filters with logical AND/OR semantics across accounts, owners, and memcmp patterns mirror what getProgramAccounts already does, so the mental model is familiar. The cuckoo filter in yellowstone-grpc-proto for deduplication is a nice touch for high-throughput subscribers who receive the same account update from multiple commitment levels. Client examples exist in Go, Rust, TypeScript, and Python, which is better coverage than most infra projects at this star count. The ping/pong keepalive protocol is explicitly documented with working example code — this is the kind of thing that silently breaks streaming clients behind cloud load balancers and most projects don't bother to address it.

The most interesting feature — SubscribeDeshred, which gives you pre-execution transactions from shreds before replay finishes — is not actually in this repo. It returns UNIMPLEMENTED in the open-source plugin; the real implementation lives on a private Triton branch. You get the protobuf definition and the promise, not the code. Block reconstruction has a known upstream Solana bug where entry counts are always zero, acknowledged in the README but not fixed, which means any consumer doing entry-level analysis is working with incomplete data. The e2e test infrastructure requires a running validator with the plugin loaded, which makes CI on this effectively impossible outside Triton's own infra — the test suite is more a smoke test harness than something you'd actually run in a PR. Running this yourself means operating a full Solana validator, which is a significant ops burden; most users will end up paying Triton anyway.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →