[ Opt-in + Non-consensus + Reliability & Telemetry ]
SolanaCDN. Shreds, observable.
Improves vote propagation reliability and surfaces cluster activity in near real time. Optional shred mirroring for observability and diagnostics.
Touches nothing sacred: no consensus, no block production, no leader scheduling. Turbine, Gossip, and Repair run untouched.
Reliability and telemetry for Solana validators
SolanaCDN is an opt-in, non-consensus reliability and telemetry companion embedded in open-source Solana validator codebases, improving vote propagation visibility and reliability, with optional shred mirroring for observability and diagnostics.
Vote propagation reliability
Improves vote propagation reliability by providing faster and more consistent vote relay paths and reducing propagation variance under network load.
Telemetry & visibility
Gives earlier visibility into cluster voting activity and optional shred arrival timing using Prometheus-compatible metrics.
Open-source integration
Integrated into open-source Solana validator codebases. If SolanaCDN is unavailable, the validator continues operating normally.
Prometheus metrics
Track vote propagation and shred reception telemetry using Prometheus-compatible metrics.
Non-consensus by design
Does not modify block production, consensus logic, leader scheduling, or voting rules.
Non-blocking networking
All network operations are non-blocking and best-effort.
No interference
Does not delay or interfere with normal Turbine, Gossip, or Repair paths.
Neutral relay layer
Pipe provides a neutral, out-of-band relay and aggregation layer for observability.
A five-step path to reliability and visibility
Your validator runs normally. SolanaCDN is opt-in and non-consensus, and can be enabled or disabled independently.
[ Validator (normal) + SolanaCDN (opt-in) ]
[ SolanaCDN → Telemetry (votes + shreds) ]
[ SolanaCDN → Best-effort relay → Nearest POP ]
[ POPs → Aggregation → Metrics ]
[ SolanaCDN off → Validator continues ]
Opt-in
SolanaCDN can be disabled without impacting validator operation.
Resource bounded
CPU usage is capped and isolated (<1 core).
Best-effort
All network operations are non-blocking and best-effort.
Technical Architecture
Consensus
Non-consensus; consensus and voting rules unchanged
Interference
Does not delay Turbine, Gossip, or Repair paths
Resources
CPU capped and isolated (<1 core)
Networking
Non-blocking, best-effort operations
Built to run on any
modern validator setup
Deployment
Open-source validator codebases (SolanaCDN integrated)
Opt-in, non-consensus operation
Mainnet-beta compatible
Prometheus-compatible metrics
Optional shred mirroring
Operational bounds
CPU capped and isolated (<1 core)
≈100 MB RAM (typical)
+50 MB disk (typical)
Bandwidth varies by mode
Fail-safe fallback (validator continues)
Open-source validator codebases
&
Prometheus metrics
Mainnet-beta
&
Linux
Globally distributed POPs
To reduce propagation variance, select the POP closest to your hardware. Need help? Contact support
north america
new york
San Francisco
Dallas
Europe
London
Frankfurt
Amsterdam
Asia Pacific
tokyo
Singapore
Sydney
SolanaCDN is designed for consistent relay and observability
SolanaCDN uses Pipe’s neutral, out-of-band relay and aggregation layer. It does not influence consensus or transaction ordering.
Long-Distance Optimization
Long-distance optimization
Intercontinental relay paths are designed to reduce vote propagation variance under network load.
Parallel Delivery
Parallel delivery
Multi-POP paths improve redundancy and provide more consistent relay behavior.
cpu
CPU capped (<1 core)
CPU usage is capped and isolated (<1 core).
memory
Bounded memory footprint
Designed to keep memory usage predictable (e.g., ~100 MB RAM).
network
Optional shred mirroring bandwidth
≈115KB/slot (96 shreds × ~1.2 KB each)
collection
SolanaCDN observes vote propagation telemetry and optional shred arrival timing.
upload
Signals are relayed to a nearby POP over non-blocking, best-effort transport.
fanout
POPs relay data across the network and aggregate telemetry for observability.
download
Operators and tooling can query aggregated telemetry for earlier visibility into cluster activity.
injection
Optional out-of-band relay path can forward shreds to the validator’s TVU port for normal processing.
SolanaCDN uses Pipe’s neutral, out-of-band relay and aggregation layer. It does not influence consensus or transaction ordering.
Long-distance optimization
Intercontinental relay paths are designed to reduce vote propagation variance under network load.
Parallel delivery
Multi-POP paths improve redundancy and provide more consistent relay behavior.
CPU usage is capped and isolated (<1 core). All network operations are non-blocking and best-effort.
CPU capped (<1 core)
CPU usage is capped and isolated (<1 core).
Bounded memory footprint
Designed to keep memory usage predictable (e.g., ~100 MB RAM).
Optional shred mirroring bandwidth
≈115KB/slot (96 shreds × ~1.2 KB each)
SolanaCDN provides a best-effort relay and telemetry flow for vote propagation visibility, with optional shred mirroring for diagnostics.
SolanaCDN observes vote propagation telemetry and optional shred arrival timing.
Signals are relayed to a nearby POP over non-blocking, best-effort transport.
POPs relay data across the network and aggregate telemetry for observability.
Operators and tooling can query aggregated telemetry for earlier visibility into cluster activity.
Optional out-of-band relay path can forward shreds to the validator’s TVU port for normal processing.
Simple, transparent plans for validators
Free Beta
Opt-in participation for validators during the beta program (terms may apply). We compensate operators for infrastructure participation and operational overhead.
Standard
Estimated range per validator after beta. Performance varies by network conditions, geography, and validator configuration.
Enterprise
Custom deployments and tailored support.
PROGRAM DETAILS
During beta
Free for mainnet validators during beta (terms may apply).
After beta
Early adopters may receive a discount for the first year.
Pricing
We plan to announce usage-based pricing at least 60 days before the beta ends.
Compensation
We compensate operators for running and maintaining SolanaCDN as part of a reliability and telemetry program. Payments are for infrastructure participation and operational overhead.
Policy
No surprise charges — you choose whether to continue, with advance notice.
Your questions,
answered
No. It is completely out-of-band and non-consensus. SolanaCDN does not modify block production, consensus logic, leader scheduling, or voting rules.