NoLimitNodes
PricingDocsBlogAcademyAboutSupportContact
Log in
Blog/Guides

Jito Shreds Explained: What Solana Shreds Are and Why Traders Want Them

Jito shreds are ordinary Solana shreds with faster delivery. What a shred contains, data vs coding shreds, Turbine vs shred streams, why traders want them first, and what they cannot tell you.

N
NoLimitNodes Engineering
Infrastructure Team
Nov 17, 20268 min read
On this page +
  • 01What is a shred in Solana?
  • 02Data shreds vs coding shreds
  • 03Turbine and shred streams
  • 04What makes Jito shreds different?
  • 05Why traders want shreds first
  • 06What shreds cannot tell you
  • 07How to get Jito-compatible shreds
  • 08FAQ
  • 09Get shreds first
  • 10Sources

Jito shreds are ordinary Solana shreds, the small signed fragments of a block that a slot leader broadcasts, delivered through Jito's ShredStream network instead of only through Solana's normal Turbine propagation. They are not a separate data type. “Jito shreds” describes where the shreds came from, not what they are.

This guide is for developers, searchers and RPC operators who keep hearing “get shreds first” and want to know what that means. It covers what a shred contains, how shreds travel, why trading teams pay for them, and how to receive the same Jito-compatible shreds now that Jito has announced the end of its hosted ShredStream service.

TIP / Key takeaways
  • A shred is a signed fragment of a Solana block, sized to fit in one UDP packet. Jito's docs describe shred traffic as many packets of about 1,200 bytes.
  • Data shreds carry block entries and transactions. Coding shreds carry erasure-coding data that lets receivers rebuild lost data shreds.
  • Shreds arrive before the block finishes executing, which is why they are the earliest view of on-chain activity.
  • Shreds have no execution results: no logs, errors, balance changes or commitment level.
  • Jito announced that ShredStream would shut down on September 5, 2026. NoLimitNodes Shredstream delivers raw shreds in a Jito-compatible format.

01What is a shred in Solana?#

When a validator is the slot leader, it builds its block as a stream of entries. Each entry is a batch of transactions plus a proof-of-history hash. The leader serializes those entries and cuts the bytes into shreds, pieces small enough to fit in a single UDP packet. Each shred is signed by the leader, so receivers can confirm it came from the expected validator.

Every shred carries a small header that tells a receiver where it belongs:

Header fieldWhat it tells you
signatureThe leader’s signature, to check authenticity
variantShred type (data or coding) and format
slotWhich slot (block) the shred belongs to
indexPosition of the shred within the slot
versionThe cluster’s shred version, used to reject shreds from other networks
fec_set_indexWhich erasure-coding set the shred belongs to

Because a leader streams shreds while it is still producing the block, a receiver can start reading transactions before the block is complete, voted on or replayed by the rest of the network.

Diagram of a Solana block being cut into shreds: the leader's entries are serialized into bytes, split into data shreds, and grouped into FEC sets, each with coding shreds that can rebuild lost data shreds.
How a leader turns entries into data and coding shreds. Each shred fits in one UDP packet.

02Data shreds vs coding shreds#

Shreds come in two kinds:

  • Data shreds carry the serialized entries. Reassembling them in index order gives you the leader's block data.
  • Coding shreds carry Reed-Solomon erasure codes computed over a group of data shreds, called an FEC set (forward error correction set). If some data shreds in a set are lost in transit, a receiver with enough coding shreds can rebuild them.

UDP drops packets, so erasure coding is what makes a UDP-based block broadcast reliable. A receiver does not need every packet. It needs enough shreds from each FEC set.

03How shreds travel: Turbine and shred streams#

By default, shreds move through Turbine, Solana's block propagation protocol. The leader sends each shred to a root node, which retransmits it to a layer of validators, who retransmit to the next layer. The tree is weighted by stake, so validators with more stake tend to sit closer to the root and see shreds earlier. Nodes near the leaves, such as an unstaked RPC node, see them later.

A shred stream shortcuts that tree. Instead of waiting for shreds to hop through several Turbine layers, a provider with good network placement forwards shreds straight to your server as soon as it receives them. That is the service Jito ShredStream offered, and the one NoLimitNodes Shredstream offers today. Our Solana Shredstream guide goes deeper into Turbine and the receiver loop.

04What makes Jito shreds different?#

Nothing inside the shred changes. What Jito added was delivery:

  1. Clients got a Solana public key approved by Jito and ran the open-source jito-shredstream-proxy.
  2. The proxy authenticated to Jito's Block Engine and received shreds from up to two regions on UDP port 20000 by default.
  3. It forwarded them to your own IP:port destinations, or decoded them and streamed transactions over gRPC.

Jito said this could save “hundreds of milliseconds” during trading, and it gave servers in less-connected regions a redundant shred path. Because so many teams used the proxy, a lot of deshredders and trading stacks were built around the packets it forwarded. A feed that sends packets in the same format can plug into those stacks without code changes.

05Why traders want shreds first#

Shreds are the earliest public signal that the leader has included a transaction. For latency-sensitive teams, that matters:

  • Sniper bots see a token creation or first liquidity add while the block is still being produced.
  • MEV searchers spot large swaps that will move a pool and react in the next slots.
  • Market makers update quotes before processed RPC data shows the trade.
  • RPC operators feed shreds into nodes in weaker regions, so those nodes keep up with the chain tip.

Compare that with the usual paths. Processed or confirmed data from RPC and Yellowstone gRPC is only available after a validator has replayed the transactions. Shreds come before that step.

Timeline of when each Solana data source sees a transaction: raw shreds while the leader is still producing the block, then processed data from RPC and Yellowstone gRPC after replay, then confirmed after a supermajority vote, then finalized.
Shreds are first because they skip replay. They also carry no execution result or commitment level.

06What shreds cannot tell you#

Speed has a cost. Raw shreds:

  • Have no execution results: no logs, errors, balance changes or compute usage.
  • Have no commitment level: a shred's slot can still end up on a minority fork that gets dropped.
  • Can be duplicated: you will see the same shred from multiple paths and must deduplicate.
  • Arrive out of order: you sort by slot and index and wait for FEC sets to complete.

That is why many teams pair two feeds. Shreds give the earliest signal, and gRPC confirms what actually executed. To turn shreds into transactions, see How to Decode Jito Shreds.

07How to get Jito-compatible shreds today#

Jito's documentation announced that ShredStream would be completely shut down on September 5, 2026, and recommended DoubleZero Edge as its migration path. If your stack already decodes the packets Jito's proxy forwarded, the simplest move is a provider that sends the same format.

NoLimitNodes Shredstream sends raw mainnet shreds over UDP, in a format compatible with the Jito proxy and client path, to a public IPv4 address and port you verify in the dashboard. Your existing receiver and deshredder can be reused.

Jito ShredStream (before shutdown)NoLimitNodes Shredstream
AccessPublic key approved via Discord, auth keypairDashboard destination verified with a UDP challenge
Softwarejito-shredstream-proxyNone required. Shreds go straight to your port.
Packet formatRaw Solana shreds forwarded by the proxyCompatible with the Jito proxy and client path
Included destinationsn/a1 on Ultra and Max, 2 on Enterprise
Extra destinationsn/a$100/month each, on any plan
NoLimitNodes details from our pricing page and Shredstream docs.

Moving an existing Jito setup is covered step by step in Jito ShredStream Shutdown: How to Migrate.

08Frequently asked questions#

Are Jito shreds different from normal Solana shreds?

No. Jito shreds are standard Solana shreds produced and signed by the slot leader. The difference is delivery: Jito ShredStream forwarded them over a low-latency network to approved clients, instead of clients waiting for Solana’s Turbine tree. The data inside each shred is identical.

How big is a Solana shred?

A shred is sized to fit in one UDP packet under a typical network MTU. Jito’s troubleshooting docs describe incoming shred traffic as many packets of about 1,200 bytes. Each packet holds one shred: a header with the signature, slot, index and FEC set, followed by the payload.

Can I see transactions from shreds before they are confirmed?

Yes. Once you collect a slot’s data shreds in order and deserialize the entries, you can read the transactions before the block is executed or confirmed. Treat them as unconfirmed. The slot can still be skipped or land on a fork, and shreds contain no execution results.

What replaced Jito ShredStream?

Jito recommended DoubleZero Edge in its shutdown notice. Other providers also stream raw shreds. NoLimitNodes Shredstream sends Jito-compatible packets over UDP, so teams can keep their existing receivers and deshredders and only change where packets arrive.

09Get shreds first#

Shreds are the earliest view of what a Solana leader is putting on chain. Jito ShredStream made them easy to get, and the packet format its proxy forwarded is still what many stacks expect.

Start receiving Jito-compatible shreds with NoLimitNodes Shredstream. Ultra includes one destination. See pricing or talk to sales about multi-region setups.

Related reading: Migrate from Jito ShredStream · How to Decode Jito Shreds · Shredstream vs Yellowstone gRPC

10Sources#

  • Jito docs: ShredStream and the shutdown notice, checked November 17, 2026
  • jito-labs/shredstream-proxy on GitHub
  • NoLimitNodes Shredstream docs
#solana#jito shreds#solana shreds#solana shredstream#turbine#jito
N
NoLimitNodes Engineering
Infrastructure Team

The team that runs our RPC, WebSocket, gRPC, and streaming fleet. We write about what we operate: validators, Geyser pipelines, and the request paths in between.

On this page
  • 01What is a shred in Solana?
  • 02Data shreds vs coding shreds
  • 03Turbine and shred streams
  • 04What makes Jito shreds different?
  • 05Why traders want shreds first
  • 06What shreds cannot tell you
  • 07How to get Jito-compatible shreds
  • 08FAQ
  • 09Get shreds first
  • 10Sources
↑ back to top
///Read next
EcosystemNov 17, 2026

Jito ShredStream Shutdown: How to Migrate Your Shred Feed

Jito announced its hosted ShredStream would shut down on September 5, 2026. What the service did, who loses what, the alternatives, and a four-step migration that keeps your existing deshredder.

#solana#jito shredstream#jito shredstream alternative
7 min read
GuidesJul 28, 2026

Solana Shredstream Guide: Shreds, Turbine, Forks, and Bots

A practical guide to raw Solana shreds, Turbine propagation, deshredding, entries, duplicate packets, forks, and the receiver loop trading bots operate.

#solana#shredstream#shreds
10 min read
///Relevant Solana infrastructure
Solana Shredstream

Raw leader shreds for latency-sensitive trading and MEV systems.

Explore Solana Shredstream →
← Older
Jito ShredStream Shutdown: How to Migrate Your Shred Feed
Newer →
How to Decode Jito Shreds: Turn Solana Shreds into Transactions
Run it yourself

Every benchmark in this blog runs against our public endpoints.

Spin up an RPC, WebSocket, or gRPC endpoint in under a minute. Flat monthly pricing. Reproduce the numbers for your own workload.

See pricing

Ready to get started?

Choose a plan and start building in under 30 seconds.

Talk to Sales
NoLimitNodes

Solana RPC infrastructure built for performance and scale.

RPC Access
  • Solana HTTP RPC nodes
  • Solana WebSocket nodes
  • Yellowstone gRPC nodes
  • Solana Shredstream
  • UltraSend transaction relay
Infrastructure
  • Compute Platform
  • VPS
  • VDS
  • Bare Metal
  • Geyser Plugin Hosting
Enhanced Streams
  • PumpFun
  • PumpSwap
  • Raydium
  • Orca
  • Meteora
  • System Events
  • Browse all Solana Enhanced Streams →
Program Streams
  • PumpFun
  • PumpSwap
  • Raydium CLMM
  • Orca Whirlpool
  • Meteora DLMM
  • Jupiter Swap
  • Jupiter Perps
  • Kamino Lending
  • Browse all 37 Solana programs →
Trading
  • EZWallet
Analytics
  • Historical Datasets
  • Historical Raw Blocks
Company
  • About
Resources
  • Pricing
  • RPC Rate Limits
  • Custom Development
  • Documentation
  • Blog
  • Academy
  • Support
  • Contact Sales
Compare
  • Yellowstone gRPC vs LaserStream
  • Triton vs Helius
  • Raydium API vs Helius
  • PumpSwap API vs Bitquery
  • QuickNode Streams vs NLN
  • All comparisons →
Legal
  • Terms & Conditions
  • Privacy Policy
© 2026 CLR3 Inc., operating as NoLimitNodes. Registered in Ontario, Canada. All rights reserved.solana mainnet