ComparisonEU

EU eIDAS eIDAS 2.0 vs eIDAS

eIDAS 2.0 introduces the EUDI Wallet and reshapes relying party and attribute ecosystems.

Use this page to plan what to build and what evidence you'll need.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 21, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 21, 2026

Overview

eIDAS (Regulation (EU) No 910/2014) established EU trust services and cross-border eID recognition. The amended framework, as changed by Regulation (EU) 2024/1183 and corrected on 9 April 2025, keeps that foundation but expands the system in two important ways: it introduces European Digital Identity Wallets and it expands the trust-service perimeter to cover electronic attestations of attributes, electronic archiving, electronic ledgers, and management of remote electronic signature and seal creation devices. The practical takeaway is that many organizations now need new wallet-compatible flows, expanded trust-service scoping, and a stronger evidence program.

Section 1

What stayed the same (the eIDAS foundation still matters)

Trust services remain core: electronic signatures, seals, timestamps, registered delivery, website authentication, and supervision of qualified trust services.

If you already rely on qualified trust services (e.g., QES), you still need strong QTSP due diligence, evidence retention, and lifecycle governance.

Trust service categories and legal effects remain foundational for cross-border digital transactions.
Supervision and audit expectations for QTSPs remain central for high-assurance use cases.
Standards alignment, including ETSI signature, certificate, and policy profiles, still matters for interoperability.

Section 2

What changed (EUDI Wallet + attribute ecosystems)

The amended framework adds wallet-centric capabilities and responsibilities, including wallet providers, relying-party acceptance concepts, and attribute issuance or verification pipelines.

It also extends the trust-service perimeter. eIDAS is no longer only about signatures, seals, timestamps, delivery, and website authentication.

EUDI Wallet: identity and attribute container with security, certification, and user-transparency expectations, including transaction logs.
Electronic attestations of attributes: a new attribute layer that relying parties can request and verify with user-controlled disclosure.
Expanded trust services: electronic archiving, electronic ledgers, and management of remote electronic signature and seal creation devices.
Implementation layer: the Commission adopted five wallet implementing regulations in late 2024 to define core functionalities, interfaces, PID and attributes, certification, and ecosystem notifications.

Section 3

Operational impacts for relying parties

If you authenticate users or rely on identity attributes, EUDI Wallet can become a new channel that must be integrated with privacy and security guardrails.

Relying party readiness is not only technical: it affects product UX, data governance, and incident handling.

Acceptance planning: decide which journeys will support wallet-based authentication first and define safe fallback paths.
Verification pipeline: implement deterministic verification, revocation or status checks, and decision logs for wallets, signatures, and attribute attestations.
Data minimization and transparency: enforce minimal-attribute requests and provide clear user-facing explanations.
Roadmap timing: plan around the end-2026 wallet rollout and the late-2024 implementing acts rather than treating eIDAS 2.0 as a distant concept.

Section 4

Program strategy (build once, generate many evidence views)

Do not build eIDAS compliance and wallet integration as separate programs. Build one identity and trust program with reusable evidence.

Treat outputs as living artifacts: policies, architecture decisions, test results, conformity evidence, supervisory correspondence, and operational logs.

Control system: trust services governance + wallet flow controls + verification logging + change management.
Evidence system: a single evidence index that supports audits, regulators, and partner due diligence.
Testing cadence: interoperability tests + negative tests + operational drills (revocations, issuer key rotations).

Recommended next step

Use EU eIDAS eIDAS 2.0 vs eIDAS as a cited research workflow

Research Copilot can take EU eIDAS eIDAS 2.0 vs eIDAS from how this topic compares with adjacent regulations or standards to a reusable workflow inside Sorena. Teams working on EU eIDAS can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Research workflow

Open Research Copilot for EU eIDAS eIDAS 2.0 vs eIDAS

Start from EU eIDAS eIDAS 2.0 vs eIDAS and answer scope, timing, and interpretation questions with cited outputs.

Explore next step

Talk to Sorena

Talk through EU eIDAS

Review your current process, evidence gaps, and next steps for EU eIDAS eIDAS 2.0 vs eIDAS.

Explore next step

Primary sources