Reference
ShredStream is a UDP delivery service, not a request/response API. Blockspace pushes raw Solana shreds to the destination IP and port you registered. This page documents the wire format, regions, and operational behavior.
Transport
- Protocol — UDP
- Encoding — raw Solana shred bytes; no Blockspace-specific framing
- Source — Blockspace proxy nodes (one per region you subscribe to)
- Auth — IP allowlisting on Blockspace side. The destination IP/port you registered is the only target
Regions
Available regions:
| Region | Code |
|---|---|
| Frankfurt | FRA |
| Amsterdam | AMS |
| Tokyo | TYO |
| New York | NY |
| London | LON |
| Dublin | DUB |
| Singapore | SGP |
For lowest latency, host your listener in the same region as the source.
Provisioning
For each region, provide:
- Destination IP — your listener's public IP
- UDP port — the port your listener binds to
Format used in the dashboard:
FRA - 203.0.113.1:20000
AMS - 203.0.113.2:20000
NY - 203.0.113.3:20000
If your firewall filters incoming traffic on the listener port, allow Blockspace proxy IPs for each region. Proxy IPs are surfaced in the dashboard. They can change during maintenance or migration — you'll be notified with the updated list.
Wire format
Each UDP datagram is one Solana shred. The on-the-wire format matches what Solana validators produce — decode with any standard Solana shred parser.
Receiver software
There's no Blockspace-specific protocol. The recommended starting point is jito-labs/shredstream-proxy — drop-in receiver and forwarder for raw shreds.
Throughput and tuning
Tier-specific throughput numbers are surfaced in the dashboard. For all tiers, ensure your kernel UDP buffers are large enough:
sudo sysctl -w net.core.rmem_max=8388608
sudo sysctl -w net.core.rmem_default=8388608
Outage detection
UDP is connectionless — silence is ambiguous (idle chain or broken link?). Monitor packet rate at the application layer:
if packets_in_last_5s == 0 {
alert("shredstream receive stall");
}
If packets stop arriving, check the status page, confirm the destination IP/port in the dashboard, and verify your firewall still allows the current Blockspace proxy IPs.