TRUST · THE CLOCK
Every date on this page was set by a parliament, not by us.
There is no counter running on this page. A countdown needs a script, and the date does not need help to be true — it will still be the date tomorrow whether or not a widget ticks toward it. Read each one against your own calendar. Below the letters is the table; every row in it carries the citation that settles it.
To a government.
You are the party most of these dates actually bind, not us. The Regulation gives you a date for handing at least one wallet to every person and company in your state, and no vendor's roadmap moves that date by a single day. If you miss it, the people who lose something are your own residents, waiting in the gap between a law that already applies and a wallet that does not exist yet. We build to the wire your own reference architecture specifies, and we will keep building to whatever it specifies next — but the date is yours to hit, not ours.
To the rest of this field.
You read this page the way we do — looking for the date that forces somebody's hand. Almost none of these dates force anything on either of us: they bind governments and the narrow set of firms already required to authenticate their users strongly, and selling a compliance deadline to anyone outside that set is selling them a fear rather than a fact. We would rather lose the sale than make that pitch. If a date on this page ever does start to bind us and not you, we intend to be the ones who tell our own customers first.
To the person these deadlines are about.
Almost none of the dates below are a duty on you. Nobody can compel you to carry a wallet because a law told a government to offer you one, and nobody here is going to tell you otherwise to make a date feel more urgent than it is. If a state misses its own deadline, what you lose is a service that should have existed and did not — not a status, not a right you signed away, and not a countdown you need to beat. Read the table at your own pace. It will still be true tomorrow.
The dates themselves.
- 2024-05-20 eIDAS 2.0 — very large online platforms European Union Regulation (EU) 2024/1183, Art 5f(3)
- 2025-06-28 European Accessibility Act European Union Directive (EU) 2019/882 — Arts 2(4), 4(5), 14, 32
- 2025-07-01 EU Anti-Money Laundering Authority European Union Regulation (EU) 2024/1620, Art 108
- 2026-07-01 Australia AML/CTF Amendment Act 2024 Australia Anti-Money Laundering and Counter-Terrorism Financing Amendment Act 2024 (Cth), No. 110 of 2024, Sch. 3 incl. Pt 4 item 11; Transitional Rules F2026L00393, s.12
- 2026-09-01 UK digital verification services trust framework v1.0 — no earlier than United Kingdom DVS trust framework v1.0, finalised 9 June 2026; Data (Use and Access) Act 2025
- 2026-12-24 eIDAS 2.0 — the wallet obligation European Union Regulation (EU) 2024/1183, Art 5a(1)
- 2027-01-01 CCPA/CPRA — automated decision-making technology California, United States California Consumer Privacy Act as amended by the CPRA; CPPA regulations §§ 7155, 7157
- 2027-02-01 UK Money Laundering and Terrorist Financing (Amendment) Regulations 2026 United Kingdom SI 2026/621 — regs 20, 34A, 36(b), 37
- 2027-06-30 (a schedule, not a legal deadline) Swiss e-ID (swiyu) — trust infrastructure, expected first half of Switzerland Federal Office of Justice, revised timetable for the e-ID and the trust infrastructure, 30 June 2026
- 2027-07-10 AMLD6 — the next transposition tranche European Union Directive (EU) 2024/1640
- 2027-07-10 EU Anti-Money Laundering Regulation European Union Regulation (EU) 2024/1624, Art 90
- 2027-12-24 eIDAS 2.0 — the private-sector acceptance obligation European Union Regulation (EU) 2024/1183, Art 5f(2)
Read from _evidence.ts §3, each date carrying the citation printed beside it. Full detail on who each instrument binds is on the regulations page, not repeated here.
Why this friendliness is a position, not marketing.
Open protocols shall form the backbone of the shared digital world, developed through
inclusive processes rather than corporate fiat; technical standards shall be developed
through processes that centre the people they affect. Both sentences are this platform's own
founding document, not language written for this page, and both are scored honestly rather
than quoted for effect: the Declaration marks the first
Article partial — the open-protocol limb is real and countable, universal access
is not ours to claim — and the second not-yet, because this platform is governed
by its owner and says so plainly. Citing a founding document is easy. Meeting it is the part
that is not finished, and the register below is where that gets checked rather than asserted.
Before you go any further.
The one date on this page that touches this platform directly is the wallet obligation — and it binds member states, not the vendors building toward the wire those states will eventually specify. What that means for a person who wants a wallet today is on the register.
- PLANNED A wallet a person installs from an app store. wallet-native You cannot hold a credential on a phone you own. Everything a person would do with a proof waits behind this.
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
Straight answers.
- Why is there no countdown?
- Because a countdown is a script, and this site does not ship one to reveal content — the same rule that keeps every page readable with JavaScript off. The date does the work; the ticking would only have been decoration.
- Does any date here create a duty on you, the reader?
- No, almost never. Read the third letter above — that is the whole answer, and it is not going to change depending on how close the date gets.
- Could one of these dates be wrong?
- Yes, and it has happened before. Several rows on this page carry a correction against a date this site got wrong the first time. Some of them are recorded there.
Do not trust us. Check us.