NoLimitNodes
PricingDocsBlogAcademyAboutSupportContact
Log in
Blog/Ecosystem

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.

N
NoLimitNodes Engineering
Infrastructure Team
Nov 17, 20267 min read
On this page +
  • 01What was Jito ShredStream?
  • 02What changed with the shutdown?
  • 03Who is affected?
  • 04Jito ShredStream alternatives compared
  • 05How to migrate to NoLimitNodes
  • 06FAQ
  • 07Keep your shred feed running
  • 08Sources

Jito ShredStream was Jito Labs' service for streaming raw Solana shreds from block leaders to traders, searchers and RPC operators. Jito's documentation announced that ShredStream would be completely shut down on September 5, 2026, and pointed users to a migration path. If your bot, indexer or RPC node depended on Jito shreds, you need a new source for the same data.

This guide is for teams that ran jito-shredstream-proxy or consumed Jito shreds in production. It explains what Jito ShredStream did, what you lose without it, and how to move to a feed that sends the same Jito-compatible packets, so your receiver and deshredder keep working.

TIP / TL;DR
  • Jito announced that ShredStream would shut down on September 5, 2026, and recommended DoubleZero Edge as its migration path.
  • Shreds are the fragments of a block that a Solana leader sends before the block finishes executing. They are the earliest view of on-chain activity you can get.
  • NoLimitNodes Shredstream sends raw mainnet shreds over UDP in a format compatible with the Jito proxy and client path, so existing Jito-compatible receivers and deshredders can be reused.
  • Migration takes four steps: open a UDP port, register the destination, verify it with a UDP challenge, and point your existing deshredder at it.

01What was Jito ShredStream?#

Jito ShredStream delivered low-latency shreds from Solana leaders to approved clients. According to Jito, it could save “hundreds of milliseconds” during trading. It also gave servers in less-connected regions a redundant path for shreds.

Access worked like this:

  1. Approval: you got a Solana public key approved through Jito's Discord.
  2. Proxy: you ran the open-source jito-shredstream-proxy (Apache-2.0), which authenticated to Jito's Block Engine with that keypair.
  3. Regions: you chose up to two regions with DESIRED_REGIONS, such as amsterdam,ny.
  4. Delivery: the proxy received shreds on UDP port 20000 by default and forwarded them to the IP:port destinations in DEST_IP_PORTS. Optionally, it ran a gRPC service that streamed decoded transactions.

If you want to understand shreds themselves first, read Jito Shreds Explained or the Solana shred glossary entry.

02What changed with the Jito ShredStream shutdown?#

Jito's documentation added a deprecation notice saying the service would be “completely shut down in 60 days (September 5, 2026).” It recommends moving to DoubleZero Edge, whose transition guide includes a free trial.

Once the hosted service stops:

  • No new approvals: Jito ShredStream approvals and auth keypairs no longer give you a feed.
  • No upstream feed: jito-shredstream-proxy in shredstream mode has no Jito Block Engine feed to connect to.
  • Silent receivers: anything downstream of the proxy, such as RPC nodes using it as a shortcut for shreds, deshredders and trading bots, stops getting early shreds and falls back to normal Turbine propagation.
Before and after diagram. Before: Jito Block Engine sends shreds to jito-shredstream-proxy, which forwards them to DEST_IP_PORTS and your deshredder. After: NoLimitNodes Shredstream sends Jito-compatible raw UDP shreds straight to your verified IPv4 and UDP port, and the same deshredder reads them.
The upstream changes. The packets your deshredder reads, and the code that reads them, do not.

03Who is affected?#

WorkloadWhat Jito shreds gave youWhat happens without them
Sniper and MEV botsThe earliest view of new transactions, before executionSignals arrive later, through processed RPC or gRPC data
Market makersFaster reaction to swaps that move a poolQuotes go stale while you wait for processed data
RPC operatorsA second shred source for nodes in weaker regionsNodes rely only on Turbine and can fall behind the tip
Indexers and analyticsRaw block data before executionNo change to correctness, only to latency

If your workload needs execution results such as logs, balance changes or errors, shreds were never the right tool. A Yellowstone gRPC stream gives you processed transactions with commitment levels. See Shredstream vs Yellowstone gRPC for when to use each.

04Jito ShredStream alternatives compared#

OptionOutputReuses your Jito receiverNotes
NoLimitNodes ShredstreamRaw UDP shreds, mainnetYes, Jito-compatible packetsOne destination included with Ultra and Max, two with Enterprise. Extra destinations cost $100/month each on any plan.
DoubleZero EdgeShred feedCheck provider docsThe migration path Jito recommends. A free trial is available.
Your own validator or RPC nodeTurbine shredsPartlyHow early you see shreds depends on your stake and position in Turbine, plus hardware and operations work.
Yellowstone gRPCProcessed transactionsNoLater than shreds, but includes execution metadata. Easiest to consume.
Options for replacing a Jito ShredStream feed. NoLimitNodes details from our pricing page and Shredstream docs; DoubleZero Edge from Jito's shutdown notice.

The deciding question is whether you want to rewrite your ingest path. If your stack already deshreds the packets the Jito proxy forwarded, a Jito-compatible feed is a configuration change, not a rewrite. For a side-by-side of the two services, see Jito ShredStream vs NoLimitNodes.

05How to migrate from Jito ShredStream to NoLimitNodes#

NoLimitNodes Shredstream sends raw Solana mainnet shreds over UDP to a public IPv4 address and port that you verify. Packets are compatible with the Jito proxy and client receiving path, so an existing Jito-compatible receiver and deshredder can be reused.

Four migration steps: 1 prepare a public IPv4 receiver with one UDP port open, 2 add the IP and port as a Shredstream destination on an active node in the dashboard, 3 read the SHREDCAST-VERIFY packet and paste the token back to verify, 4 point your existing deshredder at the new port.
Moving a Jito setup to NoLimitNodes Shredstream. Delivery starts only after step 3.

Step 1: Prepare a receiver

Use a host with a public IPv4 address and open one UDP port, from 1024 to 65535, for the feed. Raw UDP carries no NoLimitNodes authentication or encryption, so isolate the receiver and expose only that port.

receiver host
bash
# Allow the shred port and watch packets arrive (adjust the port to your setup)
sudo ufw allow 20000/udp
sudo tcpdump -n -i any 'udp and dst port 20000'

Step 2: Add the destination

Sign in at dash.nolimitnodes.com, open an active node, find Shredstream delivery, and save your IP:port. Ultra and Max each include one destination, and Enterprise includes two. You can also buy extra destinations at $100 a month each on any plan, including Free.

Step 3: Verify with the UDP challenge

NoLimitNodes sends a one-time SHREDCAST-VERIFY <id> <token> packet to your socket. Paste the token back into the dashboard to prove you control the address. Delivery starts after verification, with no staff approval. Full steps are in the Shredstream setup docs, and firewall rules are in the firewall docs.

Step 4: Point your existing deshredder at the new port

Before, packets came from jito-shredstream-proxy forwarding to DEST_IP_PORTS. Now NoLimitNodes sends them straight to your verified destination. Your deshredder keeps parsing the same packets. You still handle deduplication, forks and missing shreds, just as you did with Jito. The Jito-compatible client docs map each proxy setting to its NoLimitNodes equivalent.

NOTE / Run both feeds before cutover
If you still have another shred source, run it next to the new feed for a while and compare slots seen, complete erasure sets, decoded transactions and drop counts. Tag each upstream before deduplication, so a gap in one feed is not hidden by the other.

Migration checklist

  • Public IPv4 receiver with one UDP port open, and nothing else exposed
  • Destination saved and UDP challenge verified in the dashboard
  • Deshredder listening on the new port
  • Duplicate and fork handling tested on live traffic
  • Old jito-shredstream-proxy containers and firewall rules for Jito IPs removed
  • Alerting on packet rate, so a silent feed pages you

06Frequently asked questions#

Is Jito ShredStream still available?

Jito’s documentation announced that its hosted ShredStream service would be completely shut down on September 5, 2026, and recommended migrating to DoubleZero Edge. Teams that still need raw shreds can move to another provider. NoLimitNodes Shredstream sends packets compatible with the Jito proxy and client path, so existing receivers keep working.

Can I keep using jito-shredstream-proxy?

The proxy’s shredstream mode authenticates to Jito’s Block Engine to receive shreds, so it has no upstream feed once the hosted service is shut down. With NoLimitNodes, shreds arrive directly at your verified UDP destination. Your deshredding code can stay the same because the packets are Jito-compatible.

What is the difference between Jito shreds and NoLimitNodes shreds?

Both are raw Solana shreds produced by the slot leader and delivered over UDP before the block finishes executing. The difference is the delivery network and access model. NoLimitNodes Shredstream sends Jito-compatible packets to destinations you verify in its dashboard, with no Discord approval or auth keypair.

Do shreds include logs or transaction errors?

No. Raw shreds contain the leader’s block data before execution. They have no logs, errors, balance changes, compute usage or commitment levels. If you need execution results, use Yellowstone gRPC alongside shreds: shreds for the earliest signal, and gRPC for confirmed outcomes.

How much does a Shredstream destination cost on NoLimitNodes?

Ultra and Max each include one Shredstream destination, and Enterprise includes two. Extra destinations cost $100 a month each and can be added on any plan, including Free. See the pricing page for current plan prices.

07Keep your shred feed running#

The Jito ShredStream shutdown removes one upstream source but does not change what shreds are or how you decode them. If your stack already reads the packets Jito's proxy forwarded, the fastest migration is a feed that sends the same packets.

Get NoLimitNodes Shredstream: register a destination yourself and keep your existing deshredder. Compare plans on the pricing page, or talk to sales about volume or regions.

Related reading: Jito Shreds Explained · How to Decode Jito Shreds · Solana Shredstream Guide

08Sources#

  • Jito docs: ShredStream and the shutdown notice, checked November 17, 2026
  • jito-labs/shredstream-proxy on GitHub
  • NoLimitNodes Shredstream docs
#solana#jito shredstream#jito shredstream alternative#solana shredstream#solana shreds#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 was Jito ShredStream?
  • 02What changed with the shutdown?
  • 03Who is affected?
  • 04Jito ShredStream alternatives compared
  • 05How to migrate to NoLimitNodes
  • 06FAQ
  • 07Keep your shred feed running
  • 08Sources
↑ back to top
///Read next
GuidesNov 17, 2026

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.

#solana#jito shreds#solana shreds
8 min read
EngineeringNov 17, 2026

How to Decode Jito Shreds: Turn Solana Shreds into Transactions

From UDP socket to transaction: receive Jito-compatible shred packets, parse the 83-byte header, buffer and recover FEC sets, deshred into entries, and handle the edge cases that break naive decoders.

#solana#decode jito shreds#jito shreds
8 min read
← Older
gRPC API for Solana: How It Works and When to Use It Instead of JSON-RPC or WebSockets
Newer →
Jito Shreds Explained: What Solana Shreds Are and Why Traders Want Them
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