SlabtestnetRun a node

Phases

Roadmap

Slab is built in phases. The first three are done and running on the testnet. We're in the fourth, durability. The order after that is decided: operators first, agents after, then hardening the parts that still need trust.

  1. Phase 1 · done

    Foundations

    The data plane on its own.

    • Append-only segment store with an index, Merkle accumulator for audits
    • Client-side encryption (ChaCha20-Poly1305) and Reed-Solomon erasure coding
    • QUIC transport, Kademlia routing, hedged reads (first verified shards win)
  2. Phase 2 · done

    Paying for storage without watching it

    A control plane that handles money and never sees content.

    • Blind-signed vouchers (RFC 9474), checked offline by nodes
    • Epoch audits with Merkle proofs, payouts for storage and for delivery receipts
    • Repair under churn, proof of possession, stake and slashing
  3. Phase 3 · done

    Testnet

    Running it for real, and measuring it.

    • Container image and a 20-node testnet on two hosts
    • Directories, inline small files, range reads, feeds, an HTTP gateway
    • Measured on CPU, memory, code size and latency
    • Self-updating nodes from signed releases, with automatic rollback
  4. Phase 4 · now

    Durability

    Making data loss a non-event, at any network size.

    • doneOne shard per node, at most 6 shards of a slab per network (/24 or /48)
    • doneOperators as failure domains: no operator holds more than its share of a slab
    • doneJoining through bootstrap.slab.me.uk, saved peers, reachability checks before a node takes shards
    • donePlacement hardening from the security review
    • doneParallel slab reads and writes, and reads that stop waiting on dead nodes
    • doneRoom kept for repair: uploads stop at 90 % full, repair may use the rest
    • doneUnreliable nodes are avoided: failed pushes and reads make a node suspect
    • in progressRS 32+16 with 1 MiB slabs for large files, 10+6 for small ones: built, rolling out to the testnet
    • in progressRenewing paid storage: a renewal extends a slab's term through the nodes that hold it, opt-in auto-renew with a budget cap, unpaid data deleted only after a grace period; built, not yet on the testnet

Not yet

Real money, a public source release and a production network. The testnet can be reset. Moving real money needs proper payment handling first, and nothing on that path ships without explicit sign-off.