eIDAS 1.0 vs eIDAS 2.0

← Trust frameworks

eIDAS (electronic IDentification, Authentication and trust Services) is the EU regulation that establishes a common legal framework for electronic identity and trust services across Member States. Two regulatory generations are now in force, and they apply to digital credentials differently.

eIDAS 1.0 (Regulation (EU) 910/2014)

Adopted in 2014, in force since 2016. Covers three trust service levels for electronic signatures (simple, advanced, qualified) and the same three levels for electronic seals (the organisational equivalent). Qualified Trust Service Providers (QTSPs) are accredited at national level and listed on the EU LOTL.

Notified eID schemes provide cross-border mutual recognition for access to public services, but do not cover attribute attestation — there is no eIDAS 1.0 concept of a “verifiable credential” issued to a citizen wallet.

Trust services in scope: electronic signatures, electronic seals, electronic timestamps, electronic registered delivery, website authentication (QWAC).

eIDAS 2.0 (Regulation (EU) 2024/1183)

Adopted in 2024, with the rollout of Member-State-issued EUDI Wallets scheduled for 2026. Introduces the legal categories Qualified Electronic Attestation of Attributes (QEAA), Public-body Electronic Attestation of Attributes (PubEAA), and regular Electronic Attestation of Attributes (EAA).

Every Member State MUST issue at least one EUDI Wallet (Article 5a(1)) within 24 months of the entry into force of the implementing acts that the Article refers to. The first of those acts entered into force on 24 December 2024, so the deadline is 24 December 2026. All MS wallets are designed to be accepted across Member States, mediated by the wallet trust framework rather than bilateral agreements.

The wallet is the citizen-facing entry point to the trust framework. The same wallet holds the citizen’s PID (Person Identification Data) and any number of QEAAs, PubEAAs and EAAs issued by accredited parties.

The three tiers of attestation

eIDAS 2.0 defines three legal categories of Electronic Attestation of Attributes, with distinct issuer requirements and legal effects:

TierIssuerLegal effectIn trusted list?
QEAA (Art. 45g)Qualified TSP (QTSP)Equivalent to a lawfully issued paper attestation of attributesYes — LOTL + national TSL
PubEAAPublic sector body (or on its behalf)Equivalent to QEAA when conditions met; cross-border recognitionYes — national trusted list
EAA (Art. 45f)Any TSP (non-qualified allowed)“Shall not be denied” admissibility and cross-border recognition; no presumption of validityNot required

The non-discrimination clause (Article 45f) is the mechanism that gives even non-qualified EAAs a cross-border legal floor:

An electronic attestation of attributes shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements of qualified electronic attestations of attributes.

Regulation (EU) 2024/1183, Article 45f

A credential issued by a TSP that is not in the national QTSP list cannot be dismissed just because it is non-qualified or because it is electronic. But a non-qualified EAA does not carry the equivalence to paper that QEAA grants under Article 45g, nor the presumption of validity that QEAA/PubEAA enjoy. The tier matters for the use case: formal recognition workflows benefit from qualified or public-body attestations, although eIDAS 2.0 does not itself mandate a category for diplomas; microcredentials from private providers, corporate CPD, and informal recognition can use EAA with legal admissibility but without full legal effect. See the Trust spectrum for how these tiers map to concrete credential formats.

What eIDAS 2.0 asks of the credential format

Most of eIDAS 2.0 is about institutions, trust lists and legal categories. One provision reaches down into the credential format itself. Article 5a(16) of Regulation (EU) 2024/1183 sets two requirements for the wallet’s technical framework. Point (a): after issuance, neither the attestation provider nor any other party may obtain data that lets transactions or user behaviour be tracked, linked or correlated, unless the user explicitly authorises it. Point (b): the framework must enable privacy-preserving techniques that ensure unlinkability where the attestation does not require identifying the user. The target is unlinkability, not merely selective disclosure; and where a presentation must identify the holder, as many degree checks do, point (a) carries the weight.

Unlinkability is not the same as selective disclosure. Selective disclosure lets the holder reveal only some attributes, for example a degree without a date of birth. But if every presentation carries the same signature or the same hashes, those values act as a persistent identifier, and verifiers comparing notes can still follow the holder. A format can offer perfect selective disclosure and remain fully linkable, so selective disclosure alone does not meet the requirement.

The two credential stacks handle this differently: W3C-VC secured with the bbs-2023 cryptosuite produces a fresh, uncorrelatable proof for each presentation (status-list indices and identifiers must still be designed not to correlate), while SD-JWT approximates unlinkability through batch issuance, with known limits. See Selective disclosure vs unlinkability for the detail, and Choosing a stack for how this weighs in the choice of format for different credential types.

What changes for credentials

AspecteIDAS 1.0eIDAS 2.0
IdentityNotified eID schemesEUDI Wallet (mandatory)
Attribute attestationNot in scopeQEAA / PubEAA / EAA
Credential storageN/AWallet-native
Trust anchorsNational TSL + LOTLNational TSL + LOTL + Wallet Trust Anchor
Citizen-mediated flowFederated SAML/OIDCWallet-mediated (LE→NP→LE)
Educational credentialsEuropass / EDCI lineageEUDI Wallet attestations (SD-JWT VC, mdoc); DC4EU / EBSI lineage piloted until 2025

Citizen-mediated trust (LE→NP→LE) only becomes legally viable with eIDAS 2.0.

Before 2024, an EU-wide wallet-based recognition workflow had no regulatory basis. After 2024, it does.

The two EDC lineages map only loosely to the two regulations. Europass / EDCI uses eIDAS 1.0 qualified seals. The DC4EU / EBSI lineage, piloted until 2025, is built on W3C VCDM, which is not yet a binding EUDI Wallet format. Since Implementing Regulation (EU) 2026/1731 (in force 11 August 2026), the binding annexes of the EUDI Wallet implementing acts name SD-JWT VC and ISO/IEC mdoc for person identification data and for attestations (ETSI TS 119 472-1 profiles). W3C VCDM is not among them today, but the regulation’s recitals state that wallets should also support it, as the reference format for attestations in education, once new W3C VCDM profiles are available. ARF v3.0 currently treats W3C VCDM as optional and for non-qualified attestations only, so a qualified or public-body credential in the wallet would today travel as SD-JWT VC or mdoc. See EUDI Wallet and European Digital Credentials.

← Trust spectrum  ·  Trust frameworks  ·  EUDI Wallet ARF →