DID
A DID, or Decentralized Identifier, is a globally unique identifier that does not depend on a central registry. It lets issuers, holders and verifiers reference each other and resolve public keys without a central authority.
A DID resolves to a small document listing the public keys and service endpoints its owner controls, so anyone can verify a signature made with that DID without asking a third party for permission.
Every DID has the same shape: the scheme did, a method name, and an identifier that method knows how to resolve, as in did:web:credenco.com. The method decides where the document lives and who keeps it reachable.
The identifier stays fixed while the keys inside its document can be replaced, so an issuer can rotate a compromised key without reissuing everything it ever signed.
The EUDI Wallet trust model under eIDAS 2.0 does not run on DIDs: its Architecture and Reference Framework builds interoperability for the PID and for qualified and public body attestations on an X.509 PKI, with issuer trust anchors published in national Trusted Lists and in Lists of Trusted Entities published by the Commission. Non-qualified attestations may use other trust models, and DIDs remain common in the wider verifiable credential ecosystem, where they identify issuers and, in some credential formats, holders. A DID does not vouch for anyone, though: it shows that the same party signed two things, not that the party is a licensed bank. That judgement comes from a Trust Framework or a trusted list on top.
Read the full explanation
This page gives the short definition. Our explainer shows what it means in practice: who is involved, how it works and what changes for your organisation.
DID explainedWho controls a DID?
The organisation or person the DID identifies, called its subject, controls it by holding the private key that matches the public key in the DID document. No registry or central authority can revoke or reassign a DID on its subject's behalf.
What do the parts of a DID mean?
Every DID has three parts: the scheme did, a method name, and an identifier that method knows how to resolve, as in did:web:credenco.com. The method decides where the DID document lives and who keeps it reachable. The identifier stays fixed even when the keys inside its document are replaced.
Does the EUDI Wallet use DIDs?
Not for the credentials eIDAS 2.0 regulates. The Architecture and Reference Framework builds interoperability for the PID and for qualified and public body attestations on an X.509 PKI, with issuer trust anchors in national Trusted Lists. Non-qualified attestations may use other trust models, and DIDs remain common in the wider verifiable credential ecosystem.