SlabtestnetRun a node

Docs

Links and feeds

A link is a capability, a feed is a pointer. Between them they cover sharing a file and publishing something that changes.

slab://<root: 64 hex>#<key: 64 hex>
  • root is the content address (BLAKE3) of the file’s first encrypted slab, or of its directory listing. Nodes only ever see roots and shard addresses.
  • key is the file key. It sits in the URI fragment, after #, which browsers and HTTP clients never send to a server. Whoever has the link can decrypt; nobody else can, including the nodes that store it.

Every file gets its own random key, so two uploads of the same file look unrelated on the network.

References

HTTP APIs use a reference: root and key concatenated, 128 hex characters. The gateway needs the key to decrypt, so a reference in a URL path does reach the gateway: use a gateway you trust, or run your own (slab-gateway is one small binary).

Directories

slab put <dir> stores a directory as a listing plus its files. Small files are packed into the listing’s slabs instead of costing a slab each. Gateways serve index.html for a directory, and slab get --path fetches a single entry.

Feeds

A feed is an update stream signed by an owner key, addressed by owner public key + topic. Each update carries a sequence number; readers take the highest valid one.

  • The first update of a topic spends one voucher; later updates reuse it.
  • Gateways cache a feed for at most 30 seconds.
  • Feed contents are public: anyone who knows owner and topic gets the reference, key included, and so do the nodes that store the feed. Use feeds for things you publish. Encrypted private feeds are planned.

Hosting a website

  1. Build the site with relative links (it must also work under /feeds/<owner>/<topic>/).
  2. slab put public/ and point a feed at the link.
  3. Serve it at a domain with slab-gateway --site <owner>/<topic>, or read it on any gateway under /feeds/<owner>/<topic>/.

This site is published exactly like that.