RESEARCH SNAPSHOT — MEASURED 5 AUGUST 2026. A dated record; the registers it describes are expected to change.

The certification asymmetry

eIDAS 2.0 certifies one side of the wallet trust boundary and merely registers the other. Snapshot of both halves, measured 5 August 2026. Every claim below was fetched and re-verified that day.

1 · What the Regulation demands

Wallets

Art. 5c(1), Reg. (EU) 2024/1183

Certification by conformity assessment bodies; Member States notify the Commission of every certified wallet (Art. 5d).

Relying parties (verifiers)

Art. 5b(1)–(2)

Registration of a name, registration number, contact details and intended use. No conformity assessment. There is no Art. 5c equivalent for the verifying side.

2 · What the Commission's own trust hub publishes today

eidas.ec.europa.eu/efda/wallet — six "Lists of trusted entities". Its API answers checkIfListIsPublished = false for all six; all six machine-readable JSON endpoints return 403.

Wallet ProvidersNOT PUBLISHED
PID ProvidersNOT PUBLISHED
WRPAC ProvidersNOT PUBLISHED
Registrars & RegistersNOT PUBLISHED
mDL ProvidersNOT PUBLISHED
Pub-EAA ProvidersNOT PUBLISHED
Certified wallets: zero. No EUDI Wallet has completed Art. 5c certification (the ENISA candidate certification scheme was in public consultation until 30 April 2026). The list machinery exists — CIR (EU) 2025/849 obliges the Commission to publish and maintain the list in machine-readable form — but no OJ notice has appeared.

3 · Relying-party registers, member state by member state

WhereLive register?Verified state, 05.08.2026
EU aggregationNO Canonical list URL declared by the dashboard config; returns 403, list unpublished.
EstoniaNO RIA: RP-register MVP planned "end of 2026 or beginning of 2027"; registration begins after the MVP; access-certificate solution still in development. Wallet itself at tender stage (announced 18 May 2026).
GermanyNO Official FAQ: public "transparency register" planned ("registered organizations and use cases can be viewed in a public overview") plus an "EUDI Wallet Hub DE" portal; details "currently being worked out"; wallet expected from early 2027.
NetherlandsNO VNG still "examining how the relying-party register should look"; acceptance obligation for (semi-)public providers expected ~20 Nov 2026. developer.overheid.nl has no RP-registration section at all.
ItalyNO* AgID accreditation framework for IT-Wallet exists under national law (CAD Art. 64-quater) — distinct from the Art. 5b register; no public elenco of relying parties found (*search-level evidence only).

4 · The clock that is already running

6 May 2025 — CIR (EU) 2025/848 and 2025/849 adopted: the rulebooks for RP registration and for the certified-wallet list.
5 Aug 2026 (today) — both halves at zero: six trust-hub lists live, none published; no national RP register operational.
24 Dec 2026 — CIR 2025/848 applies: national RP registers must expose a public website and REST API with JWS-signed data. Public fields include the RP's identifiers, entitlements, intermediary status and — per intended use — the list of data it intends to request. From this date, "what do relying parties actually ask for" becomes a mechanically measurable question.
Honest boundary. Absence of a live register is not absence of preparation — Estonia, Germany and the Netherlands all publish dated plans. And a library-level finding about verifier behaviour says nothing about any deployed relying party. The claim this page supports is narrower and legal-empirical: where the Regulation places assurance and where it does not — and that, mid-2026, neither published list yet constrains anyone.

Method & sources (all fetched 2026-08-05; re-verification = re-fetch the same URLs): EUR-Lex Reg. (EU) 2024/1183 Art. 5b/5c/5d (verified 2026-08-04 in-browser); eidas.ec.europa.eu/efda/wallet + its checkIfListIsPublished API ×6 + trust.tech.ec.europa.eu/lists/eudiw/*.json ×6 (403); ria.ee EUDI-wallet page (upd. 22.07.2026); eudi-wallet.gov.de/en/faq; yivi.app (29.06.2026) + developer.overheid.nl. CIR 2025/848 / 2025/849 details cross-checked in three secondary sources — re-pull the OJ texts from EUR-Lex before citing in a manuscript (EUR-Lex was bot-walled for the automated check).

Tyche Institute · research demonstrator prototype · single file, no external requests.