Jito Shreds

AllenHark Jito Shreds is a drop-in replacement for Jito's official ShredStream feed, which shuts down on September 5, 2026. You keep your existing shredstream-proxy binary and your existing keypair — you register your keypair's public key with AllenHark and repoint one flag.

This page covers setup end-to-end: prerequisites, installing the AllenHark proxy build, registering your pubkey, configuring the proxy, and verifying shreds are flowing.

Why you need to do this

Jito announced the ShredStream deprecation in July 2026. After September 5, 2026, Jito's own block-engine-url stops accepting connections from shredstream-proxy — the upstream binary refuses to run past the shutdown date. If your infrastructure depends on that feed (searchers, memecoin sniper bots, market makers, analytics platforms ingesting raw shreds), you need a block-engine endpoint that still exists after that date.

AllenHark maintains a kill-switch-free fork of the proxy and runs the gateway it talks to, so nothing else in your pipeline changes.

Prerequisites

• An existing Solana keypair — the same one your shredstream-proxy already authenticates with. You do not need to generate a new one.
• Your keypair's public key (base58-encoded), to register for whitelisting.
• An AllenHark account (sign in to the console).

Step 1 — Install the AllenHark proxy

Upstream's shredstream-proxy binary refuses to start once Jito's shutdown date passes, so you need AllenHark's maintained fork. It is a kill-switch-free build of Jito's shredstream-proxy (Apache-2.0), published at:

Clone and build it exactly as you would the upstream binary:

1# Build prerequisites (Ubuntu): build-essential clang libclang-dev cmake protobuf-compiler
2git clone https://github.com/AllenHark-Inc/allenhark-shredstream-proxy.git
3cd allenhark-shredstream-proxy
4cargo build --release

The CLI flags, environment behavior, and authentication flow (challenge/JWT + heartbeat) are unchanged from upstream — this is the same protocol Jito's proxy speaks, just without the forced shutdown.

Step 2 — Register your keypair's public key

Shreds access is whitelisted by pubkey, not by IP. In the AllenHark console:

1. Navigate to Jito Shreds.
2. Submit your keypair's public key (not the private key — never share your private key with anyone, including AllenHark).
3. Start your 24-hour free trial, or subscribe directly.

Only one pubkey may be registered per subscription, and each user may hold one Jito Shreds subscription at a time.

Step 3 — Point --block-engine-url at AllenHark

Update your proxy's block-engine flag to the AllenHark gateway endpoint. AllenHark currently serves the Frankfurt (fra) region at https://fra.jito.allenhark.network:

1./target/release/jito-shredstream-proxy shredstream \
2  --block-engine-url https://fra.jito.allenhark.network \
3  --auth-keypair /path/to/your/keypair.json \
4  --desired-regions frankfurt \
5  --dest-ip-ports 127.0.0.1:8001,127.0.0.1:8002

The binary is jito-shredstream-proxy and takes the shredstream subcommand — the same CLI as Jito's upstream proxy. Your public IP is auto-detected for the heartbeat; no --public-ip needed on a normal host.

• --block-engine-url — the only value you change. Set it to https://fra.jito.allenhark.network (the Frankfurt gateway; also shown in your console dashboard).
• --auth-keypair — unchanged. Point it at the same keypair file you registered the pubkey from.
• --desired-regions — set to frankfurt. AllenHark currently serves the Frankfurt region only; additional regions will be announced as they come online.
• --dest-ip-ports — unchanged. This is where the proxy forwards decoded shreds locally; your downstream consumer keeps listening here exactly as before.

Nothing downstream of --dest-ip-ports changes. Your socket, your deshredding code, and your consumer processes are untouched — AllenHark's gateway speaks Jito's exact protocol, including the auth challenge/JWT exchange and heartbeat.

Step 4 — Verify shreds are flowing

Once the proxy is running against the new --block-engine-url:

• Check the proxy's own logs for a successful auth handshake (challenge signed, JWT issued) and an established heartbeat.
• Confirm packets are arriving on your --dest-ip-ports listener, the same way you'd have verified the upstream Jito feed.
• In the AllenHark console, your Jito Shreds subscription status should show as active and connected.

If shreds aren't arriving, double check that the registered pubkey matches the --auth-keypair the proxy is running with — whitelisting is strictly pubkey-based.

Trial & Pricing

• 24-hour free trial — validate the full migration (auth + shred delivery) before paying anything.
• $50/month thereafter, billed per subscription.
• One subscription per user, one pubkey per subscription.
• All traffic is served from the single Frankfurt gateway at https://fra.jito.allenhark.network. The --desired-regions value is not used for routing today — set it to frankfurt.

FAQ

Do I need a new keypair? No. Register the pubkey of the keypair your shredstream-proxy already signs with.

What exactly changes in my config? One flag: --block-engine-url. Everything else — --auth-keypair, --dest-ip-ports, your downstream code — stays the same.

Is this the same protocol as Jito's ShredStream? Yes. The AllenHark proxy is a fork of Jito's shredstream-proxy and speaks the identical auth challenge/JWT and heartbeat protocol against the AllenHark gateway.

What happens if I don't migrate before September 5, 2026? Jito's ShredStream stops accepting connections, and the upstream shredstream-proxy binary refuses to run past the shutdown date. Your feed goes dark until you switch to a maintained proxy build and endpoint.

Can I keep using my own build of the proxy? No — after the shutdown date, only a maintained fork (like AllenHark's) will run. Use the AllenHark proxy binary linked in Step 1.

Where's the source code? github.com/AllenHark-Inc/allenhark-shredstream-proxy — Apache-2.0, a kill-switch-free fork of Jito's shredstream-proxy.

Related

• Jito Shreds product overview — pricing, FAQ, and signup
• ShredStream — AllenHark's direct UDP shred feed (no proxy required)
• Migration guide (blog) — the full story on why Jito ShredStream is shutting down and how to move

Support

For migration help, join our Discord.