What does a shred stream deliver?
Shreds carry pieces of Solana block data. A raw feed delivers those pieces to your receiver; your software handles decoding and the rest of its data pipeline. Observing a transaction in this data is different from proving its execution result or finality.
Lumios exposes the raw feed as ShredStream. This page describes that dashboard product; it does not imply access to a separate provider’s similarly named service.
Prepare the receiver before registration
The documented raw feed sends UDP datagrams to a public IPv4 address and port that you operate. Choose an enabled location and register the destination in Endpoints → ShredStream. Confirm traffic at the network and application layers before adding decoding.
Expect loss, duplicate packets, and reordering. Receive order is not a reliable transaction ordering rule. Keep packet handling small and measure socket drops, queue depth, and processing progress.
- Verify the destination and inbound network rules.
- Confirm the decoder understands the received shred format.
- Decide how to detect gaps and recover incomplete application state.
- Test bursts and reconnect or registration changes before depending on the feed.
Raw shreds or decoded transactions?
Choose raw shreds when you want to own the decoding pipeline. Pulse provides a separate decoded path over QUIC with signature-first and full-transaction modes. Yellowstone offers filtered subscriptions for backend data consumers.
Start with your output requirement: packet bytes, transaction messages, or filtered updates. Compare the operating cost of each consumer, not only its first-event timing. Available products and locations are shown for your selected access.
Common questions
Are shreds the same as preconfirmations?
No. Shreds are data. A preconfirmation claim needs an explicit definition of the signal, issuer, and guarantees. Use the guide below to evaluate those differences.
Do I need to operate a receiver?
For the raw UDP feed, yes. You need a reachable receiver and software that handles the payload. If you need decoded output, compare the separate Pulse and Yellowstone paths.
Sources & documentation
Consult the current specifications for endpoint behavior and supported features.