Multi-stage compression pipeline
Versioned strategies (v1, v2, v3, hybrid, production_v3) and an XGBoost-tuned variant adapt to block payloads in real time. Real Solana mainnet blocks compress 15-25x with sub-millisecond encode latency.
v0.1 — production_v3 compression on mainnet blocks
A decentralized vault for Solana block data.
SolanaVault turns Solana archive storage into a peer-to-peer economy. A multi-stage compression pipeline shrinks blocks 15-25x with zero loss, while NNG transport, Kademlia discovery, and Byzantine consensus serve the data back through the standard Solana RPC API. Stop renting archive nodes — query a network that pays its own keep.
15-25:1
compression ratio
95%+
storage savings
13-85us
decompression
sub-ms
encode latency
~/solanavault
# Start the light client — drop-in replacement for mainnet-beta
$ ./target/release/vault-light-client start --balance 50000
[INFO] bootstrapping kademlia dht ... 217 peers
[INFO] gateway selected: vault://us-east-2.gw.cryptuon
[INFO] json-rpc listening on http://localhost:8899
# Point any Solana client at the local endpoint
$ curl -s http://localhost:8899 -d '{"jsonrpc":"2.0","id":1,"method":"getConfirmedBlock","params":[245000000]}'
{"jsonrpc":"2.0","id":1,"result":{ ... block 245000000 (146 bytes wire, decompressed in 28μs) ... }}
What you get
Built for production Solana workloads.
Every line of the stack is real, public, and benchmarked. The numbers below come from the same Rust workspace that powers your gateway.
Drop-in Solana RPC API
The light client exposes the same JSON-RPC surface as mainnet-beta. Swap your endpoint, keep your client libraries, ship today. getConfirmedBlock, getTransaction, getSignaturesForAddress — all present.
P2P transport on NNG
Binary messaging over NNG sockets gives microsecond inter-node latency. Kademlia DHT routes content addresses to the closest replica, with automatic failover and reputation-aware peer selection.
Byzantine consensus on data integrity
Every block served carries a cryptographic proof verified by a Byzantine quorum. Liars get slashed and lose reputation. Honest storage nodes earn consensus rewards on every retrieval.
Pay-per-use gateway economics
Light clients pay only for the queries they make. Gateway operators keep 85% of revenue; storage and consensus nodes earn the remaining 15%. No upfront commitments, no archive node TCO.
RocksDB-backed smart caching
The memory subsystem combines RocksDB persistence with a tiered cache manager and a memory pool sized for production. Hot blocks stay in RAM; warm blocks live in compressed pages; cold blocks come from the network.
Observable by default
tracing + tracing-subscriber for structured logs, Prometheus metrics via metrics-exporter-prometheus, and a dashboard API that powers both the TUI and web consoles. Governor-based rate limiting at every endpoint.
Architecture
Four roles, one network.
SolanaVault decouples the work of serving block data from the work of storing it, so each role can be priced and scaled independently.
- Applications — your existing code, untouched.
- Light client — exposes JSON-RPC locally, pays per query, caches hot blocks.
- Gateway nodes — relay requests for revenue; route through DHT to the closest replicas.
- Storage nodes — hold compressed blocks, vote in Byzantine consensus, earn rewards.
┌─────────────┐ ┌──────────────┐ ┌─────────────┐
│ Application │───▶│ Light Client │───▶│ Gateway │
│ (unchanged) │ │ (pay-per-use)│ │ (earns 85%) │
└─────────────┘ └──────────────┘ └─────────────┘
│
▼
┌─────────────────────────┐
│ SolanaVault P2P Network │
├──────────┬──────────────┤
│ NNG │ Kademlia DHT │
│ Transport│ Discovery │
├──────────┴──────────────┤
│ Byzantine Consensus │
│ + Reputation Scoring │
├─────────────────────────┤
│ Compression Pipeline │
│ v1 → v2 → v3 → hybrid │
│ + XGBoost adaptation │
├─────────────────────────┤
│ RocksDB Storage Engine │
│ + Tiered Cache Manager │
└─────────────────────────┘Honest comparisons
How we stack up.
We respect the teams we compete with. Pick the tool that fits — and read the full breakdown before you commit.
SolanaVault vs Helius
→Hosted Solana RPC and DAS API with strong DX, but priced per request and centralized on Helius infrastructure.
SolanaVault vs Triton One
→High-end Solana RPC with custom hardware and Geyser feeds. Excellent performance, still operator-centric and expensive at scale.
SolanaVault vs QuickNode
→Multi-chain RPC provider with a polished console. Pricing is per-request and per-feature, and historical access is gated by plan.
SolanaVault vs Old Faithful
→Filecoin/IPFS-backed Solana historical archive. Strong for cold retrieval, weaker for live RPC and not optimized for sub-second queries.
FAQ
Questions teams ask before they pilot.
Is SolanaVault really decentralized, or is there a coordinator? +
It is genuinely peer-to-peer. Peer discovery uses Kademlia DHT, transport uses NNG sockets, and data integrity is enforced by Byzantine consensus. There is no central scheduler, no privileged registry, and no single party that can revoke access.
Do I have to change my application code? +
No. SolanaVault exposes the standard Solana JSON-RPC interface. Replace https://api.mainnet-beta.solana.com with http://localhost:8899 (or your gateway URL) and existing clients — Anchor, web3.js, solana-py — work unchanged.
What kind of compression ratios are realistic? +
On production Solana blocks we observe 15-25:1 typical ratios, with our v3 pipeline regularly exceeding 20:1. Compression takes under a millisecond per block; decompression takes 13 to 85 microseconds. The README shipping ratios are reproducible via vault-cli compress-demo.
How are gateway operators paid? +
Pay-per-use. Light clients deposit a balance to a gateway and pay per query. Gateways keep 85% of the revenue collected. The remaining 15% is distributed to storage and consensus participants based on contribution and reputation.
Can I self-host the entire stack? +
Yes. The workspace is MIT/Apache-2.0 dual licensed. cargo build --release produces vault-light-client, vault-node, vault-rpc-decentralized, and vault-cli. You can run a private SolanaVault network end-to-end with zero managed dependencies.
How does this compare to running a regular archive node? +
Archive nodes cost thousands per month in storage and IOPS. A SolanaVault light client pays a fraction of that and only for the data it actually fetches. You retain the full RPC API surface and gain microsecond decompression on cached blocks.
What happens if a storage node lies about block contents? +
The Byzantine consensus layer cross-checks responses across multiple replicas. Mismatches reduce the offending node's reputation and trigger slashing. After a threshold the node is evicted from the routing tables and its stake redistributed.
Is there a managed offering? +
Yes — Vault Cloud. Pick a tier, get included queries, custom rate limits, and SOC2-ready logs. Or run a Vault gateway yourself and keep the revenue. Most teams start on Vault Cloud and graduate to self-hosted once usage justifies it.
Stop renting archive nodes.
Vault Cloud gives you a managed gateway in under a minute. Self-host any time — the workspace is MIT/Apache-2.0.