FAQ
Questions about the plans and setup
Short answers first. If yours is missing, email support.
Every question, in one place.
Something we did not cover? Email support and a person on our team will answer.
A shred is one of the small packets a Solana leader cuts its block into before Turbine spreads it across the network. Every RPC node and indexer works from those packets once they are put back together. Receiving shreds directly lets your own code watch a block form while its packets are still landing.
Only in the route. Ultra Low Latency Shreds go from our server straight to yours, with nothing in between. Standard Shreds carry the identical stream, but it passes through our relay before it reaches you. Because Ultra skips that hop, it reaches you sooner. We publish no timing figures.
A public IPv4 address with a UDP port our packets can reach, and a program listening on it. You do not need to run a validator or hold stake. To get entries and transactions rather than raw packets, you also need your own decoder.
One payment buys 30 days of delivery to one destination: a single IPv4 address with one UDP port. Your 30 days begin when the payment clears. Want a second destination? Buy it as its own order, at the price of its plan.
At our Eeze checkout. You pay in USDC on Solana, and we count a payment once Solana has finalized it. Cards are not accepted, and there is no account to open first.
No. Three days before your 30 days run out, we send you a payment link for another 30. We never take a payment on our own. Paying ahead costs you no time: the new 30 days are added after the current ones finish.
Yes. You can try either plan free for 2 hours, one time per person: email support@solanashreds.xyz the IPv4 address and UDP port to test, and your 2 hours begin once we confirm packets reach it.
If we do not deliver the stream you paid for, you get the whole payment back, with no fees kept. To ask, email support@solanashreds.xyz with your order reference. Details are on the refunds page.
Shreds are sent from Frankfurt, Germany. Pick a server with a good network path to Frankfurt; a shorter path means the packets spend less time travelling.
No. We send raw shred packets and decode nothing. Your pipeline reassembles them, recovers missing pieces from the erasure codes and parses entries and transactions. That split is deliberate: you choose the decoder, the language and what you keep.
No. The stream is a live forward over UDP with no backfill, history, resend or replay. If your receiver stops reading, the packets sent in that time are gone for good, so run it continuously and size its socket buffer generously.
We send a verification packet to the IPv4 address and UDP port you gave us. Reply with the token inside it, and we switch the stream on once it matches. If the packet never arrives, we can send a new one, and a new token replaces the old one.
Each datagram is at most 1228 bytes, small enough to cross the internet without being split into fragments. Read with a buffer of at least that size. Apart from verification packets, everything that arrives on the port is stream data.
No. The source UDP port is not fixed, so a rule that expects one particular source port can silently drop the stream. Allow inbound UDP to the destination port you gave us instead.
Yes. To move the stream to a new IP or port, email support. We check the new address the same way before we stop sending to the old one.
Feed the stream to as many of your own servers as you like. Passing it to another person or company needs our written agreement first.
No. There is no account, dashboard, API key or SDK. Our support team sets up each destination by hand once you have paid and emailed us the address. Delivery is tied to that address, not to a key.
No. We deliver raw shreds over UDP only. Your own receiver or any shred decoder turns them into entries and transactions.
Give us an address.
We send the shreds.
Pick a plan, pay in crypto, then tell us which IPv4 address and UDP port should get the stream.