Raw Solana shreds, pushed straight to your UDP port
Shredstream gives you Solana block data before a validator finishes executing it. You enter one public IPv4 address and UDP port in the NoLimitNodes dashboard. We start pushing raw, Jito-compatible shreds to that destination automatically. You keep the client and workflow you already know. The tradeoff is real. Raw shreds do not include transaction logs, balance changes, errors, compute usage, ordering guarantees, or a commitment level. Your receiver must deshred entries, handle duplicate packets, and account for forks. If you need processed data with filters and execution metadata, use Yellowstone gRPC. If those last milliseconds decide whether your strategy lands, Shredstream is the earlier data path. Ultra includes one account-wide destination, including during the trial.
Available during your Ultra trial. Enter your public IPv4 and port in the dashboard. Delivery starts automatically.
See full pricingPackets and states your receiver must handle
raw delivery gives you the earliest data and leaves recovery, ordering, and fork handling to your client
| Event | Type | Description | Frequency |
|---|---|---|---|
| Data shreds | event | Carry erasure-coded ledger entry data produced by the current Solana leader. | Very high |
| Coding shreds | event | Carry recovery data that lets your receiver reconstruct missing data shreds. | Very high |
| Duplicate packets | event | UDP and multi-path delivery can repeat packets. Deduplicate before you rebuild entries. | High |
| Incomplete shred sets | event | A slot can arrive in pieces. Hold state until enough data exists to reconstruct an entry. | Medium |
| Forked slots | event | An early slot can lose the fork choice. Treat raw observations as signals, not final state. | Low |
| Deshredded entries | event | Your Jito-compatible receiver reconstructs entries and transactions from the raw packet stream. | Very high |
The Ultra Shredstream entitlement
last reviewed 2026-07-28
Where Shredstream sits in the Solana data path
A leader does not send a finished block as one file. It breaks ledger entries into data shreds, adds coding shreds for recovery, and sends those packets through Turbine. Shredstream gives you those packets before the receiving validator finishes replay and execution.
Solana calls Turbine its block propagation protocol. Jito says its compatible service “delivers the lowest latency shreds from leaders on the Solana network.” See the official Jito documentation for the client model and shutdown notice.
Leader builds entries
Transactions enter the slot.
Leader emits shreds
Data and recovery packets leave the leader.
You receive UDP
Your client rebuilds entries and transactions.
Validator executes
Logs, balances, errors, and commitment come later.
You get earlier data. You also take on more work.
What you get
- Raw data before validator execution finishes.
- A Jito-compatible packet format.
- Direct delivery to your public IPv4 and UDP port.
- Automatic provisioning with Ultra.
What you must handle
- Deshredding entries and decoding transactions.
- Duplicate, missing, and out-of-order UDP packets.
- Forks and slots that never become canonical.
- No logs, errors, balance changes, or commitment guarantee.
Set up delivery without a support ticket
Start an Ultra trial or upgrade an existing account. Open a UDP port on a server with a public IPv4 address. Then open the Shredstream page in your dashboard and save the destination.
We provision the feed immediately. Raw UDP has no NLN packet authentication or encryption, so isolate the receiver and expose only the port you need. Keep your Jito-compatible deshredder behind that socket.
Read the setup guide, check the firewall checklist, or compare Shredstream with gRPC.
Use Shredstream only when raw timing changes the result
Shredstream fits market makers, arbitrage systems, MEV research, and trading loops that already operate a low-latency UDP ingest path. You should know what you will do with a transaction before the packet arrives.
It is the wrong default for indexers, analytics, wallet UIs, and notification services. Those systems benefit more from filters, execution metadata, stable ordering, and commitment levels. Use Yellowstone gRPC for that work.
Frequently asked questions
Related products
Pick the right data path based on timing, metadata, filtering, and engineering effort.
Move your raw UDP feed before the announced Jito service shutdown.
Processed, filterable Solana data with execution metadata and commitment levels.
Understand Turbine, data and coding shreds, deshredding, duplicates, and forks.
Standard JSON-RPC endpoints. The pull-side of the same fleet.
Lighter-weight push transport for account-level UIs and prototypes.
Send raw Solana shreds to your server
Ultra includes one account-wide public IPv4 and UDP-port destination. It is available during your trial and provisions automatically from the dashboard.