EU eIDAS 2.0 and European Digital Identity Wallet

eIDAS 2.0 Reality

Regulation (EU) 2024/1183 entered into force in May 2024 as the formal revision of the original 2014 eIDAS framework. It imposes on every Member State the obligation to issue at least one EUDI Wallet to its citizens and residents within the implementation window set by the regulation and the implementing acts that follow it. The Architecture Reference Framework (ARF), maintained by the Commission and the Member States in cooperation, supplies the technical specification: wallet structure, attestation formats (including ISO/IEC 18013-5 mobile-driving-licence profiles and W3C Verifiable Credentials), the trust framework for qualified electronic attestations of attributes, and the interoperability requirements between national wallets.

The deployment surface is broader than identity in the narrow sense. EUDI Wallets are scoped to carry payment-relevant credentials, professional qualifications, educational diplomas, healthcare entitlements, mobility credentials, and commercial-sector attestations — anywhere a Member-State-grade identity assertion is the precondition for an interaction. The relying-party surface includes every Member State public administration, every regulated commercial counterparty under sectoral mandates (banking, telecoms, insurance, large platforms), and a voluntary commercial surface that the regulation explicitly invites.

Mandatory Interoperability

The regulation's load-bearing element is mandatory cross-member-state interoperability. A wallet issued by one Member State must function — for identification, authentication, and credential presentation — in every other Member State, against every relying party covered by the regulation. The ARF translates this into a concrete set of properties: common attestation formats, common cryptographic schemes, common trust-list mechanisms, and a common revocation and lifecycle posture. The implementing acts adopted in 2024 and 2025 sharpen these requirements into enforceable timelines, and Member States are scaling pilot deployments under the Large-Scale Pilots (POTENTIAL, EWC, NOBID, DC4EU) toward general availability.

The interoperability obligation is not merely format-level. It extends to the chain that connects an issuer (a Member State authority, a qualified trust service provider, a sectoral attestation issuer) through a wallet (operated by or on behalf of the citizen) to a relying party (in another Member State, in another sector, under another regulator). At each handoff, the chain must preserve the binding between the credential, the issuer's authority to issue it, the wallet's binding to the holder, and the relying party's permitted-use scope. The regulation requires this chain to function across heterogeneous national implementations without bilateral integration — a property that has no precedent in EU digital infrastructure at this scale.

Governance-Chain Substrate

Governance chain as an architectural primitive is built on a five-property structure — issuance, binding, presentation, verification, and lineage — where each link in the chain is recorded as a provenance event rather than reconstructed from operational logs. The five properties are substrate-level: a credential is issued under a declared issuer credential; it is bound to a wallet under a declared binding event; it is presented to a relying party under a declared presentation scope; it is verified against a declared trust anchor; and the entire sequence is recorded as a lineage object that the holder, the relying party, and the issuer can each independently audit without reference to a central log.

Mapped onto the EUDI Wallet architecture, the substrate corresponds to exactly the chain the ARF requires but does not, by itself, supply as a uniform architectural element. EUDI Wallet operations operate through the governance-chain primitive: cross-member-state operations admit through declared federation, where each Member State's trust list is a federation parameter rather than a bilateral integration; sectoral attestations enter as additional credential classes whose admissibility is declared at the issuer-trust-list layer; private-sector relying-party operations admit through the same five-property chain that public-sector operations use, with the permitted-use scope as the differentiating parameter. The lineage record is the artifact that satisfies both the holder's data-protection rights under the GDPR and the relying party's audit obligations under sectoral law.

EU Position

For the EU ecosystem, the substrate is not an alternative to the ARF — it is the architectural element that makes the ARF's interoperability obligation operationally complete. The ARF specifies the formats, the cryptography, and the trust framework; the substrate supplies the chain semantics that make the formats compose across Member States. Without a uniform chain primitive, each pairwise interoperation reverts to bilateral arrangement at the implementation layer; with one, the federation is structural and the cross-border scenario reduces to a substrate property rather than a project plan.

The position is sharpest for the high-value scenarios the regulation is meant to enable. A Spanish-issued EUDI Wallet presenting a German-issued professional qualification at a Dutch relying party in a regulated sector is not a bespoke integration; it is a single chain composed of declared links, each with its own admissibility, recorded once and verifiable everywhere. The Member States gain a uniform architectural substrate; the Commission gains a structural answer to the interoperability obligation; the citizens gain a portable, holder-controlled credential that is auditable without surveillance.

EU Trajectory

The trajectory is set by the regulation. Member State issuance ramps through 2026 and 2027; the Large-Scale Pilots converge on general-availability deployments; the implementing acts continue to specify the operational details. The substrate adds the chain-level architectural element that the regulation's interoperability obligation effectively requires, supplied as a uniform primitive rather than as a federation of bilateral integrations. The EU eIDAS 2.0 ecosystem gains an architectural composition substrate at the moment the deployment window opens — not as a competitor to the ARF but as the load-bearing element that makes the ARF's promises hold.