Content-Addressed Storage Without S3

🪩 The Disco Party is MATA's distributed cloud.

Content-addressed storage is fetch-by-hash. You ask the mesh for a CID — the cryptographic identity of the bytes — and any peer that holds those bytes can answer. You do not ask a vendor URL. You do not hope the bucket still exists, the key still works, and the region is not having a day. Content-addressed files stay findable as long as k-of-n shards survive on homes. S3 is a pointer into someone else's building. A CID is a pointer into the object itself.

That swap is how a distributed cloud stores objects without becoming a worse AWS. What Is A Distributed Cloud is the architecture. SpaceDB is the database that already thinks in sealed entries. This article is the object layer: content-addressed storage, durability, erasure.

Why Content-Addressed Storage Beats A Vendor URL

A URL is a promise about a host. Hosts change names, change owners, change prices, and go dark. Content-addressed storage is a promise about bytes. If the hash matches, you have the file. If it does not, you do not. There is no "the object is still at this path but the contents drifted." Content-addressed files cannot silently rot under the same key. That is Integrity as an engineering property, not a slogan — and it sits under Security, the Digital Freedom primitive that maps to encryption and authenticity.

S3 adds a second promise: pay us or the URL dies. The egress bill is how that promise is enforced. Content-addressed storage on a disco mesh enforces nothing of the kind. Peers serve a CID because Settlement pays them, or because they are your other laptop. The Electronic Frontier Foundation treats durable publishing as a speech problem. A CID you can refetch from friends is publishing that outlives a bucket policy. The Disco Party is the set of friends with disks.

Trust is who may request the CID — a capability, not an IAM user in a vendor account. Incentive is who gets paid for serving it. The three primitives stay three.

How Content-Addressed Storage Works Without S3

SpaceDB's library is open. The network is disco. Transport is iroh. ShardStore is erasure. KeyDirectory is mID. Settlement is $MATA / Iron Bank. Content-addressed storage is what those seams look like when the payload is a file. Peer-to-peer device sync moves the pieces. You never "list the bucket." You present a grant and a CID.

A CID Names Content-Addressed Files, Not A Folder

The CID is the hash of the sealed object — or of the merkle root that stands for it. Content-addressed files that share a prefix do not share a blast radius. Rename is a new link, not a mutate-in-place. The IETF HTTP semantics already distinguish representation from resource. A CID is the representation's name. That is why content-addressed storage composes: two apps can talk about the same bytes without sharing a vendor account.

Erasure Coding Keeps Content-Addressed Storage Online

spacedb-durability cuts ciphertext. rusty_erasure is GF(2^8) Reed-Solomon, SIMD to GFNI, wasm-ready, no C, no GPL. k-of-n shards land on homes that cannot read them. Content-addressed storage that held one full replica on one NAS would be a USB drive with extra marketing. Erasure is how a CID survives a dead home. The NIST Zero Trust Architecture assumes the disk is hostile. Shards honor that.

Fetch The CID, Verify, Then Trust The Bytes

Download is not the end. Hash again. If the CID matches, content-addressed storage did its job. If it does not, the peer is wrong or hostile and you drop the transfer. The NIST Secure Software Development Framework wants verify-then-use. A vendor URL trains people to skip the verify. A CID makes the skip obvious.

Content-Addressed Storage Is How The Disco Holds A Library

Photos, game chunks, model weights, backups — anything you would have parked in a bucket. Digital Freedom is Trust, Security, and Incentive on those objects. The Freedom Guide is the human path. What Is Digital Freedom is the why. Remade With Rust is the stack.

Content-Addressed Storage Does Not Need An Account To Exist

S3 needs an account, a region, and a billing alert. A CID needs a peer. Sign in with Sovereign ID is how a person authorizes a fetch. It is not how the object exists. Content-addressed files can sit on a friend's shard set while you are offline. The Privacy Rights Clearinghouse is a list of accounts that became the only copy. Content-addressed storage refuses to be that copy.

Dedup Is A Side Effect, Not The Pitch

Identical content-addressed files collapse to one CID. That saves disk. Fine. The pitch is still independence from a vendor URL. Do not sell a distributed cloud as a compression trick. Sell it as a name that cannot be repossessed. The Federal Trade Commission has seen every "we made storage cheaper" pitch that came with a new lock-in.

Remade Primitives, Disco Party, Digital Freedom

SpaceDB, spacedb-durability, rusty_erasure, and mID are Remade-With-Rust primitives. They become a disco party when content-addressed storage replaces the bucket. They become Digital Freedom when Trust, Security, and Incentive — identity, encryption, payouts — attach to a CID instead of an S3 key. Start at the Disco Party and the Learn index. Fetch by hash. Stop bookmarking a vendor.

Rebuilding a file when homes die is erasure coding. Why that fetch has no egress line-item is no egress bill. The database that stores the CID is SpaceDB.