[ Open Source + Non-consensus + Shreds ]
The same shreds, on a shorter path.
Raw mainnet shreds for validators, trading desks, and Solana apps.
A second path to mainnet shreds, running beside Turbine rather than instead of it. One 1,500 USDC invoice, three ways in: validators take them on TVU, desks over QUIC, apps through JSON-RPC and TxFeed.
Three doors on one shred invoice.
Validators, trading desks, and Solana apps share one 1,500 USDC plan. Website CDN, object storage, and Pipe Live are separate products — see Website CDN, object storage, and Pipe Live.
Validator ingest and origin
Shreds arrive on the UDP TVU port stock Agave already listens on — no fork, no patch. While your node is leader it can also publish its own shreds to the fleet (an extra destination) on Jito-Agave, Frankendancer, or Harmonic. Stock Agave has no extra destination, and ingest works fine without one.
Raw shreds for desks
QUIC from anywhere, or UDP in a colo. Trading desks run their own decoder on their own keys and send TPU-QUIC toward the next leader, landing on the same shreds they read. What 1,500 USDC buys is the feed itself, not a bot that trades on it.
RPC, TxFeed, and watch
A JSON-RPC URL, webhooks, and TxFeed — a subscription to transactions as the shreds carrying them arrive. Watch a wallet or paper-trade a strategy before risking funds, replay the last 24 hours from archive, and hydrate a new node from the fleet instead of a public snapshot. No TVU port to bind and none of the full-feed bandwidth. Strategy templates are 20 USDC each and run on top of this feed.
Leader-aimed send
You sign locally and the serving POP forwards TPU-QUIC at upcoming leaders, so your transaction takes the same short path the feed came down. The dashboard shows the result as submit slot → landed slot, confirmed against the shreds themselves. This is a path to the next leader; leaders still choose, and dropped is a real outcome.
Open-source client
The receiving client is open source and fully auditable — Reed-Solomon recovery, slot reassembly, and a decoder validated against mainnet. The feed it receives is a paid subscription.
Non-consensus by design
Your validator votes exactly as it does today. SolanaCDN runs out-of-band and leaves block production, consensus logic, leader scheduling, and voting rules untouched.
Fail-safe by default
If a POP goes away, your node keeps running on native Turbine without noticing. Feed operations are non-blocking and never own the TVU socket.
How SolanaCDN gives your validator an edge
Download plus upload on the 1,500 USDC shred plan. No fork, no validator patch, and native Turbine stays in place.
No fork and no validator patch. Your node keeps its existing TVU, gossip, and repair paths. SolanaCDN is an out-of-band UDP feed aimed at that TVU socket.
[ Stock Agave / RPC — no fork ]
[ agave-validator --ledger <path> contact-info ]
[ curl -X POST …/agent/heartbeat ]
[ POP → raw UDP → your TVU port ]
[ --shred-receiver-address <pop-ip>:<tvu-port> ]
Stock Agave ingest
No adapter. Register UDP TVU, heartbeat from that host, and Agave ingest does the rest. Disable the feed anytime without touching the node.
Origin upload
Your node publishes to the fleet only during its own leader slots, and only on Jito-Agave, Frankendancer, or Harmonic. Stock Agave has no extra destination.
Fail-safe fallback
The POP writes into a socket Agave already owns — the client never binds TVU. Switch the feed off, or lose the POP entirely, and the node is simply back to Turbine alone.
Technical Architecture
Consensus
Non-consensus; consensus and voting rules unchanged
Interference
Does not delay Turbine, Gossip, or Repair paths
Resources
CPU usage is workload-dependent
Networking
Non-blocking, best-effort operations
Built to run on any
modern validator setup
Deployment
Stock Agave / unmodified RPC node
Mainnet-beta compatible
Out-of-band UDP shred feed into TVU
Laptops use QUIC — no public TVU required
Prometheus-compatible metrics
Open-source client, on-chain billing
Operational bounds
CPU usage is workload-dependent
Memory bounded by config (e.g., FEC decoder caps)
Disk footprint is workload-dependent
≈13.5 MB/s only if you take the full shred feed
Fallback: multi-POP + transport failover
Stock Agave / RPC
&
Prometheus metrics
Mainnet-beta
&
Linux
Globally distributed POPs
Closer is faster. Shreds, sites, objects, and live streams all serve from the POP nearest whoever is asking.
north america
new york
San Francisco
Dallas
Europe
London
Frankfurt
Amsterdam
Asia Pacific
tokyo
Singapore
Sydney
A faster network layer, built on the public internet
SolanaCDN uses Pipe's neutral, out-of-band relay and aggregation layer. Does not influence consensus or transaction ordering.
Long-Distance Optimization
Intercontinental relay optimization
Relay paths are optimized across continents to reduce shred-delivery variance under network load.
Parallel Delivery
Parallel delivery
Multi-POP paths provide redundancy and more consistent shred relay alongside native gossip.
cpu
Workload-dependent CPU
CPU scales with how much of the feed you take, and stays inside the caps your config sets.
memory
Bounded memory footprint
Memory is bounded by config — FEC decoder caps set the ceiling.
network
Shred-feed bandwidth
Bandwidth follows what you subscribe to. Taking every data and coding shred is the heavy case — see Operational bounds for the figure. JSON-RPC and TxFeed are nowhere near it.
collection
The Solana parent captures Turbine and shred arrival at the POP. Gossip, TVU, and TPU stay here.
upload
Leader origin is extra-dest into the parent TVU — not a billed mesh hop.
fanout
POPs relay shreds across the mesh through the fastest measured paths.
download
Download: your validator’s TVU port, or a QUIC session. Desks and laptops do not register TVU.
injection
Injection is Path A: the POP writes shreds to the public UDP TVU.
SolanaCDN uses Pipe's neutral, out-of-band relay and aggregation layer. Does not influence consensus or transaction ordering.
Intercontinental relay optimization
Relay paths are optimized across continents to reduce shred-delivery variance under network load.
Parallel delivery
Multi-POP paths provide redundancy and more consistent shred relay alongside native gossip.
CPU and memory are workload-dependent and bounded by config. All shred-path network operations are non-blocking and best-effort.
Workload-dependent CPU
CPU scales with how much of the feed you take, and stays inside the caps your config sets.
Bounded memory footprint
Memory is bounded by config — FEC decoder caps set the ceiling.
Shred-feed bandwidth
Bandwidth follows what you subscribe to. Taking every data and coding shred is the heavy case — see Operational bounds for the figure. JSON-RPC and TxFeed are nowhere near it.
Shred download is TVU or QUIC. Validator injection is Path A only. Leader origin upload is extra-dest, not mesh “upload.”
The Solana parent captures Turbine and shred arrival at the POP. Gossip, TVU, and TPU stay here.
Leader origin is extra-dest into the parent TVU — not a billed mesh hop.
POPs relay shreds across the mesh through the fastest measured paths.
Download: your validator’s TVU port, or a QUIC session. Desks and laptops do not register TVU.
Injection is Path A: the POP writes shreds to the public UDP TVU.
One shred invoice.
Shred Feed
Three doors, one invoice: validators take shreds on TVU and can publish their own, trading desks read raw shreds over QUIC, and apps get JSON-RPC, webhooks, and TxFeed. One included shred stream (UDP or QUIC); extra streams are a 1,500 USDC add-on. Live shreds and included RPC are never paywalled.
Strategy Catalog
First-party templates — DCA, entry and exit triggers — that run in your client, on your keys, against your live feed. Templates, not a desk. They do not include the feed.
Enterprise
Dedicated infrastructure and tailored support for teams with specific performance or operational requirements.
HOW BILLING WORKS
Strictly prepaid
Access runs exactly as long as a paid period covers it. Nothing renews itself, nothing charges automatically, and no payment method is stored — you send USDC when you choose to.
Verified on chain
Every payment is checked against the chain itself — amount, token, and destination. If a sender deducts a fee, the difference is credited as a partial payment and your dashboard shows exactly what remains.
Leader-aimed send
Included in the same 1,500 USDC, with HTTP JSON-RPC. You sign locally; the serving POP forwards TPU-QUIC against the current leader schedule. That is a path to the next leader, not purchased inclusion, Jito bundles, or stake-weighted QoS.
Landing you can see
solanacdn trade confirms landing from the shred feed. The dashboard shows submit slot → landed slot. /status publishes targeted, included, and dropped per leader. Dropped is a real outcome.
Your questions,
answered
Your validator votes exactly as it does today. The feed is out-of-band and non-consensus: it leaves block production, consensus logic, leader scheduling, and voting rules untouched.