🧩 Decoded Shred Stream
A Decoded Shred Stream delivers Solana transactions already reconstructed: deshredded and reassembled on our nodes, then sent to your server in the standard Solana wire format. No FEC/Merkle/deshredding pipeline on your side — transactions arrive ready for your parser, at sub-millisecond latency.
🧭 Who It Is For
Choose Decoded Shred Stream if:
- You already have a transaction parser. The payload is a standard wire-format transaction (a bincode-serialized
VersionedTransaction). - You want standard-format ingestion without shred infrastructure. Erasure recovery (FEC), Merkle verification, and deshredding are done on-node for you — there is nothing shred-specific left to build or maintain.
- You need pre-confirmation data with minimal integration effort. Transactions are reconstructed from shreds before block confirmation, so you keep the timing edge of the shred feed with a fraction of the engineering.
⚖️ Positioning: Raw Shreds vs Decoded
ShredStream.com offers two products along the same axis — how much decoding is done for you:
| Product | You receive | You build | Delivery |
|---|---|---|---|
| Raw Shred Stream | Raw Turbine shreds | Deshredding + parsing + interpretation | UDP |
| Decoded Shred Stream | Wire-format transactions | Parsing + interpretation | UDP or gRPC |
- Choose Raw Shred Stream for byte-level control over everything, including reconstruction.
- Choose Decoded Shred Stream to skip reconstruction but keep your own transaction parsing.
🚀 Latency
Deshredding happens on-node, straight from the shreds — not in a downstream service. The reconstructed transaction leaves the node within microseconds of the raw shred feed itself. You give up essentially nothing in latency and gain a standard, parser-ready payload.
📡 Delivery Modes
- UDP — transactions are pushed as datagrams to the IP and port you configure, each prefixed by a compact binary header (16 bytes) and the 8-byte slot — the transaction starts at byte 24. See Receiving Decoded Transactions.
- gRPC — a connection-oriented, outbound stream with server-side account filtering and ordered delivery, over the same sub-millisecond-latency transactions. See gRPC Delivery.
🧰 Official Clients
One package per language, covering both delivery modes with the same API — bind the port (UDP) or connect with your endpoint and token (gRPC), then iterate transactions with their slot and signatures. Reconnection, filter re-send and seq gap detection are handled for you.
| Language | Install | Package |
|---|---|---|
| JavaScript / TypeScript | npm install decoded-shredstream | npm |
| Python | pip install decoded-shredstream | PyPI |
| Rust | cargo add decoded-shredstream | crates.io |
| Go | go get github.com/shredstream/decoded-shredstream-go | GitHub |
Before execution. These transactions are captured from the shreds, before the block is executed: they carry no status, logs, balance changes or inner instructions, and some of them will fail on-chain. Use a post-execution source when you need confirmation.
📖 In This Section
- Receiving Decoded Transactions — the UDP envelope, offsets, gap detection, and a minimal decoder.
- gRPC Delivery — endpoint, token metadata, account filters, and
VersionedTransactiondeserialization.