The Future: Decentralized Identity and Verifiable Credentials
The Identity Model Is Changing
For decades, digital identity has worked the same way. A centralized provider (your app, Google, Facebook, an enterprise directory) stores your credentials and vouches for you. When you log in, the service either checks your credentials against its own database or asks a third party (OAuth, SAML) to confirm who you are. The provider is the authority. You are the subject.
This model works, but it has fundamental problems. Breaches expose huge volumes of credentials because identity data is concentrated in centralized honeypots. Users have little real control over their identity data, which is scattered across hundreds of services with their own terms. And cross-border identity verification is expensive, slow, and often unreliable.
Decentralized identity flips the model. Instead of a provider holding your identity, you hold it. Instead of trusting the provider, the relying party checks cryptographic proofs signed by credential issuers. The building blocks (verifiable credentials, holder wallets, and selective disclosure) are now mature enough that governments are building production systems on them.
This isn't a theoretical future. The EU has legislated it. And it will change how you think about CIAM.
The EU Digital Identity Wallet (eIDAS 2.0)
The European Parliament approved the revised eIDAS regulation in February 2024. It was published as Regulation (EU) 2024/1183 and entered into force in May 2024. It requires every member state to offer citizens and residents a free European Digital Identity Wallet by the end of 2026.
What the regulation sets up:
- Every EU citizen and resident gets access to a government-recognized digital identity wallet
- The wallet stores identity data and attestations: national ID data, driving licenses, diplomas, and more
- Private services that are legally required to use strong user authentication (banking, telecoms, healthcare, transport, and others) must accept the wallet, with obligations landing in late 2027 (Garrigues summary of the timetable)
- Very large online platforms, as designated under the Digital Services Act, must accept the wallet for authentication when a user asks to use it
- Users can disclose only the attributes a service needs (prove you're over 18 without revealing your birthdate)
What this means for CIAM:
- If your product serves EU users in a covered sector, you'll need wallet-based authentication alongside traditional methods
- Your CIAM must be able to verify wallet presentations and the issuers behind them
- The consent model changes: users present data from their wallet, rather than your system collecting and storing it
- Data minimization becomes architecturally enforced, not just a policy
The EU Large-Scale Pilots (POTENTIAL, EU Digital Identity Wallet Consortium, NOBID, and DC4EU) have tested real-world use cases since 2023. The wallet architecture uses OpenID for Verifiable Presentations (OpenID4VP) and OpenID for Verifiable Credential Issuance (OpenID4VCI) as protocols. Its credential formats are SD-JWT VC and the ISO mobile driving license (mdoc) format.
If you sell software to EU users or enterprises, track eIDAS 2.0 implementation now. Wallets roll out through the end of 2026, and acceptance obligations follow in 2027. Companies that wait until enforcement will face the same scramble GDPR caused in 2018.
Verifiable Credentials and DIDs: A Practical Explanation
Let's cut through the jargon. Decentralized identity rests on two core concepts.
Verifiable Credentials (VCs)
A verifiable credential is a digital version of a physical credential, such as a driver's license, a degree, or a professional certification. It can be cryptographically verified without contacting the issuer.
How it works in practice:
- Issuer (a government, university, or employer) creates a credential with claims about you ("Jane Doe, born 1990-05-15, holds a valid driver's license in Germany")
- The issuer digitally signs the credential with its private key
- You (the holder) store the credential in your digital wallet
- When a verifier (say, a car rental service) needs to confirm your license, you present the credential from your wallet
- The verifier checks the signature against the issuer's public key, published in a trusted list or registry, to confirm it's authentic and untampered
The critical difference from traditional identity: the verifier doesn't need to call the issuer. Verification happens cryptographically, not through a real-time API call. That means the issuer doesn't learn when or where you use your credential, which is a significant privacy improvement.
Decentralized Identifiers (DIDs)
A DID is a globally unique identifier that its owner controls, without a central authority issuing or managing it.
Traditional identifiers depend on centralized systems. Your email depends on your mail provider, your domain on a registrar, your social login on Google or Facebook. If any of these disappear or revoke your access, you lose your identifier.
A DID looks like this: did:web:example.com:users:12345 or did:key:z6Mkf5rGMoatrSj1...
DIDs use different "methods." Some anchor to blockchains (did:ethr), some to web infrastructure (did:web), and some are self-certifying (did:key). Not every system uses them. The EU wallet, for example, relies on PKI and trusted issuer lists rather than DIDs, while the EU's separate blockchain infrastructure (EBSI) uses its own did:ebsi method.
Practical impact: DIDs and wallets enable portable identity. A user can carry verified credentials across services. Instead of creating an account from scratch everywhere, they present verified credentials from their wallet.
Selective Disclosure and Zero-Knowledge Proofs
Selective disclosure lets you prove a statement without revealing the underlying data. Zero-knowledge proofs (ZKPs) are the strongest form of it.
Example: A bar needs to verify you're over 21. Today, you show a driver's license that reveals your name, address, date of birth, license number, and photo. With selective disclosure, you prove "I am over 21" and nothing else.
How this applies to CIAM:
- Age verification without collecting birthdates: prove an age threshold, not an exact date
- Income verification without revealing salary: prove "income above $50K" for financial services
- Credential verification without storing credential data: confirm a professional license is valid without copying it
- Geographic eligibility without revealing location: prove "EU resident" without revealing country or address
Today's EU wallet formats (SD-JWT VC and mdoc) achieve selective disclosure with salted hashes, not ZKPs. ZKP-based schemes add unlinkability, so verifiers can't correlate presentations, and they are being studied for future versions. Modern ZKP systems are fast enough on phones that the remaining barriers are standards and certification, not raw performance.
Selective disclosure is arriving with the EU wallet now; full zero-knowledge proofs will follow as standards settle. CIAM platforms that verify wallet presentations natively will have an edge in privacy-sensitive markets (healthcare, fintech, government).
Where the Decentralized Identity Market Is Heading
Analyst estimates of the decentralized identity market vary widely by definition, so I won't anchor on one number. The direction is clearer than the size, and it is driven by four forces:
Regulation: Beyond eIDAS 2.0, governments are building digital identity infrastructure: Australia passed its Digital ID Act in 2024, India keeps expanding the Aadhaar ecosystem, and Brazil runs GOV.BR. Canada's Pan-Canadian Trust Framework sets interoperability rules.
Enterprise use cases: Companies are exploring verifiable credentials for supply chain verification (prove a component meets environmental standards), employee credential checks (verify certifications without manual background checks), and reusable KYC/AML onboarding.
Standards convergence: The W3C Verifiable Credentials Data Model 2.0, DID Core, the OpenID for Verifiable Credentials family, SD-JWT VC, and ISO mdoc give implementers interoperable building blocks. The debate has shifted from "can this work?" to "which format and protocol fit my use case?"
Vendor activity: Microsoft (Entra Verified ID), Ping Identity, SpruceID, and others ship verifiable credential products. Avast (now Gen Digital) acquired Evernym, an early self-sovereign identity company, in 2021.
What Enterprises Need to Prepare for Now
You don't need to implement decentralized identity today. But you do need to make decisions now that won't make it painful later. Here's what's actionable:
1. Ensure Your CIAM Architecture Supports Credential Presentation
Traditional CIAM assumes the identity provider holds user data. Verifiable credentials invert this: the user presents data to you. Your CIAM needs to evolve from "store and retrieve user attributes" to "verify presented credentials."
Action now: Choose a CIAM vendor with a verifiable credentials roadmap or extensible authentication flows. Vendors with custom authentication pipelines (Auth0 Actions, FusionAuth Lambdas) will be easier to extend for credential verification.
2. Adopt Standards-Based Protocols
If your authentication uses standard protocols (OAuth 2.0, OIDC), extending to the OpenID for Verifiable Credentials specifications is relatively straightforward. If you've built proprietary flows, the move will be harder.
Action now: Ensure all authentication flows use standard OAuth 2.0/OIDC. Eliminate proprietary token formats and authentication mechanisms.
3. Implement Data Minimization
The decentralized model rests on collecting only the data you need. Start practicing this now, even with traditional CIAM. Don't collect birthdates if you only need an age check. Don't store addresses if you only need country-level location.
Action now: Audit your user data model. For each attribute, document why you collect it and whether you could get the same outcome with less data. This prepares you for flows where you verify attributes without storing them.
4. Build for Credential Portability
Users will increasingly expect to bring verified credentials from their wallets instead of re-entering information and repeating verification. KYC processes that take days could happen in minutes with pre-verified credentials.
Action now: Design onboarding on the assumption that credentials will eventually be presented rather than collected. Build verification logic that accepts external assertions, not just self-reported data.
5. Track the EU Timeline
The eIDAS 2.0 rollout is phased:
- May 2024: Regulation (EU) 2024/1183 enters into force
- Late 2024 through 2025: The Commission adopts implementing acts with the technical specifications
- By end of 2026: Member states make wallets available
- Late 2027: Regulated private relying parties that require strong authentication must accept the wallet
- 2028 and beyond: Broader adoption across sectors
Action now: If you serve EU users in a covered sector, put wallet acceptance on your 2027 roadmap and staff it in the first half of the year.
Practical Adoption Roadmap
Phase 1: Foundations (Now to Q1 2027)
- Ensure standards-based authentication (OAuth 2.0, OIDC) is in place
- Implement data minimization in your current CIAM setup
- Select a CIAM vendor with a verifiable credentials roadmap
- Assign a team member to track W3C VC, OpenID for Verifiable Credentials, and eIDAS 2.0 developments
- Experiment with open-source verifiable credential libraries in a sandbox
Phase 2: Pilot (Q1 2027 to Q2 2027)
- Build a proof of concept that accepts credentials for one use case (age verification, professional credential checks, or KYC)
- Test against at least one EU Digital Identity Wallet implementation
- Develop the ability to issue credentials yourself (employee badges, customer certifications)
- Define policies for which credentials you accept and from which issuers
Phase 3: Production (Q3 2027 to Q4 2027)
- Deploy wallet-based authentication alongside traditional methods
- Implement selective disclosure for privacy-sensitive attributes
- Build user-facing UI for credential presentation (wallet connection, credential selection, consent)
- Integrate credential verification into compliance workflows
Phase 4: Optimization (2028+)
- Reduce reliance on stored attributes as credential-based verification matures
- Add zero-knowledge proof verification for sensitive attributes as standards allow
- Explore issuing your own credentials (loyalty status, subscription tier, verified purchaser)
- Build credential-based authorization policies (grant access based on presented credentials, not stored roles)
You don't need to become a decentralized identity expert overnight. Companies that build foundations now (standards-based auth, data minimization, extensible CIAM) will adapt in months while competitors spend years catching up. Treat it like GDPR: the companies that prepared early had an advantage, and the ones that waited scrambled.
How This Changes CIAM Selection Criteria
Decentralized identity adds new criteria to the evaluation framework from Chapter 2:
New Evaluation Questions
-
Does the vendor have a verifiable credentials roadmap? Ask specifically about OpenID4VP, SD-JWT VC, mdoc, and the W3C Verifiable Credentials Data Model 2.0. "We're watching the space" is not a roadmap.
-
Can the platform verify externally presented credentials? This is different from issuing them. Your CIAM must accept and validate credentials users present from their own wallets.
-
Does the platform support selective disclosure? Can it handle presentations that reveal only specific attributes?
-
Is the authentication pipeline extensible enough for new credential types? You need to add verification methods without replacing your CIAM. Look for webhook-based or serverless extension points.
-
How does the vendor handle the shift from stored identity to presented identity? Moving from "we hold your data" to "you present your data" is fundamental. The vendor should have a coherent plan for it.
-
Does the vendor participate in standards bodies? Active work in the W3C, the OpenID Foundation, or the Decentralized Identity Foundation signals commitment. Passive observation signals a late adopter.
Vendors Active in Decentralized Identity
- Microsoft: Entra Verified ID is in production and uses did:web, which resolves trust from the issuer's web domain (it earlier anchored identifiers on ION, a Bitcoin-based DID network)
- Ping Identity (which absorbed ForgeRock): active in standards work, with verifiable credential products in market
- Okta/Auth0: ask for the current status and roadmap; verifiable credentials have not been a headline Auth0 feature
- SpruceID: open-source focused; built DIDKit and the Sign-In with Ethereum specification
- Trinsic: API-first platform for accepting digital IDs and wallets
Most developer-first CIAM vendors have not made verifiable credentials a core feature. That's expected, since their startup and growth-stage customers have less immediate demand. As eIDAS 2.0 acceptance deadlines approach, expect that to change. Before you take a vendor's word on standards support, read the plain-language Verifiable Credentials and SD-JWT page on Start with Identity. It covers the issuer, holder and verifier roles, and how credentials are issued, presented and revoked.
The Big Picture
The transition from centralized to decentralized identity won't happen overnight. It will be gradual, messy, and uneven across geographies and industries. For the next several years, you'll need to support both models: traditional CIAM (passwords, passkeys, social login, SSO) and credential-based verification (wallets, verifiable credentials, selective disclosure).
The CIAM vendors that win after 2028 will bridge those two worlds, serving users with traditional auth today while preparing for credential-based auth tomorrow. Your job as a buyer is to pick a vendor building that bridge, not one that will strand you on the wrong side of it.
The identity layer you choose today will serve your product for years. Make sure it can handle not just the authentication patterns of 2026, but the credential-based model governments and standards bodies are building right now.
For more on this shift, see my enterprise playbook for decentralized identity and verifiable credentials.