eIDAS 2.0

Origin: composes. The European Union wrote this law. Solidus did not draft it, is not certified under it, and has no say in what it requires.

eIDAS 2.0, formally Regulation (EU) 2024/1183, is the European Union law that creates the European Digital Identity Wallet (EUDI Wallet) and requires every EU Member State to offer one to its citizens. It entered into force on 20 May 2024, amending the original 2014 eIDAS Regulation (Regulation (EU) No 910/2014), which had governed electronic identification and trust services, things like qualified electronic signatures, across the EU for a decade before this update.

What it actually requires

Three things, in plain terms:

1. Every Member State must provide at least one EUDI Wallet to its citizens, residents, and businesses, either built by the government itself, commissioned from a private party, or recognized from an existing private-sector wallet that meets the technical spec. The regulation's own text sets the deadline at 24 months after the relevant implementing acts took effect, commonly reported as around the end of 2026.
2. Large private-sector "relying parties", banks, telecoms, healthcare providers, and big online platforms among them, will eventually be legally required to accept the wallet as an authentication and identity-proofing method, roughly a year after the Member-State deadline (around 2027).
3. The technical detail is delegated, not written into the regulation's text directly. The Commission adopted a series of implementing acts that specify exactly how the wallet has to work, and those acts point to a living technical specification called the ARF (see that entry) for the actual engineering detail.

Why it matters beyond Europe

eIDAS 2.0 is the first time a jurisdiction of this size has mandated a specific technical shape for digital identity, not just "you must offer digital ID," but "it must use these credential formats, these presentation protocols, this trust model." Anyone building identity infrastructure, inside or outside the EU, now has to decide whether to target ARF conformance directly, interoperate at the standards layer without claiming conformance, or ignore it entirely. Solidus's honest answer is the second one.

Solidus's actual relationship to it

Solidus is not an EUDI Wallet, is not a notified Member-State PID provider, and has never gone through an eIDAS conformance assessment: there is nothing to claim here and no shortcut around that. What is true, and narrower: Solidus independently adopted several of the same open standards the regulation's implementing acts point to, OpenID4VCI for issuance, OpenID4VP for presentation, SD-JWT VC as a credential format, W3C DID Core and VC Data Model 2.0 underneath all of it, and has them running on its public testnet today. That overlap exists because Solidus built its own KYC-credential product on the same standards ecosystem the EU chose, not because Solidus passed any EU process. "Uses the same building blocks" and "is certified under the law" are two structurally different claims, and only the first one is true here.

Check it yourself

The regulation's text is public at eur-lex.europa.eu/eli/reg/2024/1183/oj. For the standard-by-standard breakdown of what Solidus has and hasn't shipped against the technical spec this regulation delegates to, see the EUDI ARF mapping, read it as a gap list, not a conformance claim.