ATproto

Federated Protocols

Open, decentralized protocol (Authenticated Transfer Protocol) for social applications with self-authenticating data and identity, account portability via DIDs, content addressing via CIDs, and global relay architecture. Designed for 'big world' use cases scaling to billions of accounts. Separates 'speech' layer (permissive data distribution) from 'reach' layer (flexible content curation and moderation)

Federado Empresa Risco de captura médio
Links
Visitar Comunidade

Detalhes

Licença Apache 2.0 / MIT
Status de Dev Released
Proprietário Bluesky Social PBC (CEO: Jay Graber, CTO: Paul Frazee); originally funded by Jack Dorsey/Twitter; IETF working group charter published January 2026 for standardization
País USA
Ano de Início 2019
Stack TypeScript, Go, Lexicon
Financiamento VC, Grant
Última Investigação 15 de jan. de 2026

Domínios de Caso de Uso

Communication Identity & Trust

Affordances

Protocol federation Sovereign identity Data portability

Federated Protocol Atributos

Content Addressing Yes (CIDs for blobs and repo commits; content-addressed via IPLD/CID format; self-authenticating data verifiable from any copy)
E2EE Not yet implemented (planned as 'entire second phase of protocol development'; encompasses private accounts, direct messages, encrypted data; MLS being explored; recommended against 'bolting on' encryption with existing primitives)
Signature DID-based signatures (K-256/secp256k1 elliptic curve for repository signing; all repo commits cryptographically signed; self-authenticating — data integrity verifiable from any copy without trusting source server)
Federation Model Shared-heap via Relay: PDS (Personal Data Servers) host user repositories; Relay/BGS (Big Graph Service) aggregates global firehose of all repo events; AppViews index and serve application-specific APIs; modular microservice architecture separating data hosting, aggregation, and application logic
Instance / Server Requirements PDS: Low (~1GB RAM, modest hardware); Relay/BGS: High (resource-intensive global indexing of entire network); AppView: Moderate to high (application-dependent)
Account Portability Full portability (DID-based identity; can migrate between PDS providers; designed for account migration even with non-cooperative PDS; social graph survives migration because DIDs are server-independent; some migration details still being finalized)
Discovery / Relay Architecture Global Relay (BGS firehose — aggregates all PDS events via WebSocket streams) + AppViews for application-specific indexing/search + Labelers for content classification; DNS-like lexicon resolution for schema discovery
Server Authority Model Minimal server authority (PDS stores user data but doesn't control identity; Relay is unopinionated indexer; AppView filters and curates; user can move PDS without losing identity or social graph; Labelers provide moderation without controlling speech)
Protocol Maturity / Standardization Proprietary open standard transitioning to IETF: Internet Drafts for repository format and data sync submitted September 2025; IETF working group charter published January 2026; additional specs (schemas, identity, OAuth, private data) under development by Bluesky PBC
Data Sovereignty User-controlled via PDS (Personal Data Server); self-authenticating data (signed Merkle trees verifiable independent of hosting server); users own their repositories and can verify data integrity without trusting PDS