How it works
Slab splits storage into two parts that only meet through signed tokens. The nodes move bytes, and a separate control plane handles money.
Two planes
Nodes (the data plane) store shards, route requests over QUIC and answer storage challenges. They have no wallet, no blockchain connection and no balances. An upload is accepted when it carries a valid voucher, which a node checks offline against a public key.
The control plane sells vouchers, holds operator stake, runs audits and computes payouts. It is off the data path, and it never learns what was stored: vouchers are blind-signed (RFC 9474), so the control plane can’t link a voucher it sold to the upload that spent it.
From file to shards
- The uploader’s client encrypts the file (ChaCha20-Poly1305) and cuts it into 256 KiB slabs.
- Each slab is erasure-coded into 10 data and 6 parity shards with Reed-Solomon. Any 10 of the 16 rebuild the slab, so it survives the loss of 6.
- The 16 shards go to 16 different nodes, the ones whose IDs are closest to the slab’s address, with at most 6 on any one host.
- The link to the file is
slab://<root>#<key>. The key sits after the#and never goes over the network.
The storage overhead is 1.6×, compared with 3× for keeping three full copies.
Keeping data alive
- Repair. Every 10 minutes the nodes holding a slab check each other. When fewer than 14 shards are healthy, the node nearest the slab’s address rebuilds the missing ones from any 10 and places them on free nodes.
- Audits. Each epoch, nodes commit to what they hold, then answer 16 random challenges with Merkle proofs. A fake answer is detected and slashed.
- Reads ask the 24 nodes around a slab’s address for any shard, and the first 10 verified answers win. A slow node doesn’t slow the read.
What nobody learns
| Who | Sees | Doesn’t see |
|---|---|---|
| A node | encrypted shards, the voucher that paid for them | content, file names, who paid |
| The control plane | accounts and how many vouchers each bought | what they were spent on |
| The audit service | which slabs are paid for (ciphertext addresses) | who bought them |