







This document defines a “peer” DID Method that conforms to the DID Spec. The method can be used independent of any central source of truth, and is intended to be cheap, fast, scalable, and secure. It is suitable for most private relationships between people, organizations, and things. We expect that peer-to-peer relationships in every blockchain ecosystem can benefit by offloading pairwise and n-wise relationships to peer DIDs.
did:web Method Specification
DIDs that target a distributed ledger face significant practical challenges in bootstrapping enough meaningful trusted data around identities to incentivize mass adoption. We propose a new DID method using a web domain's existing reputation.
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.
Decentralized Identifiers (DIDs) v1.1
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.
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.
Holochain: Reinventing Applications
Holochain is a framework for writing fully distributed peer-to-peer applications. It is not based on blockchain technology. Nor is…

DID Method Rubric v2.0
The decentralized nature of DIDs has inspired a wide range of DID methods, as different innovators document novel approaches for using DIDs with different Verifiable Data Registries. At last count, there were 226 methods listed in the W3C extensions registry and countless others in use. This means that implementers are faced with the challenge of choosing which methods to support. This is true not only for components like DID Resolvers, which necessarily process method-specific features, but also for issuers and verifiers, who must decide independently with method meets their business needs for features like revocation, provenance, and cost.
FOSDEM 2026 - Willow - Protocols for an uncertain future
Centralised systems were designed with the best of intentions, but were turned against us anyway. And peer-to-peer systems will be exactly the same.

EigenTrust
The EigenTrust algorithm is a reputation management algorithm for peer-to-peer networks, developed by Sep Kamvar, Mario Schlosser, and Hector Garcia-Molina.[1] The algorithm provides each peer in the network a unique global trust value based on the peer's history of uploads and thus aims to reduce the number of inauthentic files in a P2P network. It has been cited by approximately 5800 other articles according to Google Scholar.[2]
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.
Decentralized Identifiers - PLANET Research - The Open Co-op
Decentralized Identifiers (DIDs) offer self-sovereign identity, reducing reliance on central authorities, enhancing security and user control.

did-method-plc/did-method-plc
Public Ledger of Credentials: a cryptographic, strongly-consistent, and recoverable DID method
FEP-1042: Peer to Peer Fediverse Identities
Hey folks, we at [Distributed Press](https://distributed.press) have been working on making a bridge between peer to peer or "dweb" protocols and ActivityPub implementations over the past year and wanted to solidify our approach so that others can interoperate. Here's is an initial draft expla...
The State Of The DAOs | HackerNoon
Decentralised Autonomous Organisations (DAOs) are one of the most anticipated applications of blockchain technology. After all, this is the first time in history we homo sapiens had the means to coordinate in a trustless and anonymous way to make collective decisions for a certain cause.

Willow - Willow’25
Peer-to-peer protocols which scale up, down, and sideways. Sychronisable data storage, fine-grained access control, private and efficient synchronisation, and secure data delivery by any means possible.
Bab - Verifiable partial data for peer-to-peer systems.
A family of hashing functions inspired by Blake3 ad Bao, with some judicious tweaks.
High Assurance DIDs with DNS
This document outlines a method for improving the authenticity, discoverability, and portability of Decentralized Identifiers (DIDs) by utilizing the current DNS infrastructure and its technologies. This method offers a straightforward procedure for a verifier to cryptographically cross-validate a DID using data stored in the DNS, separate from the DID document.