Solana Shred
Validator & infra
A Solana shred is an erasure-coded packet used to propagate part of a leader's block through Turbine. Data shreds carry ledger entry data. Coding shreds carry recovery information. Validators collect enough shreds to reconstruct entries, then execute the transactions inside them.
Detailed explanation
The leader does not send one complete block to every validator. It splits ledger data into shreds and adds coding shreds through erasure coding. Turbine fans those packets through a tree, which spreads the bandwidth cost across participating validators.
A shred includes protocol identifiers such as its slot and index. Receivers group packets by those fields. They remove duplicates, recover missing data when a coding set permits it, and rebuild ledger entries in protocol order.
A raw shred is not a processed transaction. It does not contain an execution result, logs, balance changes, compute-unit use, or a commitment level. The slot can also sit on a fork that the cluster later abandons.
This is why a low-latency trading system often uses two paths. It detects a possible opportunity from raw shreds, then confirms execution and state through Yellowstone gRPC or HTTP RPC.
When you'll see this
You will see data shreds, coding shreds, shred indexes, erasure sets, deshredding, and Turbine discussed together. A Shredstream client receives those packets over UDP and reconstructs entries locally.
Read the full Shredstream guide for the receiver loop, duplicates, fork handling, and bot architecture.
How NoLimitNodes uses this
Our Shredstream service pushes raw, Jito-compatible mainnet shreds to one public IPv4 and UDP port. Ultra includes one account-wide destination, including during the trial.
Related terms
- Yellowstone gRPC · The Triton-built Geyser plugin that exposes a gRPC stream of accounts, transactions, and slots over the wire.
- Geyser Plugin · A shared library a Solana validator loads to push account, slot, and transaction updates into your own pipeline.
- Processed, Confirmed, Finalized · The three Solana commitment levels, ordered from "this validator saw it" to "supermajority will not roll it back."
- Compute Unit Budget · The CU limit and price you set with the ComputeBudget program to control how much work and priority fee a transaction uses.