ShredStream
Opt-in delivery of raw Solana shreds to an eligible OpenInfra server over a dedicated private UDP network.
Service contract
| Property | OpenInfra delivery contract |
|---|---|
| Eligible servers | Active or trialing VPS, VDS, and bare-metal servers |
| Transport | Raw UDP datagrams over an isolated private network |
| Destination | The server's assigned 10.250.0.x address on UDP port 20001 |
| Authorization | Per-server dashboard selection; no project API key |
| Control delay | Allow 30-60 seconds after enabling or disabling |
| Persistence | The private address remains reserved while delivery is off |
What the feed contains
A Solana leader encodes block data into data and coding shreds for propagation through the network. OpenInfra forwards the raw UDP shred datagrams received by its relay. The payload is not JSON, a parsed transaction object, a WebSocket message, or a gRPC response.
Your process must bind to UDP port 20001 and understand the Solana shred format. OpenInfra controls network delivery only; it does not start a listener or decoder inside your server.
How delivery works
- New VPS and VDS servers are provisioned with a disabled ShredStream interface and a reserved private address.
- Bare-metal delivery is prepared during manual provisioning; support assigns its private destination before customer controls become available.
- Enabling a server adds its private address to relay discovery; disabling removes it without releasing the address.
- The relay refreshes the selected destinations periodically, so dashboard changes are not instantaneous.
- Suspended, canceled, deprovisioned, or otherwise ineligible servers are excluded from delivery.
Delivery semantics
UDP is connectionless and has no acknowledgement, replay, ordering, or completeness guarantee. Consumers must tolerate duplicates, gaps, and packets arriving out of order. A packet observed in ShredStream is pre-confirmation data and must not be treated as proof that a transaction landed.