SolanaVault
How it works

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. The result is a peer-to-peer network with no central scheduler, registry, or coordinator.

┌─────────────┐    ┌──────────────┐    ┌─────────────┐
│ 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  │
                                └─────────────────────────┘

The four roles

1

Applications

Your existing Solana code, untouched. Anchor, web3.js, solana-py — they all speak the standard JSON-RPC that the light client exposes locally.

2

Light client

Exposes JSON-RPC on localhost, deposits a balance, pays per query, and caches hot blocks. This is the drop-in replacement for a mainnet-beta endpoint.

3

Gateway nodes

Relay requests for revenue and route through the Kademlia DHT to the closest replicas. Gateways keep the majority of the per-query fee.

4

Storage nodes

Hold compressed blocks, vote in Byzantine consensus, and earn rewards for verified storage proofs, uptime, and honest responses.

The network stack

NNG transport

Binary messaging over NNG sockets for microsecond inter-node latency.

Kademlia DHT

Content-addressed routing to the closest replica, with automatic failover and reputation-aware peer selection.

Byzantine consensus

Every served block carries a cryptographic proof cross-checked across replicas; liars lose reputation and are slashed.

Compression pipeline

Versioned strategies (v1 → v2 → v3 → hybrid → production_v3) plus an XGBoost-tuned variant, adapting per block for 15-25x ratios.

RocksDB storage

Persistence plus a tiered cache manager: hot blocks in RAM, warm in compressed pages, cold from the network.

Economics layer

Staking and reward distribution price bandwidth, storage, uptime, and verified proofs so each role is paid for exactly what it contributes.

Run it yourself.

Clone the workspace, cargo build --release, and bring up your own SolanaVault network end to end.