Decentralized Identity (DID)
Abbreviation: DID
Pronunciation: dih-SEHN-truh-leyezd eye-DEHN-tuh-tee (DEE-EYE-DEE)
Also known as: Decentralized Identity, DID
Definition
Decentralized identity uses user-controlled identifiers and verifiable credentials to establish digital relationships without depending on one central identity provider. DIDs often work with verifiable credentials issued by trusted organizations. The identifier does not itself prove a person's legal identity, reputation, or attributes; those claims depend on credential issuers, schemas, status, and verifier policy.
Overview
Meaning and scope
Decentralized identity uses user-controlled identifiers and verifiable credentials to establish digital relationships without depending on one central identity provider. DIDs often work with verifiable credentials issued by trusted organizations. The identifier does not itself prove a person’s legal identity, reputation, or attributes; those claims depend on credential issuers, schemas, status, and verifier policy.
Mechanism and operation
Resolving a DID can produce a DID document containing verification methods and service information. Implementers should choose a DID method, validate resolution results, keys, proofs, controller changes, credential status, and privacy implications. Wallets need secure key recovery and selective disclosure where supported. Verifiers must assess issuer authority and avoid placing unnecessary personal data on immutable public ledgers. Applications relying on Decentralized Identity (DID) should validate the exact credential issuer, subject binding, status, expiry, proof format, and intended audience. In Decentralized Identity (DID) implementations, high-value access or payment decisions should not rely on an unverified profile claim or wallet address alone.
Practical payment example
A merchant verifies a credential presented through a decentralized identifier. It still checks the credential issuer, revocation status and subject binding before treating the credential as trustworthy.
Operational checks
Decentralized Identity (DID) should distinguish the identifier, controller, resolution method, credentials, and proof of control. In Decentralized Identity (DID) implementations, possession of an identifier does not by itself establish a person’s legal identity, current authority, or entitlement to a service. Implementations of Decentralized Identity (DID) need method or network identifiers, canonical encoding, key-rotation and recovery rules, revocation behavior, and clear handling when resolution data is unavailable or changes over time.
Distinctions and limits
Decentralized identity commonly uses W3C Decentralized Identifiers, which are globally unique identifiers controlled through cryptographic methods rather than assigned by one central registry.
Related reading
Related definitions: network.
Example
A merchant verifies a credential presented through a decentralized identifier. It still checks the credential issuer, revocation status and subject binding before treating the credential as trustworthy.
Comparison
Decentralized identity commonly uses W3C Decentralized Identifiers, which are globally unique identifiers controlled through cryptographic methods rather than assigned by one central registry. The identifier does not itself prove a person's legal identity, reputation, or attributes; those claims depend on credential issuers, schemas, status, and verifier policy.
Key Takeaway
DIDs provide cryptographic identifier control, while meaningful identity claims still depend on trusted credentials, privacy, and verification policy.
Sources
- W3C Documentation: Did Core — W3C (2026-07-30)
- W3C Documentation: Vc Data Model 2.0 — W3C (2026-07-30)
- NIST Documentation: Cryptographic Standards And Guidelines — NIST (2026-07-30)
- IETF RFC 3986 — IETF (2026-07-30)