DID PLC is a self-authenticating DID which is strongly-consistent, recoverable, and allows for key rotation.
did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method
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
plc-passkey · Passkeys as PLC Rotation Keys
Derive deterministic secp256k1 rotation keys from passkeys via WebAuthn PRF and add them to AT Protocol did:plc documents.
How to edit `did:plc` rotation keys · bluesky-social atproto · Discussion #3366
I have migrated my Bluesky handle rekmarks.com to my own PDS. I am trying to replace one of its rotation keys. Here's what I observe: I check the rotation keys returned by com.atproto.identity....
Decentralized Identifiers (DIDs) v1.0
Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID refers to any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) as determined by the controller of the DID. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject.
didplc.directory | DID:PLC Read Replica
A DID:PLC read replica for the AT Protocol. Resolve DID documents without hitting the main plc.directory server.
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.
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.
Introducing plcbundle - Tree For You
A Transparent and Verifiable Way to Sync the AT Protocol's PLC Directory
DIDComm
DIDComm lets people and software use DIDs to communicate securely and privately over many channels: the web, email, mobile push notifications, QR codes, Bluetooth, message queues, sneakernet, and more.
built an atproto terminal ui for setting up alternative plc rotation keys. there are two types of keys. hardware-based: no sync software-based: synced via icloud is anyone interested in this? I could package it up and release it, though it needs a lot of UX work. tangled.org/saewitz.com/plc-touch/
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.dev
