ShredStream, explained

Shreds are packets used to propagate pieces of Solana block data. They can provide an early signal, but they are raw, pre-confirmation input rather than parsed or authoritative chain state.

What is a shred?

When a Solana leader produces block data, it encodes that data into data and coding shreds for propagation across the network. Consumers reconstruct and parse the relevant data from those shreds.

The packets arrive before normal commitment and confirmation workflows complete. They are not JSON, parsed transaction objects, or proof that a transaction landed.

Why subscribe to shreds directly?

• Feed an existing Solana component that already understands raw shreds.
• Build a custom reconstruction or propagation-monitoring pipeline.
• Produce early signals that are independently verified through RPC or gRPC.

Connecting to ShredStream

With OpenInfra.sh, ShredStream runs over an isolated private network. Enable an eligible server from the project Solana page, wait for the destination to show On, then verify a bounded sample on UDP port 20001:

sudo timeout 15 tcpdump -ni any 'udp and dst port 20001' -c 5

The dashboard controls relay discovery; no API key or public ShredStream endpoint is involved. OpenInfra delivers the raw UDP packets but does not start a listener or decoder inside the server. Disable delivery when the consumer is not running.

When not to use it

Raw UDP delivery can contain duplicates, gaps, and out-of-order packets. For account state, parsed updates, settlement, balances, and anything that must be authoritative, use Yellowstone gRPC or committed RPC state. Use ShredStream for signal, RPC for truth.