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:dns Method Specification
Many early DID methods were based on distributed ledgers or other decentralized infrastructure, and some of those still remain popular. However, the DID community has also seen a lot of innovation and has come up with new types of DID methods. One of them is did:web, which is based on traditional DNS and web server infrastructure. The DID method presented here is did:dns, which follows a similar idea but offers several improvements over did:web.
did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method
DID Method Rubric v1.0
The communities behind Decentralized Identifiers (DIDs) bring together a diverse group of contributors who have decidedly different notions of exactly what "decentralization" means.
did:plc Specification v0.1
DID PLC is a self-authenticating DID which is strongly-consistent, recoverable, and allows for key rotation.
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.
Creating a did:web atproto account using goat | bryan newbold
This is a hastily-written guide to creating a did:web atproto account. You'll need: familiarity with command line tools a domain name and web server you control, for the did:web a handle domain name you control (can be the same as the did:web domain) an invite code to an atproto PDS the goat t...
Creating a did:web atproto account using goat | bryan newbold
This is a hastily-written guide to creating a did:web atproto account. You'll need: familiarity with command line tools a domain name and web server you control, for the did:web a handle domain name you control (can be the same as the did:web domain) an invite code to an atproto PDS the goat t...
PC do Manual
PC do Manual é uma plataforma de aplicações de código aberto derivada do site Manual do Usuário.
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.
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.
wrote a quick guide to creating a did:web atproto PDS account using goat. this isn't something I recommend for folks in most cases (did:plc is great!), but I think it is important on principle, and we should test and document it better.
Creating a did:web atproto account using goat | bryan newbold
whtwnd.com