Move your Jito-compatible shred receiver without rebuilding it
Jito Labs has announced that its hosted ShredStream service will shut down on September 5, 2026. NoLimitNodes gives you a replacement raw UDP feed that works with the Jito-compatible proxy and client path you already operate. The provisioning model changes. You register one public IPv4 address and UDP port in the NoLimitNodes dashboard, then we push mainnet shreds to it automatically. There is no token inside each packet and no staff approval step. The raw-data behavior does not become simpler just because the upstream changes. You still need to deshred entries, remove duplicates, track forks, and validate completeness. Run both sources in parallel before cutover, compare reconstructed slots, and keep your previous configuration ready until the new path is stable in your environment.
Streamed events and instructions
every event the program emits, decoded and ready to consume
| Event | Type | Description | Frequency |
|---|---|---|---|
| Existing receiver | event | Keep the Jito-compatible proxy or client that already deshreds packets. | — |
| New destination | event | Register the public IPv4 and UDP port that reaches your receiver. | — |
| Parallel packets | event | Run both upstream feeds while you compare slot and shred coverage. | — |
| Duplicate detection | event | Tag upstream paths during validation and deduplicate before downstream logic. | — |
| Cutover | event | Switch the production consumer after your acceptance checks pass. | — |
| Rollback | event | Retain the previous configuration until the parallel-run window closes. | — |
Migration facts
last reviewed 2026-07-28
The Jito shutdown date
The official Jito documentation says the hosted ShredStream service will shut down on September 5, 2026. Jito describes the service as one that “delivers the lowest latency shreds from leaders on the Solana network.”
That notice creates an upstream deadline. It does not change the Jito proxy code or the raw Solana shred format. Plan the move early enough to observe both feeds under live load.
Map the configuration
| Concern | NoLimitNodes V1 |
|---|---|
| Receiver | Your Jito-compatible proxy or client |
| Target | One public IPv4 and UDP port |
| Provisioning | Automatic from the dashboard |
| Network authentication | Destination IP and port only |
| Firewall | Allow inbound UDP on the configured port |
| Feed | Solana mainnet raw shreds |
Follow the client configuration guide and the firewall guide.
Validate with a parallel run
Send each upstream into an isolated receiver or tag packets before they enter shared processing. Compare slot coverage, shred indexes, reconstructed entry counts, duplicate rate, missing-set rate, and time from packet receipt to decoded transaction.
Set acceptance criteria first
Decide what your workload accepts before you view results. Raw UDP cannot promise ordering, replay, or commitment. Your validation should test your receiver’s behavior under those conditions.
The official Jito proxy repository remains the reference for the compatible receiving path.
Cut over and keep a rollback
Move one production consumer first. Watch packet receipt, reconstructed slots, decode errors, process memory, CPU, and downstream decisions. Expand only after the same checks pass in production.
Keep the previous receiver settings and deployment artifact until the validation window ends. If a check fails, restore the former path and preserve packet samples for diagnosis.
You can provision the NoLimitNodes feed during the Ultra trial from the Shredstream product page.
Frequently asked questions
Related products
Test your receiver before the shutdown
The Ultra trial includes one Shredstream destination. Provision it automatically and run both paths before cutover.