A DID:PLC read replica for the AT Protocol. Resolve DID documents without hitting the main plc.directory server.
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.
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
did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method
QuickDID - AT Protocol Identity Resolution Service
High-performance handle-to-DID resolution service for the AT Protocol ecosystem. Resolve Bluesky and AT Protocol handles instantly.
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.
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.
hello! yeah! quite a lot of PLC progress (and some left to go). (warning: long thread) 1. there is an official reference read-replica implementation: github.com/did-method-plc/go-didplc/tree… the official read-replica is better than the Allegedly reference-server-wrapper that i made, in two important ways:
bogosbinted69420.bsky.social
hello, has there been progress on this since the writeup? thank you for your work, i'm not grasping the full extent of it but i'm really interested in decentralization of the atmosphere
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
