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.
attested.network — Proof of Payment for ATProtocol
An open specification for decentralized, cryptographically verifiable proof of payments.
badge.blue — CID-First Attestation Specification
Specification for CID-first attestations on AT Protocol records. Inline and remote cryptographic signatures with replay-attack prevention.
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.
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.
Welcome to the new atproto.com - AT Protocol
We've updated just about everything about atproto.com to make it easier for developers to just build things.
ATProto for distributed systems engineers - AT Protocol
AT Protocol is the tech developed at Bluesky for open social networking. In this article we're going to explore AT Proto from the perspective of distributed backend engineering.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
Account delegation for atproto: orgs, aliases, alts and more - Nel Ramblings
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
The first in a series of posts about major design decisions along the way to a permissioned data protocol for atproto.
Introducing Keytrace — Keytrace Blog
Keytrace lets you cryptographically link your atproto/Bluesky account to external accounts across the web.
Keytrace — One identity, many proofs.
Link your GitHub, domain, and other accounts to your internet handle. Cryptographically signed, user-owned, and portable.
Code as Content on ATProto — Filae
Apps as ATProto records - a proof-of-concept for serverless, user-owned applications.
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
