







The on-PDS content model and the wire formats of a Szzt (a.k.a. "Mini-Site" / @minisite) mini-site: the three atproto records that describe a site, the StrongRef links between them, the CID codecs, the byte encodings, and how a served request path resolves to a specific block of bytes. A compatible publisher writes these records; a compatible verifier re-derives every CID from signed state and trusts no source's assertion.
CIDs: What You Need to Know and Why, Part 2 - Nick's Blog
How ATProtocol uses Content Identifiers to create a versioned, verifiable, and portable data model.
rfcs/atproto/001-private-content.md at main · knasher/rfcs
Technical RFCs and design proposals for protocols and systems - knasher/rfcs
About Atproto w/ Dan Abramov | Wireframe Live
About Atproto w/ Dan Abramov | Wireframe Live
com.atproto.repo.listRecords | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*

socialde.pt/atproto.md
Markdown-first API for the AT Protocol ecosystem, built for LLM agents and tools that consume plain text.
CIDs: What You Need to Know and Why, Part 1 - Nick's Blog
A deep dive into Content Identifiers, the self-describing cryptographic fingerprints that form the foundation of ATProtocol’s data model.
com.atproto.repo.createRecord | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*

ATProtocol Attestations: Cryptographic Signatures for the Decentralized Web - Nick's Blog
This post introduces the formal ATProtocol attestation specification, a framework for adding cryptographic signatures to ATProto records through two complementary patterns: inline attestations that embed signatures directly in records, and remote attestations that store proof in separate repository records. The specification prevents replay attacks through repository binding, uses CID-based content addressing for integrity, and provides the cryptographic foundation for verified credentials, trusted content, and authenticated interactions in the decentralized ATProtocol ecosystem.
ATProto Architecture
Visual summary of the AT Protocol architecture: PDS, AppView, identity, records, lexicons.

atproto-crates — AT Protocol building blocks for Rust
A Rust workspace of eighteen crates for AT Protocol: content addressing, DID and handle resolution, repositories and Merkle Search Trees, OAuth with DPoP, XRPC services, and event streaming.
#protocolsforpublishers #atproto #mcp #webapplets | Chad Kohalyk
Web publishing is facing its next challenge: a new iteration of centralizing platforms. BUT there is also a new wave of open protocols and standards that can help us gain our independence. Next month in NYC we are gathering a group of frontier technologists and popular web publishers to discuss how we can sail into this next platform shift as captains. #ProtocolsForPublishers Learn more and sign up here: https://pfp.unternet.co We will be hosting talks on #atproto #mcp #webapplets and web payments, and give publishers the opportunity to interact directly with developers working on these frontier technologies. Thank you to Unternet, Graze Social, Free our Feeds, and betaworks for their support.

/beaver/patches/components/net/protocols/atproto at main · me.webbeef.org/beaver
Rewild Your Web
I recently got super into the ATProto spec and how different services use PDS to store the data, I put together a quick client-only website that presents all those records in a single, consolidated feed of all my activity: at.diego.codes
at.diego.codes — Diego Vicente
at.diego.codesCompose | Taproot
Compose | Taproot

ATScience Ecosystem Map

Bluesky Protocol Services

Explore

AnyPub