CIDs: What You Need to Know and Why, Part 1 - Nick's Blog

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.

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.

ATProtoFans - Support Your Favorite Creators

Decentralized supporter attestation service for the ATProtocol ecosystem. Support creators with cryptographically verifiable relationships.

ATProtoFans - Support Your Favorite Creators

Decentralized supporter attestation service for the ATProtocol ecosystem. Support creators with cryptographically verifiable relationships.

reliqlabs/zkat

Zero Knowledge Proofs of/for the ATProtocol

Content Identifiers (CIDs) | IPFS Docs

Learn about how content addressing works and how content identifiers, or CIDs, play a crucial role in IPFS.

Understanding ATProtoFans: A Technical Deep Dive into Verifiable Creator Support - ATProtoFans Blog

/atproto-identity-rs/crates at main · smokesignal.events/atproto-identity-rs

A library for ATProtocol identities.

Protocol Reference

A reference of all major components and implementations of ATProto

graham.systems/cistern

Encrypted, ephemeral, private memos on atproto

Introduction - idiolect

Mutual intelligibility for schema idiolects on ATProto.

Building Unforgeable Professional Endorsements with ATProtocol - Nick's Blog

Traditional professional endorsements on platforms like LinkedIn lack cryptographic proof—anyone could forge them, and the platform controls the truth. This article introduces a two-record architecture using ATProtocol's Content Identifiers (CIDs) and Decentralized Identifiers (DIDs) to create mathematically unforgeable mutual attestations. By separating proof creation from endorsement acceptance and leveraging the firehose for distributed validation, we build a system where both parties cryptographically consent and no central authority can manipulate the record.

This is a spec for ATProto accounts to request and advertise (compute) resources.