PLC is a persistent global identifier system, which allows accounts to retain relationships while changing names or migrating between service providers. It makes use of cryptography and gives individuals (or organizations) direct control and ownership over their identitifier, but does not make use of any blockchain or cryptocurrency technology, and is inexpensive enough to provide as a no-cost service.
did:plc Directory
PLC is a persistent global identifier system, which allows accounts to retain relationships while changing names or migrating between service providers. It makes use of cryptography and gives individuals (or organizations) direct control and ownership over their identitifier, but does not make use of any blockchain or cryptocurrency technology, and is inexpensive enough to provide as a no-cost service.
Creating an Independent Public Ledger of Credentials (PLC) Directory Organization - AT Protocol
As the next step of maturing governance of the PLC identity system, Bluesky Social PBC is supporting the creation of an independent organization to operate the PLC directory.
did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method
Introducing plcbundle - Tree For You
A Transparent and Verifiable Way to Sync the AT Protocol's PLC Directory
did:plc Specification v0.1
DID PLC is a self-authenticating DID which is strongly-consistent, recoverable, and allows for key rotation.
Adversarial PLC directory migration - microcosm
Contingency planning: what's our credible failover for the centralized underpinning of ATProto identities?
Adversarial PLC directory migration - microcosm
Contingency planning: what's our credible failover for the centralized underpinning of ATProto identities?
did-method-plc/website/spec/v0.1/did-plc.md at main · did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method - did-method-plc/did-method-plc
did-method-plc/website/spec/v0.1/did-plc.md at main · did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method - did-method-plc/did-method-plc
gbl08ma.com/didplcbft
A very experimental PLC implementation which uses BFT consensus for decentralization
DNS-Anchored Durable Identity for AI Agents (DNSid)
Autonomous software agents are being deployed across enterprise, cloud, and cross-organizational boundaries. These agents negotiate, transact, delegate, and produce work products that persist beyond their own ephemeral runtime. Current standards and initiatives for agent identity collectively address runtime authentication, authorization, lifecycle management, and tool interaction, but a gap remains: a durable, governance-backed identifier that lets a relying party determine and verify the accountable entity behind an agent it encounters, including agents that have since been retired or whose keys have rotated, and attribute past and present work products to that entity. Lifecycle-history verification is governed by the applicable log method and deployment scope. DNSid addresses the accountable layer of identity: the durable ownership anchor that existing agent identity standards do not provide. This document specifies DNSid, a minimal identity primitive that assigns each agent a Fully Qualified Domain Name (FQDN), binds it to an accountable entity identified by a DNS domain under that entity's control, and publishes a structured set of pointers in DNS TXT records to the agent's cryptographic keys, lifecycle log, and operational status. DNSid uses accountable-entity-controlled signatures for record integrity and an abstract append-only lifecycle log for history. It is designed to sit beneath existing identity, authentication, authorization, and agent interaction standards without competing with them. DNSid introduces no new DNS resource record types, opcodes, or response codes, and requires no changes to DNS resolvers, authoritative servers, or the DNS protocol. It applies to any agent that can be assigned an FQDN whose accountable entity can publish verification material; public discoverability of the agent is not required.
09.06.2026 - release 1 of 3 Sovereign social infrastructure, one layer at a time. We’re now mirroring the did:plc directory - where identities live - on European infrastructure: plc.eurosky.network Decentralisation means not depending on a single directory.
Been thinking about plc.directory as a single-point-of-failure So as a learning exercise, I threw together DIDMARC - an example of an independent witness for the directory 🔍 This approach uses Starknet to be fully trustless, but a trusted mirror could perform similar checks to identify abuse
DIDMARC: DID Mapping Alignment, Reporting & Conformance
didmarc.devLonger version: Eurosky’s plc.eurosky.network is a small but real ATProto infrastructure move. It is not “a European Bluesky clone.” It is a read replica of the did:plc identity directory — the layer many accounts use to resolve keys, handles, and PDS hosts.
did:cow: Another idea to billionaire-proof ATProto IDs, also "art of using a blockchain without using a blockchain". Blockchain-managed wrapper ID, no tx to create, points to a did:plc/did:web but you can move it if something goes wrong. Got carried away and made a resolver and front-end cow.watch
did:cow
cow.watch
Edmund Edgar
Wrote up an idea to improve the DID:PLC system to protect us from the inevitable corporate enshittification phase when the centralized server stops serving mirrors for a bit then starts screwing us over. It's kind of "art of using a blockchain without using a blockchain" github.com/edmundedgar/did-plc-p2p-guard…
I suspect we’ll see a bunch of apps that leverage atproto’s did:plc identity layer but store data out of band.
boltless
