The EUDI Wallet and blockchain-based digital ID differ fundamentally in how they work, who controls them, and what legal weight they carry. The European Digital Identity Wallet is a regulated, government-backed framework built on attestations and eIDAS 2.0 legislation, which amends Regulation (EU) 910/2014. Blockchain identity systems are decentralized, often privately developed, and rely on distributed ledger technology to establish trust. This article unpacks the key differences, explores how each approach works, and helps organizations understand which one is relevant for their context.
How does the EUDI Wallet store and share identity data?
The European Digital Identity Wallet stores identity data as cryptographically signed attestations directly on the user’s device, not on a central server or shared ledger. Trusted issuers such as governments, banks, or healthcare providers issue these attestations, and users present them selectively to services that need to verify their identity.
This model places the user in control of their own credentials. The user holds attestations in a wallet instance, chooses which attributes to share, and shares only what is strictly necessary for a given interaction. For example, a user proving they are over 18 can use selective disclosure of the relevant attribute without revealing their exact date of birth.
Trust in this system does not come from a blockchain or a central database. It comes from the cryptographic signature of the issuer, verified against national trusted lists that are brought together in the EU List of Trusted Lists (LOTL). When a relying party such as a bank or government portal receives an attestation, it verifies the issuer’s digital signature against the relevant national trusted list. Verification also involves checking the revocation status of the attestation via the issuer’s status information, and checking the wallet unit attestation to confirm that the presenting wallet runs on a certified wallet solution. The issuer’s signature can be verified offline, but revocation status and wallet unit attestation checks require a connection.
The first four Large Scale Pilots ran from April 2023 to 2025 and tested this model across practical everyday scenarios. The POTENTIAL consortium piloted opening a bank account, presenting a mobile driving licence, claiming prescriptions, qualified remote signing, and accessing government services. The EWC consortium piloted Digital Travel Credentials, payments, and organisational digital identity. NOBID focused on payments, and DC4EU covered education and social security. These pilots involved over 350 organisations from 26 EU Member States and provided real-world evidence that the holder-centric, attestation-based approach works at scale. A second wave of pilots started in 2025: WE BUILD covers business wallets and payments, and APTITUDE covers travel, ticketing, vehicle registration, and payments.
How does blockchain-based digital ID work?
Blockchain-based digital identity systems use a distributed ledger to anchor identity data or cryptographic proofs in a way that is tamper-evident and verifiable without a central authority. Trust is derived from the consensus mechanism of the blockchain itself, not from a regulated issuer’s signature verified against a government trusted list.
In practice, most blockchain identity systems use a model called Self-Sovereign Identity (SSI). Users generate a Decentralized Identifier (DID), which is a unique identifier anchored to a blockchain. Credentials can then be issued and verified against this DID. The blockchain acts as a public trust anchor, confirming that a DID is valid and that the associated keys have not been revoked.
There are two broad categories worth distinguishing here:
- Public blockchain identity: DIDs and credential metadata are written to a public, permissionless ledger such as Ethereum. Anyone can read and verify the information, but privacy and regulatory compliance can be challenging to achieve.
- Private or permissioned blockchain identity: A consortium of organisations runs a controlled ledger. This offers more governance and compliance potential, but it reintroduces elements of centralised control.
The SSI model and verifiable credential standards used in many blockchain identity systems share some technical vocabulary with the EUDI Wallet. Both reference concepts such as decentralized identifiers and selective disclosure. The key difference lies in where trust is anchored and who governs the system.
What are the key differences between the EUDI Wallet and blockchain ID?
The most important difference between the EUDI Wallet and blockchain-based digital ID is the source of trust and the legal framework that surrounds it. The EUDI Wallet derives trust from regulated government issuers operating under eIDAS 2.0, which amends Regulation (EU) 910/2014. Blockchain identity systems derive trust from cryptographic consensus on a distributed ledger, which carries no inherent legal standing under EU law.
Here is a direct comparison of the two approaches across the dimensions that matter most for organisations:
- Trust anchor: The EUDI Wallet relies on qualified trust service providers and government-issued attestations verified against national trusted lists in the EU List of Trusted Lists. Blockchain ID relies on the integrity of the ledger and the issuer’s reputation.
- Legal recognition: EUDI Wallet attestations issued under eIDAS 2.0 have legal effect across all EU Member States. Blockchain credentials have no automatic legal recognition in the EU.
- Governance: The EUDI Wallet framework involves shared responsibility across multiple actors. The European Commission manages the legal framework and adopts implementing acts. EU Member States provide or mandate wallet solutions, certify and notify them, and supervise actors within their jurisdiction. The European Digital Identity Cooperation Group supports cross-border alignment. National competent authorities, wallet providers, issuers, qualified trust service providers, and relying parties each carry distinct roles. Blockchain identity governance varies widely by project and consortium.
- Interoperability: The EUDI Wallet framework is designed so that a certified wallet from one Member State can be used with an appropriate relying party in another Member State, with cross-border interoperability mandated by regulation. In practice, the scope of available use cases and the maturity of national implementations may develop in phases. Blockchain identity systems require bilateral agreements or shared standards to achieve interoperability.
- Privacy design: Both approaches can support selective disclosure and minimal data sharing. The EUDI Wallet framework mandates GDPR compliance and privacy-by-design at the regulatory level. A relying party also needs its own legal basis under the GDPR for processing the data it receives.
- Adoption path: EUDI Wallet rollout is driven by EU legislation, meaning organisations in regulated sectors will need to accept it. Blockchain identity adoption is voluntary and market-driven.
The underlying credential technology shares some vocabulary across both worlds, but the governance layer, legal enforceability, and institutional trust infrastructure are entirely different.
Is the EUDI Wallet built on blockchain technology?
No, the EUDI Wallet is not built on blockchain technology. It uses cryptographically signed attestations stored on the user’s device, with trust anchored in regulated issuers listed on national trusted lists brought together in the EU List of Trusted Lists, not on a distributed ledger.
This is a common misconception, partly because both the EUDI Wallet and some blockchain identity systems use concepts like decentralized identifiers and selective disclosure. The technical vocabulary overlaps, but the underlying architecture does not.
The EUDI Wallet architecture, as elaborated in the Architecture and Reference Framework (ARF), is built around three core components: the wallet unit held by the user, issuers that are trusted entities issuing attestations, and relying parties that verify attestations. The ARF provides the technical elaboration of the requirements set out in the implementing acts adopted by the European Commission. The credential formats prescribed by the ARF are mdoc and SD-JWT VC. The trust chain runs through regulated institutions and cryptographic signatures verified against national trusted lists, not through a blockchain consensus mechanism.
This design choice was deliberate. Blockchain-based systems introduce complexity around key management, transaction fees, ledger governance, and data immutability that can conflict with GDPR requirements, particularly the right to erasure. The EUDI Wallet framework avoids these tensions by keeping personal data off any shared ledger entirely.
Which approach offers stronger legal recognition across Europe?
The EUDI Wallet offers significantly stronger legal recognition across Europe. Under eIDAS 2.0, attestations issued through the European Digital Identity Wallet framework have mandatory legal effect across all EU Member States. Blockchain-based digital identity systems currently have no equivalent legal standing under EU law.
This distinction has real consequences for organisations operating in regulated sectors. A qualified electronic signature issued through the EUDI Wallet framework has the same legal effect as a handwritten signature across the EU. An equivalent action performed using a blockchain identity system would need to meet separate legal requirements in each jurisdiction, and in many cases would not satisfy them at all. It is also worth noting that national form requirements remain applicable even where eIDAS 2.0 establishes the legal effect of electronic signatures.
For sectors such as financial services and government services, where legal certainty is non-negotiable, this difference is decisive. Accepting a blockchain credential for KYC, contract signing, or benefits access without additional legal validation introduces compliance risk that most organisations in regulated industries cannot afford to take. KYC re-use is governed by AML legislation, not by eIDAS 2.0 itself.
The legal landscape could evolve. The EU is actively exploring how decentralised identity and blockchain-based credentials might fit within future regulatory frameworks. As of 2025, the EUDI Wallet is the only digital identity approach with built-in, cross-border legal recognition across the EU.
When should an organisation consider each identity approach?
Organisations operating in regulated EU sectors should prioritise EUDI Wallet readiness. Under eIDAS 2.0, each EU Member State must have at least one certified EUDI Wallet available for citizens, residents, and businesses by 24 December 2026. This is the legal deadline for Member States’ wallet obligations. It does not guarantee that every national wallet will have reached the same level of maturity or that every possible cross-border use case will be fully operational throughout Europe on that date. Practical interoperability and national rollout are expected to develop in phases, and organisations should plan accordingly. Public sector bodies must accept notified wallets as a means of identification from that date.
Regulated private sector organisations are required to accept the EUDI Wallet where strong user authentication is legally or contractually required, with that obligation applying from 24 December 2027. The sectors covered include banking and financial services, healthcare, telecoms, energy, transport, education, social security, drinking water, postal services, digital infrastructure, and digital services. Micro and small enterprises with fewer than 50 employees and an annual turnover or balance sheet total of no more than 10 million euros are exempt. Very large online platforms serving more than 45 million users in the EU are covered under a separate provision: for those platforms, the obligation applies where the platform requires user authentication, on the voluntary request of the user and for the minimum necessary data.
Before a relying party can request wallet data, it must register with the national authority of its Member State of establishment under CIR (EU) 2025/848 of 6 May 2025. Registration specifies, per intended use, which attributes and attestations will be requested. The wallet checks requests against this registered scope.
A practical way to think about this is by use case:
- EUDI Wallet is the right choice when you need legally recognised identity verification, qualified electronic signatures, cross-border interoperability within the EU, or compliance with eIDAS 2.0 obligations in sectors like finance, healthcare, or government.
- Blockchain identity may add value in supply chain credential verification, cross-industry trust registries, or scenarios where multiple independent parties need to verify credentials without relying on a single central authority, and where legal enforceability is not the primary requirement.
For organisations in the regulated sectors listed above, accepting the EUDI Wallet is not optional in the long run. Building your identity infrastructure around that foundation is the most future-proof strategic approach available today.
Organisations in healthcare, for example, will need to support attestation-based identity for prescription handling, cross-border patient identification, and access to health records. These are areas where the EUDI Wallet’s legal recognition and privacy guarantees are essential, and where blockchain identity alone would not satisfy regulatory requirements. Cross-border use cases in healthcare remain subject to sector-specific legislation and national registration requirements, which the EUDI Wallet framework does not remove. Processing health data also requires a legal basis under both Article 6 and Article 9(2) of the GDPR.
How the ID Connector supports EUDI Wallet acceptance
The ID Connector is an integration that lets relying parties accept every certified European wallet, whatever Member State issued it, for identification, login and qualified signing. EUDI Wallet acceptance comes first; the same interface also carries other IDs, such as national eIDs, bank IDs and identity documents, inside and outside the EU.
For organisations comparing the EUDI Wallet and blockchain-based identity, the ID Connector addresses the practical side of EUDI Wallet acceptance. It handles verification of issuer signatures against the relevant national trusted lists in the EU List of Trusted Lists, checks revocation status via issuer status information, and validates wallet unit attestations to confirm that a presenting wallet runs on a certified wallet solution. It also monitors the registered attribute scope set out in the relying party’s registration under CIR (EU) 2025/848, so that only the data the organisation is authorised to request is exchanged. For use cases involving qualified signing, the ID Connector connects to a qualified trust service provider.
Organisations in financial services, healthcare, pharma, and government can use the ID Connector to build EUDI Wallet acceptance into their existing identity flows without rebuilding their infrastructure from the ground up. Get in touch to discuss what the EUDI Wallet means for your organisation and how to prepare.