5. A repository is a signed set of records
All of an account's public data is one repository: records in collections, a Merkle search tree reducing it to one root, every version signed with the DID's key, so anyone can verify and anyone can serve it.

5. A repository is a signed set of records

All of an account's public data is one repository: records in collections, a Merkle search tree reducing it to one root, every version signed with the DID's key, so anyone can verify and anyone can serve it.

Self-authenticating data is what makes hosts interchangeable.

All your public records live in one repository. A ledger box of records: posts, likes, follows, whatever an app defines.

Records are sorted into collections, one per record type. Each record has a key inside its collection.

Above the records sits a hash tree. One root hash stands for everything.

Every version of the repository is a commit: a seal on the root. Signed with the key in your DID document.

So anyone can check it, and anyone can serve it. The repository proves itself. The server holding it does not matter.

Terms. MST: Merkle search tree, the hash tree over the records. CAR: content-addressed archive, the file format a whole repository exports as.

Check yourself. What does the seal on a commit cover?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Connections0

Connections show where other documents or comments link to this document.

Related documents

Loading connections…