Docs
Overview
Everything you need to store and read data on the Slab testnet, from the command line or over HTTP.
Slab has three ways in:
- The
slabCLI encrypts, erasure-codes and uploads files and directories, and downloads them again. It talks to nodes directly over QUIC. See the quickstart and the CLI reference. - The HTTP gateway (
slab-gateway) reads Slab data over plain HTTP, so browsers andcurlwork unchanged; Uploads are optional and paid from the gateway’s own wallet. See the gateway API. slab://links and feeds are how you share data: a link is the whole capability (address and key), a feed is a signed pointer you can move to a new version. See links and feeds.
Try it in a browser
This site runs a read-only gateway. Paste a slab:// link at /gateway, or fetch any reference
directly:
curl https://slab.me.uk/slab/<128-hex reference>/
curl https://slab.me.uk/feeds/<owner>/<topic>/
Testnet access
During the early testnet, the source, binaries and the control-plane URL come with an invite (see Run a node). Reading through a gateway needs nothing. Uploading needs vouchers, and on the testnet vouchers are paid with simulated euros.
Words used in these docs
| Term | Meaning |
|---|---|
| slab | a fixed-size piece of an encrypted file: 256 KiB today (1 MiB for large files next) |
| shard | one erasure-coded piece of a slab; any k shards rebuild it |
| root | the content address of a file’s first slab (or of a directory listing) |
| reference | root ‖ file key as 128 hex characters |
| voucher | a blind-signed token that pays for storing one slab; nodes check it offline |
| feed | an owner-signed, versioned pointer to a reference, addressed by owner key + topic |