Decentralized Identifier (DID)
A decentralized identifier (DID) is a standardized identifier that refers to a subject and can be resolved to a document containing verification methods and other information associated with that subject.
Zelf Core Team
What Is a DID?
DID stands for decentralized identifier.
A DID can refer to a person, organization, device, or another subject. It provides an identifier that applications can use in verifiable interactions.
A fictional example looks like this:
did:example:123456789
The first part identifies it as a DID. The second names its DID method, and the remaining portion is the method-specific identifier.
The subject is what the DID refers to. The controller is the entity authorized to manage it. These may be the same entity, but they are distinct roles.W3C: Decentralized Identifiers
A DID is not a password, private key, or complete identity profile. Its existence alone does not establish a person’s name, qualifications, or humanity.
How Does a DID Work?
A DID works according to the rules of its method.
1. Create the Identifier
A controller creates or establishes a DID using the chosen method.
Methods differ in their infrastructure and dependencies. Some use blockchains; others use web infrastructure or other mechanisms. A DID therefore does not automatically imply a blockchain-based system.
2. Resolve the DID Document
Compatible software processes the DID to obtain its DID document.
This document can describe verification methods, such as public keys, and the purposes for which they are authorized. It may also provide service endpoints.
A DID document should not contain the private keys used to prove control.
3. Verify an Interaction
An application can use the document’s authorized verification methods to check cryptographic evidence.
For example, a challenge-response protocol may establish control of an authorized key. That does not, by itself, prove which human is using the key.
4. Manage Changes Where Supported
The method determines whether and how the controller can update verification information, rotate keys, or deactivate the DID. Recovery capabilities also vary; they are not guaranteed by the DID format.
Why Do DIDs Matter?
DIDs provide a common identifier structure for systems that need verifiable interactions across organizational boundaries.
Consider a university issuing digital qualifications. Its DID could help receiving software locate verification information associated with the issuer. The qualification itself would remain a separate credential.
For a developer, this separation is useful: an identifier can support multiple interactions without becoming a container for every claim about its subject.
Control and Privacy Need Careful Design
A DID can support greater independence from individual platforms, but actual control depends on the method, software, infrastructure, and key-management arrangements.
Using one identifier across unrelated services may make activity easier to connect. Separate identifiers can reduce some correlation risks, but information disclosed alongside them may still reveal relationships.
Before adopting a DID-based system, practical questions include:
Can keys be changed if compromised?
What happens if the controlling key is lost?
Which infrastructure must remain available?
What information is public or linkable?
How DIDs Complement Verifiable Credentials
The distinction is straightforward:
A DID identifies a subject.
A verifiable credential carries an issuer’s claims about a subject.
Decentralized digital identity describes the broader model in which they may operate.
A DID does not independently prove that its controller is a live human, that only one account belongs to that human, or that a particular action has their approval. Those requirements call for additional checks suited to the application.