SlabtestnetRun a node

At a glance

Slab at a glance

Slab keeps money out of the data path. That changes what a node costs, what it can see and who can link a payment to your files.

In one table

Slab
Tokennone
Blockchainnone
You pay ineuros, per slab (simulated on the testnet)
Encrypted before uploadalways, on your machine
Can payments be linked to content?no: blind-signed vouchers
Redundancyerasure coding: 1.5× for large files (RS 32+16), 1.6× for small ones (RS 10+6)
Node memory at idle23–30 MiB (measured)
Node CPU at idle1–8 millicores (measured)
Who runs itindependent operators
Maturitytestnet proof of concept

Measured on our 20-node testnet, November 2026.

What only Slab does (as far as we know)

  • Blind-signed payment. Storage is paid with vouchers that the seller signs without seeing them (RFC 9474). Nothing cryptographically links an account to the slabs its vouchers paid for, not even for us. Timing still can, so buy vouchers in batches ahead of time.
  • A storage node with no money in it. No wallet keys, RPC endpoints or balances on the node: our build checks forbid them. That is why it fits in about 25 MiB.
  • Paid for delivery. Downloads produce signed delivery receipts, and nodes are paid from them. Receipts can be faked, so credit is capped per shard: self-dealing earns at most the cap.
  • Earnings as storage (planned). An operator can take storage instead of cash, so contributing disk pays for your own backups.

Where Slab is today

  • Price: not set yet. On the testnet the price is a setting in the control plane, paid in simulated euros. What carries over is cost: a node stores 1.5 to 1.6 bytes per byte uploaded and pays no gas. The real price will come from the market (roadmap phase 7).
  • CPU with data. A node holding data idles at about 0.075 cores, because repair checks grow with stored data.
  • Scale. The testnet runs 20 nodes on two hosts in one data centre, so read speeds don’t prove anything about a worldwide network yet.