Technical definition
Decentralized Identity (DID) is a cryptographic identity model defined by the W3C that enables self-sovereign identity (SSI) through globally unique, resolvable identifiers stored on distributed ledgers or peer-to-peer networks. DIDs are typically paired with cryptographic key pairs (public/private) and verifiable credentials (VCs) issued by trusted entities. The identity owner controls access via digital signatures, enabling selective disclosure of identity attributes without exposing unnecessary personal data. DIDs leverage cryptographic proofs and zero-knowledge proofs (ZKPs) to verify claims without revealing underlying data, reducing reliance on centralized identity providers.
An analogy
Imagine your identity as a set of physical keys and certificates. Instead of keeping them in a single lockbox controlled by a bank (like a traditional ID system), you carry them yourself in a secure digital wallet. You can show specific keys to unlock only the doors or services you need (e.g., proving you’re over 21 without showing your full birth certificate), and you decide who gets access to which keys.
Why it matters
DIDs aim to address privacy concerns and single points of failure in traditional identity systems by giving individuals control over their digital identity, reducing reliance on corporations or governments that may misuse or leak personal data.
Where it came from
The concept emerged alongside blockchain technology in the early 2010s, with early proposals like Microsoft’s 2016 whitepaper on decentralized identity. The W3C formalized the DID standard in 2019, building on prior work in self-sovereign identity and cryptographic identity systems.
Example in practice
A university issues a verifiable credential (VC) to a student’s DID, proving their degree without storing personal data on a centralized database. The student can then use this VC to apply for jobs, where employers verify the credential directly from the student’s DID without contacting the university, preserving privacy.
Common misconceptions
- DIDs eliminate the need for any trusted entities → correction: DIDs reduce reliance on centralized authorities but still require trusted issuers for verifiable credentials (e.g., universities, governments).
- DIDs make identities completely anonymous → correction: DIDs enable selective disclosure but can still be linked to real-world identities if required (e.g., for KYC compliance).
Risks & limitations
- Irrecoverable loss: If a user loses their private key or recovery phrase, their DID and associated credentials become permanently inaccessible.
- Privacy trade-offs: While DIDs reduce centralized data collection, they can still enable correlation attacks if identifiers are reused across services.
- Regulatory uncertainty: Compliance with anti-money laundering (AML) and know-your-customer (KYC) laws may conflict with the privacy-preserving nature of DIDs.
- Adoption barriers: Requires widespread support from institutions, wallets, and service providers, which is still limited.
- Sybil attacks: Malicious actors could create multiple DIDs to exploit systems that rely on identity uniqueness.