> For the complete documentation index, see [llms.txt](https://docs.triton.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.triton.one/solana/real-time-streaming/shred-streaming.md). # Shred Streaming Shred Streaming sends a full, deduplicated feed of raw Solana shreds to your own IPs from five locations, before blocks are assembled. {% hint style="info" %} Triton Shred Streaming is available on request. Contact us through the [Customer Portal](https://customers.triton.one/) to have it enabled on your account. {% endhint %} Shred Streaming delivers Solana shreds at the earliest point the data exists on the network: before a block is assembled, before it is replayed, and before it appears in any RPC or gRPC stream. Shreds are the fragments a leader breaks its block into and fans out across the network. * **Used for:** trading systems, MEV searchers, market makers, and any latency-sensitive backend that reconstructs blocks itself. * **Key feature:** a **full shred feed, deduplicated**. You receive every shred we see, and you typically receive each one only once. ## Is Shred Streaming for me? Processing raw shreds is an advanced feature and requires custom software development on your end. It offers no filtering, and relies on forward error correction to handle any dropped or missed packets. An alternative to raw shreds is the [SubscribeDeshred](/solana/real-time-streaming/deshred-transactions.md) gRPC subscription, available on our Riptide and regular gRPC endpoints. SubscribeDeshred uses the same shred sources as Shred Streaming, but processes the shreds back into transactions for you and offers filtering. ## How to use Shred Streaming You need to run software on your end that can decode and process raw shreds. To get you started, this repository has a full working code sample that reassembles incoming shreds into transactions: {% embed url="" %} Use it to verify that your shred stream is working, and as a starting point for your own receiver code. ## Where you can receive shreds Shred Streaming is available in five locations: | Region | Location | | ------ | --------- | | US | New York | | EU | London | | EU | Amsterdam | | EU | Frankfurt | | AP | Tokyo | You can receive shreds in any of these locations, each independently of the others. Each organization starts with one destination (an IP address and port in one datacenter); contact support to raise the limit. ## Where the shreds come from Shred Streaming aggregates shreds from several sources, so you are not dependent on a single vantage point into the network: * **Triton validators:** shreds observed directly by the validators we operate. * **DoubleZero Edge:** through a partnership with DoubleZero, we receive shreds from their Edge network. * **Partner validators:** additional validators we work with, spread across the network. * **Turbine:** for any validator we do not partner with and which is not sending its shreds through DoubleZero Edge, we receive its shreds via Turbine. Because the same shred usually arrives from more than one of these sources, the feed is deduplicated before it reaches you: whichever copy arrives first is the one you get, and later duplicates are discarded. ## How it works Shred Streaming runs on a custom network built specifically for shred distribution. * **Shortest-path ingestion.** Our receivers are positioned so that shreds reach our network over the shortest available path from the leader, rather than over whatever route the public Internet happens to pick. * **Custom low-latency path.** Once a shred is inside our network, we distribute it between datacenters over Triton's own path instead of the public Internet. * **Multicast distribution.** Within each datacenter, shreds are distributed over multicast to the hosts that forward them to your destinations. * **Dedicated network ports.** We use dedicated shred distribution hosts with multiple dedicated network ports to reduce distribution latency. The result is that a shred picked up in one location is available to subscribers in every other location very shortly after we first see it. ## Getting started {% stepper %} {% step %} ### Request access Contact customer support through the [Customer Portal](https://customers.triton.one/) and ask to have Shred Streaming enabled on your account. {% endstep %} {% step %} ### Configure your destinations Once it is enabled, a "Shred stream IPs" card appears on your mainnet-shared subscription page in the Customer Portal. Click "Add shred stream IP" and enter the **IP address and port** you want shreds delivered to (a public IPv4 address; the port defaults to `8002`), optionally add a label, select the datacenter, and click "Add IP". Add a destination for each datacenter you want to receive in, up to your limit. Shortly after you add them, shreds start arriving from our source IP, `67.209.53.15`. {% endstep %} {% step %} ### Start receiving Make sure the hosts you list can accept the traffic: the destination IPs must be reachable and the ports open. If you have an ingress firewall, allow traffic from `67.209.53.15`. {% endstep %} {% endstepper %} {% hint style="warning" %} A full shred feed is high-bandwidth and bursty. Provision the receiving hosts and their network capacity accordingly, and place them as close as possible to the location you subscribe from. {% endhint %} ## Questions For help with sizing, location selection, or anything else about Shred Streaming, reach out through your Triton CS channel or the [Customer Portal](https://customers.triton.one/). *** :life-ring: Contact support by clicking the chat icon in your [customer dashboard](https://customers.triton.one)\ :briefcase: Sales questions? [Contact us](https://triton.one/contact)\ :sparkles: AI agent? Read [llms.txt](https://docs.triton.one/llms.txt)\ :rss: Follow updates: [Blog](https://blog.triton.one) · [X](https://x.com/triton_one) · [YouTube](https://www.youtube.com/@triton_one_ltd) · [Telegram](https://t.me/tritonone) · [GitHub](https://github.com/rpcpool)