ShredStream, explained

Shreds are the smallest unit of block propagation on Solana. Subscribing to them directly is the lowest-latency way to see the chain - before a block is even confirmed. Here's how it works and when to reach for it.

What is a shred?

When a Solana leader produces a block, it doesn't broadcast the whole block at once. It splits entries into small fragments called shredsand streams them across the network using Turbine, Solana's block-propagation protocol. Validators reassemble shreds into entries, and entries into blocks.

Because shreds are emitted continuously as the leader builds the block, you can observe transactions in flight - well before the block lands and confirmation propagates back to a typical RPC endpoint.

Why subscribe to shreds directly?

• →Lower latency than any confirmed-block or RPC-based feed.
• →You see transactions as they propagate, not after the fact.
• →Ideal for first-mover strategies: arbitrage, liquidations, MEV.

Connecting to ShredStream

With OpenInfra.sh, ShredStream is included with every server and runs over the internal fabric, so you get the feed with minimal added latency:

shredstream-proxy \
  --endpoint shreds.openinfra.sh:9999 \
  --dest-ip-ports 127.0.0.1:8001

The proxy forwards deshredded entries to your local listener, where you can decode transactions and react in microseconds rather than milliseconds.

When not to use it

Shreds are pre-confirmation: a transaction you see in the stream may never land, or may land in a different order. For settlement, balances, and anything that must be final, read confirmed state from RPC. Use ShredStream for signal, RPC for truth.