Solana ShredStreamRaw data. Your pipeline.
Receive raw Solana data and coding Shreds over UDP from Frankfurt or Amsterdam. SolBrisk ShredStream is for teams that want to reconstruct ledger entries and decode transactions in their own application.
- 01Solana networkData and coding Shreds
- 02SolBrisk · FRA / AMSRaw UDP delivery
- 03Your applicationReceive → reconstruct → decode
Solana Shreds, before your decoding stage
Shreds are fragments used in Solana's block propagation. Data Shreds carry ledger data; coding Shreds provide erasure-recovery redundancy. A raw Shred stream gives you these packets rather than a pre-decoded transaction API.
This is a fit when you already operate a receiver and need control over deduplication, reconstruction and transaction parsing. UDP delivery can include reordering, duplicates or gaps, so receiver buffers and decoding behavior are part of the integration. Reconstructed transactions do not by themselves prove successful execution or finality.
Prefer structured account and transaction updates? Explore Solana gRPC.
Connect your UDP receiver
- Start a receiver on an unused UDP port and allow that port through your server's firewall.
- In the console, choose Raw Shred, your region, your server's public IPv4 address and the listening port.
- Copy the endpoint-verification command from your subscription, run it on the receiving server and enter the code it prints. Activation starts delivery and the subscription period.
- Keep your receiver running and feed packets into your decoder. Our open-source Rust decoder includes UDP receiving, reconstruction and JSONL output.
Follow the full connection guide for commands and examples, or view current pricing.
Frankfurt or Amsterdam: test from your server
Both services are available in Frankfurt and Amsterdam. Choose based on your receiver's location and actual network route. A geographically closer region is a useful starting point, but routing and local load can change which feed reaches your application first.
Subscriptions are managed separately by service, IP and region, with daily or 30-day billing in USDC and manual renewal. Check current service status before running your comparison.
Receive, decode and compare Shred feeds
The Rust Shred decoder reconstructs compatible native Merkle Shreds and emits entries and transactions. The separate latency tool compares matching Shreds received on different UDP ports of one server; on Linux it uses software kernel receive timestamps.
Read our Solana streaming latency guide for a repeatable setup and an explanation of percentiles, unmatched events and receiver bottlenecks.
Before you connect
Does a Shred stream return transaction execution results?
Raw Shreds carry ledger data, not a confirmed execution-result API. Decoding a transaction is different from verifying its execution or finality. Use the appropriate state or transaction-status source for those checks.
Can I receive on an existing trading port?
Use an unused diagnostic port when evaluating a feed. The example tools exclusively bind their port; they do not alter forwarding rules or share an existing socket. Keep live receivers separate from tests.
How should I evaluate latency?
Compare matching events on the same receiver and keep the full report, including coverage and local diagnostics. A first-arrival difference is a relative measurement, not absolute latency from the Solana leader. Repeat at different times before choosing a route.