Decentralized identity is a way to prove who you are online without a central company holding your identity files. Each person or organization holds their own identifier, called a Decentralized Identifier (DID), and their own credentials, such as a passed
reusable KYC check or a professional license, in a digital identity wallet. When a service needs to check something, the holder shares a cryptographic proof of that one fact instead of a copy of their documents. The DID shows who controls the identity; the credential shows what can be proven about it.
What Is Decentralized Identity?
Decentralized identity is an identity model where the holder, not a platform, keeps the identifiers and credentials and shares only the proof a service asks for. It has three parts:
- Decentralized Identifiers (DIDs): identifiers the holder creates and controls with cryptographic keys, without an account at a central provider.
- Verifiable Credentials: signed claims from an issuer, such as a bank or a university, that anyone can check with the issuer's public key, usually published in its DID Document.
- A digital identity wallet with selective disclosure: the holder keeps the credentials and shares one fact, such as "over 18", instead of the whole document.
Together they let a service check identity without a central database of identity files.
What Is a Decentralized Identifier (DID)?
A DID (Decentralized Identifier) is a unique digital identifier that enables a person, organization, or system to prove control over an identity without relying on a centralized authority. Unlike traditional identifiers such as usernames or email addresses, a DID is created and controlled by its owner and can be verified cryptographically.
This identifier resolves to a DID Document, which contains the cryptographic material needed to authenticate the DID, such as public keys and service endpoints. Importantly, the DID itself does not contain personal data. Instead, it points to verifiable information that allows others to confirm ownership and establish trust.
Because a DID is independent of any single platform, registry, or provider, it forms the foundation of decentralized identity systems where users maintain full control over how their identity is used and verified across different applications and ecosystems.
How does a Decentralized Identifier (DID) Work?
A DID follows four steps: creation → registration → resolution → verification. Together, these steps allow an identity to be verified securely without exposing personal data or depending on a central authority.
First, a user creates a Decentralized Identifier (DID) by generating cryptographic keys. These keys give the user control over the DID, similar to how a private key controls a crypto wallet. The DID is then registered using a DID method (the rules for how one type of DID is created and resolved, such as did:web or did:ethr), which may reference a blockchain or another registry. Importantly, no personal information is stored during this process.
When a DID is later used, applications resolve it to retrieve verification information and confirm ownership using cryptography. This enables decentralized identity verification, where a verifier checks a cryptographic signature instead of asking a central identity provider.
What is a DID Document and what information does it contain?
A DID Document is a machine-readable document that describes how a Decentralized Identifier (DID) can be authenticated and interacted with.
A DID Document typically contains:
- Public keys for authentication, allowing others to verify that the DID is controlled by its rightful owner
- Verification methods, including support for key rotation to maintain long-term security
- Optional service endpoints, which can point to messaging services, credential issuers, or other identity-related services
- No personal or sensitive data, ensuring privacy by design
Because a DID Document only includes cryptographic material and metadata, it supports Self-Sovereign Identity (SSI) principles. Users remain in full control of their identity, often through a digital identity wallet, while relying parties can perform decentralized identity verification without accessing private information.
Are Decentralized Identifiers Stored on the Blockchain?
A common question is whether DIDs store identity data on the blockchain. They do not. When a DID method uses a blockchain, the chain acts as a registry for the DID, not a data store. Some methods, such as did:web and did:key, use no blockchain at all.
Only the minimal information required to resolve a Decentralized Identifier (DID) is anchored on-chain. Identity data, credentials, and personal information remain off-chain and wallet-controlled by the user. This design ensures privacy while still benefiting from blockchain properties such as immutability and global verifiability.
By separating identity data from the ledger, DIDs enable privacy-preserving digital identity with DID architectures. This model supports secure authentication, integration with Verifiable Credentials (VCs), and enterprise-grade trust, without turning blockchains into centralized identity databases.
How Do Decentralized Identifiers Work with Verifiable Credentials (VCs)?
Decentralized Identifiers (DIDs) act as the identity anchor in decentralized identity systems, while Verifiable Credentials (VCs) carry the actual claims about that identity, such as government IDs, diplomas, licenses, or employment records.
Verifiable Credentials allow individuals to prove qualifications, age, KYC status, or professional licenses using cryptographic signatures, and with selective-disclosure formats, without handing over the full credential or relying on a centralized identity system.
In simple terms, a DID answers “who controls this identity?”, while Verifiable Credentials answer “what can be proven about this identity?”. Together, they enable privacy-preserving identity verification without relying on centralized databases or repeated data disclosure.
What is the Issuer-Holder-Verifier Model in Decentralized Identity?
Decentralized identity systems follow the three roles defined in the W3C Verifiable Credentials Data Model: issuer, holder and verifier.
Issuer
The issuer is an entity that creates and signs a Verifiable Credential using its DID.
Examples include governments issuing digital IDs, universities issuing diplomas, or companies issuing employment credentials.
- Signs credentials cryptographically with its DID
- Does not control how credentials are later used
Holder
The holder is the individual or organization that receives and stores the credentials in a digital identity wallet.
- Fully controls their credentials
- Chooses when and how to present them
- Can selectively disclose only required information
Verifier
The verifier is the party that needs to check a claim, for example, an employer, service provider, or regulator.
- Verifies authenticity using the issuer’s DID
- Does not need to contact the issuer
- Receives cryptographic proof, not raw personal data
Why This Model Matters
This DID-VC architecture removes several limitations of traditional identity systems:
- No central database: Identity data is not stored in a single platform
- Privacy by design: Users share proofs, not full documents
- Offline verification: Credentials can be verified without real-time issuer access
- Cross-platform trust: Verification works across ecosystems and jurisdictions
For example, a user can prove they are over 18, licensed, or qualified without revealing their name, address, or document number.
How Is Decentralized Identity Different from Centralized Identity?
Traditional digital identity systems are built around centralized logins, accounts issued, stored, and controlled by platforms or institutions. In contrast, decentralized identity shifts control to users by relying on Decentralized Identifiers (DIDs) and cryptographic verification rather than centralized databases.
At a high level, the difference comes down to who owns the identity, how trust is established, and how much data must be exposed to prove something about a user.
| Dimension | Centralized Identity (Web2) | Decentralized Identity (DID) |
|---|
| Ownership | Platform owns and controls the account | User controls the DID and keys |
| Revocation Risk | Absolute: access can be revoked unilaterally | Minimal: user retains control via cryptographic keys |
| Privacy | Full data sharing is common | Selective disclosure supported |
| Trust Model | Institutional trust in the provider | Cryptographic proof and verification |
What is Self-Sovereign Identity (SSI) and How Do DIDs Enable It?
Self-Sovereign Identity (SSI) is a digital identity model where individuals and organizations
fully own and control their identities, instead of relying on centralized platforms such as governments, social networks, or service providers.
In an SSI system, users decide when, how, and with whom their identity information is shared. Decentralized Identifiers (DIDs) provide the technical foundation that makes this possible by enabling identity ownership and verification without a central authority.
In simple terms:
- SSI defines the principle: user-owned digital identity
- DIDs implement the mechanism: cryptographic control and verification
Without DIDs, SSI would remain a concept rather than a practical, interoperable system.
Why Are DIDs Considered a Core Pillar of Self-Sovereign Identity?
DIDs are fundamental to SSI because they remove the structural dependencies that exist in traditional identity systems.
User-Generated Identifiers
DIDs can be created directly by users, organizations, or systems, without registering with a central authority. This ensures identity creation is permissionless and independent of any platform.
No Permission Required to Create or Use
Unlike usernames or accounts issued by service providers, DIDs do not require approval, registration, or ongoing control by a third party. As long as the controller holds the cryptographic keys, the identity remains valid and usable.
Interoperable Across Systems and Services
DIDs are designed to work across different networks, applications, and ecosystems. The same DID can be used to authenticate, receive Verifiable Credentials, and prove claims across multiple services, without creating new accounts each time.
What is a Digital Identity Wallet and Why Is It Important?
A digital identity wallet is the control layer of decentralized identity systems. It is where users store their Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs), and where they manage consent, sharing, and verification of their identity data.
Unlike Web2 identity systems, where platforms store and control user accounts, a digital identity wallet puts users in charge. The wallet allows individuals to decide what information to share, with whom, and for what purpose, without handing over full documents or raw personal data.
How does selective disclosure protect user privacy?
Selective disclosure allows users to share only the minimum information required for a specific verification and it's nothing more.
Instead of revealing full credentials, the wallet can generate cryptographic proofs that answer a verifier’s question without exposing raw data.
Share Only Required Attributes
For example, a service may only need to know whether a user is over 18, not their name, date of birth, or ID number. The wallet discloses only the required attribute.
Prove Statements Without Revealing Raw Data
Users can prove statements such as:
- “I am over 18”
- “I hold a valid license”
- “I passed KYC checks”
All without sharing the original documents or credentials.
Reduce Data Leakage and Tracking Risk
Because users do not repeatedly submit full identity documents:
- Sensitive data is not copied across platforms
- Verifiers cannot track users across services
- The risk of data breaches and misuse is significantly reduced
Are Decentralized Identifiers Secure and Privacy-Preserving?
DIDs matter today because of their security and privacy model, which rests on cryptography.
Decentralized Identifiers (DIDs) are designed to be secure by cryptography and private by architecture. Instead of relying on centralized databases or identity providers, DIDs use cryptographic verification to prove control and authenticity.
This means a verifier checks control of a DID with a signature, without asking the platform that issued an account. As a result, DIDs reduce common risks found in traditional identity systems, such as data breaches, identity theft, and unauthorized tracking.
Most importantly, DIDs do not store personal or sensitive data on-chain. They only enable verification of control and validity, keeping identity data under the user’s control.
How do cryptographic proofs secure decentralized identifiers?
DIDs rely on well-established cryptographic mechanisms to ensure both security and privacy.
Public-Private Key Pairs
Each DID is controlled through a cryptographic key pair:
- The private key is held securely by the DID controller (usually in a digital identity wallet)
- The public key is published in the DID Document
Only the entity holding the private key can prove control of the DID, making impersonation extremely difficult.
Digital Signatures for Authenticity
When a DID is used for authentication or verification, the controller signs a message with their private key.
Verifiers can independently check this signature using the public key from the DID Document.
This ensures:
- The identity is authentic
- The message has not been altered
- No central authority is required
No Sensitive Data Written On-Chain
Blockchains or verifiable data registries are used only to:
- Anchor the DID
- Enable resolution to the DID Document
They do not store names, IDs, credentials, or personal attributes. All sensitive data remains off-chain, wallet-controlled, and shared only when the user explicitly consents.
What Is Decentralized Identity Management?
Decentralized identity management is the work of running DIDs and credentials over their whole life: creating identifiers and keys, keeping the DID Document current, issuing credentials, and withdrawing them when a fact changes. For an organization that issues or checks credentials, the job a central identity provider's account database used to do moves to keys and credentials that the issuer and the holder control. It comes down to three tasks:
- Key management: the controller keeps the private keys safe and, where the DID method allows updates, rotates them by changing the verification methods in the DID Document, so an exposed key can be replaced without a new identifier. Some methods, such as did:key, cannot be updated.
- Issuance: the issuer signs each credential with a key listed in its DID Document, so verifiers can check the signature later by resolving the issuer's DID, without asking the issuer about each credential.
- Revocation: the W3C Verifiable Credentials Data Model 2.0 (a W3C Recommendation since May 2025) lets an issuer add a status entry to a credential, so a verifier can check that a Know Your Customer (KYC) result or a license has not been revoked or suspended.
On the holder's side, the digital identity wallet does the same job: it stores the credentials and asks for consent before it shares a credential, or only the parts of it the verifier needs.
Decentralized Identity Solutions: What a Working System Needs
A decentralized identity solution is a set of parts that work together, not one product. A working system needs five of them:
| Part | What it does | Common choices |
|---|
| DID method | Rules for creating and resolving identifiers | did:web, did:key, blockchain-based methods such as did:ethr |
| Credential format | How signed claims are written and checked | W3C Verifiable Credentials 2.0, SD-JWT VC (IETF draft), ISO mdoc (ISO/IEC 18013-5) |
| Wallet | Stores credentials, manages consent and selective disclosure | Mobile identity wallets, such as the EU Digital Identity Wallet, which EU Member States must offer by the end of 2026 |
| Status and revocation | Shows whether a credential is still valid | Status lists published by the issuer or a party acting for it |
| Trust list | Names the issuers a verifier accepts | Government or industry lists of trusted issuers |
Most of the technology parts follow published standards or late-stage drafts. The harder choice is often the trust list: a verifier still has to decide which issuers it accepts, and for regulated firms, KYC rules and eIDAS 2 (Regulation (EU) 2024/1183, in force since 20 May 2024) shape that choice.
What Are the Current Limitations and Challenges of DIDs?
While Decentralized Identifiers (DIDs) provide a strong foundation for secure and privacy-preserving digital identity, their adoption still faces several practical and ecosystem-level challenges. These limitations are not fundamental flaws, but rather maturity and coordination issues common to emerging infrastructure technologies.
Understanding these challenges helps organizations and developers adopt DIDs realistically and responsibly.
Wallet UX and key management
Limitation:
Decentralized identity shifts key ownership to users. Unlike Web2 accounts, there is no centralized password reset or account recovery by default.
Challenge:
Managing private keys can be difficult for non-technical users. Poor wallet UX, unclear recovery flows, and fear of key loss remain major barriers. While solutions like key rotation, social recovery, and custodial-assisted wallets are emerging, balancing usability with strong security is still an ongoing challenge.
Interoperability across ecosystems
Limitation:
Although DIDs are designed to be interoperable, multiple DID methods exist, each with different resolution and implementation approaches.
Challenge:
Not all wallets, registries, and platforms support the same standards consistently. Cross-ecosystem verification, especially across blockchains, enterprises, and jurisdictions, often requires additional integration work. While the W3C DID Core standard provides a shared foundation, ecosystem-level alignment is still evolving.
Regulatory and institutional readiness
Limitation:
DID technology is advancing faster than regulatory frameworks and institutional adoption.
Challenge:
Legal recognition of decentralized identifiers and Verifiable Credentials varies across regions. Many enterprises and governments remain cautious about identity models they do not directly control. However, active pilots in KYC, digital credentials, and cross-border identity indicate growing institutional readiness over time.
Why Decentralized Identity Matters More After the 2026 Revolut KYC Leak
In September 2026 Revolut confirmed that it had sent customer data to an unauthorised party who posed as a government agency, using an email account on a real agency domain. Revolut called it "a sophisticated external impersonation scam" (TechCrunch, 12 September 2026). According to the customer notice as reported, the data included dates of birth, addresses and copies of passports and driver's licences, and possibly verification selfies and transaction histories. Revolut said a limited number of customers were affected and did not give a number.
This was not a hack of Revolut's systems. The files left through a request process that looked normal. That is the weak point of centralized identity: a company that holds full identity files is only as safe as every channel that can ask for them, and the same passport copy often sits with many companies at once.
Decentralized identity changes what a service holds. With DIDs and
Verifiable Credentials, a service can receive proof that a user passed KYC or is over 18 instead of the document itself, so there is less raw data to hand over by mistake. Financial institutions are adopting this through
zkKYC. Regulators point the same way: the EU's European Digital Identity Framework (eIDAS 2, Regulation (EU) 2024/1183) requires the EU Digital Identity Wallet to support selective disclosure, and its Recital 14 asks Member States to build privacy-preserving technologies, such as Zero-Knowledge Proofs, into the wallet (EUR-Lex, Regulation (EU) 2024/1183, Recital 14).
How zkDatabase Strengthens Decentralized Identity Systems
Decentralized identity systems depend on more than just identifiers, they depend on
verifiable data. While
Decentralized Identifiers (DIDs) establish who controls an identity, trust at scale requires proof that
identity-related data was stored and processed as claimed, untampered and auditable over time.
Orochi Network builds
zkDatabase for this layer.
How zkDatabase Supports Verifiable Identity Data
-
Proves integrity of off-chain identity data:
Identity-related records (e.g., KYC status, credential validity, revocation states) are stored off-chain with a proof for every update, so any change is detectable.
-
Enables audit-ready verification workflows:
zkDatabase produces succinct proofs that verification steps were executed correctly, allowing auditors and regulators to validate identity processes without accessing raw personal data.
-
Preserves privacy while ensuring correctness:
By using Zero-Knowledge Proofs, zkDatabase lets identity systems prove that an eligibility or compliance check ran as claimed, without revealing underlying identity attributes.
Conclusion
Decentralized identity is more than a new identity format. It represents a shift toward user-owned, cryptographically verifiable digital identity. By replacing centralized logins with decentralized identifiers, DIDs enable secure authentication and privacy-preserving verification without relying on institutional trust.
As decentralized identity expands into enterprise and regulated environments, trust must be provable, not assumed. Orochi Network strengthens this foundation through zkDatabase, enabling identity-related data to be verified, auditable, and tamper-resistant while preserving privacy. Together, DIDs, Verifiable Credentials, and Verifiable Data Infrastructure form the basis of a more secure, interoperable future for digital identity.
FAQs
What is decentralized identity?
Decentralized identity lets people and organizations prove facts about themselves with identifiers and credentials they hold, instead of a central provider holding their identity files. It is built on Decentralized Identifiers (DIDs), Verifiable Credentials and selective disclosure.
What is a Decentralized Identifier (DID)?
A Decentralized Identifier (DID) is a user-controlled digital identifier that enables cryptographic verification of identity without relying on a centralized authority. A DID is created and managed by its controller and resolves to a DID Document containing public keys and verification methods, without storing personal data.
How does a DID work in decentralized identity systems?
A DID works by linking an identifier to cryptographic keys published in a DID Document. When authentication or verification is needed, the DID controller proves control by signing messages with a private key, which can be independently verified using the corresponding public key.
Why does decentralized identity (DID) matter?
Because today’s digital identity is fragile, invasive, and centralized and it doesn’t scale to a world that needs privacy, interoperability, and verifiable trust.
Explore zkDatabase (
https://www.zkdatabase.org/) to see how identity data stays private and checkable.