ShredStream
Raw shred data delivered to your server before a block is confirmed — the earliest possible signal on the Solana network.
Why ShredStream?
- 200–400 ms earlier than waiting for confirmed block via RPC.
- React to transactions before they appear in any block explorer.
- Receive the same shreds the Jito block engine uses for MEV bundles.
- Delivered over a dedicated UDP channel from the nearest relay.
How it works
OpenInfra operates shred relay nodes co-located with Solana validators. When a validator produces or receives shreds, our relay forwards them over UDP to your OpenInfra server via the private network fabric — typically within 1–2 ms of the validator broadcasting.
Your server runs the ShredStream listener process which assembles shreds into entries, then exposes them as a local gRPC stream or over a Unix socket. Your application connects to that local interface — no external network hop.
Latency comparison
ShredStream: ~1–5 ms after leader produces shredsYellowstone gRPC (processed): ~50–100 ms after slotRPC getBlock (confirmed): ~400–600 ms after slot