# Jito-Compatible Client Configuration

> Connect an existing Jito-compatible ShredStream receiver to NoLimitNodes raw UDP delivery.

Canonical: https://nolimitnodes.com/docs/api-reference/shredstream/jito-client

NoLimitNodes sends raw shreds in a format compatible with the Jito proxy and client receiving path. Keep your deshredder and strategy pipeline. Change the upstream destination provisioning.

## Map your configuration

| Existing concern | NoLimitNodes setting |
|---|---|
| Receiver listen address | `0.0.0.0:` |
| Delivery target | Your public `IPv4:UDP_PORT` |
| Upstream authentication | None inside the UDP packet |
| Network | Solana mainnet |
| Provisioning | Dashboard, automatic |

## Run the receiver

Bind your Jito-compatible receiver to the local UDP port. If it runs behind network address translation, forward the public port to that local socket.

```bash
# Confirm the process is listening.
sudo ss -lunp | grep 20000

# Confirm packets reach the host.
sudo tcpdump -n -i any "udp and dst port 20000"
```

## Validate before cutover

Run the existing and replacement feeds in parallel. Compare:

- Slots and shred indexes observed
- Complete and incomplete erasure sets
- Reconstructed entries and transactions
- Duplicate and decode counts
- Receiver CPU, memory, queue depth, and packet drops

Tag each upstream before shared processing so deduplication does not hide a feed-specific gap.

See the [official Jito proxy repository](https://github.com/jito-labs/shredstream-proxy) for the receiver implementation. Jito's [official service documentation](https://docs.jito.wtf/lowlatencytxnfeed/) announces a September 5, 2026 shutdown of its hosted ShredStream service.