✳flâneur — a map of the web's best reading

Personal Data Repositories | AT Protocol

atproto.com · 383 words · saved by 1 readers

A "Data Repository” is a collection of data published by a single user. Repositories are self-authenticating data structures, meaning each update is signed and can be verified by anyone. The content of a repository is laid out in a Merkle Search Tree (MST) which reduces the state to a single root hash. It can be visualized as the following layout: Every node is an IPLD object (dag-cbor) which is referenced by a CID hash. The arrows in the diagram above represent a CID reference. This layout is reflected in the URLs: A “commit” to a data repository is simply a keypair signature over a Root node’s CID. Each mutation to the repository produces a new Root node, and every Root node includes the CID of the previous Commit. This produces a linked list which represents the history of changes in a Repository. Multiple types of identifiers are used within a Personal Data Repository. The AT Protocol will launch soon. Join the waitlist to try the beta before it's publicly available. © 2023 Bluesky

Data Repositories A data repository is a collection of data published by a single user. Repositories are self-authenticating data structures, meaning each update is signed and can be verified by anyone. They are described in more depth in the Repository specification . Data Layout The content of a repository is laid out in a Merkle Search Tree (MST) which reduces the state to a single root hash. It can be visualized as the following layout: ┌────────────────┐ │ Commit │ (Signed Root) └───────┬────────┘ ↓ ┌────────────────┐ │ Tree Nodes │ └───────┬────────┘ ↓ ┌────────────────┐ │ Record │ └────

Explore this link on the map →

related reading