Join the Community

23,807
Expert opinions
40,562
Total members
385
New members (last 30 days)
199
New opinions (last 30 days)
29,224
Total comments

About EUDI in relation to DID - and DIIP

1. Governance First, Tech Second

  • The EU Digital Identity Wallet (EUDI) is based on regulated trust frameworks: Member States, Qualified Trust Service Providers (QTSPs), and regulated conformity assessment bodies.

  • DIDs, by design, are decentralized identifiers without a single root of trust. The EU didn’t want identifiers that anyone could spin up without governance. Instead, EUDI builds on eIDAS 2.0 and a legal trust infrastructure.


2. Traceability & Accountability

  • EU policy requires clear accountability chains. For example:

    • Who issued a credential?

    • Who is the wallet provider?

    • Who can revoke or suspend trust?

  • With DIDs, control is often anchored in cryptographic keys, but governance and liability are less clear.

  • The EU wanted auditable, accountable, and revocable identifiers, aligned with AML/KYC and GDPR.


3. Avoiding Fragmentation

  • DIDs are not standardized across ecosystems. Multiple DID methods exist (did:webdid:iondid:key, etc.), with different trust anchors and resolution methods.

  • This risks interoperability issues in a Single Market project where all 27 Member States must work seamlessly.

  • Instead, the EU opted for a common Trust List and Registry approach, building on the successful eIDAS “Trusted List” of QTSPs.


4. Practical Interop vs. Ideological Decentralization

  • EUDI is not anti-DID—it just doesn’t rely on them. The EU relies on Verifiable Credentials (VCs) and W3C standards (JSON-LD, JWT).

  • DIDs could still be used inside the system (e.g., wallets supporting DIDComm for messaging), but the trust anchor is always the regulated EU Trust Infrastructure—not an unregulated DID registry.


5. Future Flexibility

  • The EU approach is more cautious: get wallets running first under a regulated model, then maybe later allow DIDs for certain cross-border or private-sector use cases.

  • Some pilot projects (e.g., EBSI, Findynet, IDunion) do experiment with DIDs, but EUDI core regulation doesn’t mandate them.


✅ Summary:
The EU avoided DIDs in EUDI because it prioritised governed trust lists, accountability, and legal compliance over decentralized identifiers. DID technology may still play a role, but it isn’t the foundation—the legal trust model is.


 
The DIIP (Digital Identity Interoperability Project / Pilot) under the EUDI framework has taken a more experimental stance than the strict eIDAS regulation itself. That’s where DIDs come in.

Here’s how DIIP has been using them:


1. DIDs as Technical Identifiers

  • DIIP pilots have tested W3C DIDs as a way for issuers, holders, and verifiers to reference each other in verifiable credential exchanges.

  • The DID is not the legal trust anchor (that still comes from the EU Trust List or national registries), but it’s used as a technical handle for cryptographic messaging.


2. DIDComm for Messaging

  • Many DIIP pilots explored DIDComm v2 as the secure messaging protocol between wallets and verifiers/issuers.

  • Example: instead of inventing a new protocol for wallet–verifier connections, they re-used DIDComm’s peer-to-peer encrypted channel setup.


3. Bridging Centralised & Decentralised Trust

  • DIIP wanted to test interoperability: how can a wallet that uses a DID method interoperate with a wallet that uses the EU’s central trust list?

  • Pilots showed that DIDs can wrap or reference entities that are also on the EU Trusted List.

    • For example, a QTSP can have both a DID and an EU-listed identifier.

    • The DID gives flexibility in messaging and resolution, the EU list gives the governance anchor.


4. Sandboxing Future Use Cases

  • Some DIIP pilots tested cross-border, cross-ecosystem flows (with Canada, South Korea, etc.) where no common EU Trust List exists.

  • In those cases, DIDs worked as a fallback:

    • They allow discovery/resolution across systems.

    • They can be combined with Verifiable Presentations to carry evidence of trust.


5. Key Takeaway

  • In DIIP, DIDs are used as optional technical identifiers and for encrypted communications (DIDComm), not as the root of trust.

  • The legal identity of issuers/verifiers always comes from EU-governed trust registries.

  • Think of it as:

    • EUDI core = Legal/governance anchor (Trust Lists, QTSPs).

    • DIDs in DIIP = Interop tool and technical plumbing for messaging.


👉 So in simple terms: DIIP uses DIDs pragmatically for interoperability and messaging, but the “trust” still flows from eIDAS governance.

Greatly helped by ChatGPT here..

External

This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.

Join the Community

23,807
Expert opinions
40,562
Total members
385
New members (last 30 days)
199
New opinions (last 30 days)
29,224
Total comments

Now Hiring