DEV Community

Cover image for The EU KIDS Act Says Every Age Check "Shall Be Zero Knowledge Proof". What That Means If You Build Age Verifiers
eidas-pro for eidas-pro

Posted on Originally published at eidas-pro.com

The EU KIDS Act Says Every Age Check "Shall Be Zero Knowledge Proof". What That Means If You Build Age Verifiers

Cross-post note (remove before publishing): check that cover_image loads, keep canonical_url pointing at the eidas-pro.com post, then set published: true.

One sentence in a new EU proposal matters to anyone who writes age-verification code:

"Any age assurance measure shall be zero knowledge proof."

That is Article 28(3) of the proposed EU KIDS Act (COM(2026) 681), adopted by the European Commission on 17 September 2026. It is a proposal: Parliament and Council still have to agree on a text, and most of it would apply six months after entry into force. Nothing changes this year. But if you build verifiers, the direction is worth understanding now.

What the age-assurance chapter asks for

Chapter V (Articles 26 to 32) is short. The parts that matter to developers:

  • No identification (Art. 28(1)). An age-assurance solution "shall not enable the identification of the recipient nor locate, track, target, advertise to or profile recipients for any purpose."
  • Zero knowledge (Art. 28(3)). The sentence above. It applies to providers "and any entity acting on behalf or together with such providers", so a hosted verifier is in scope, not just the platform that calls it.
  • One route for social-media sign-ups (Art. 29(2)). To enforce the minimum age of 15, platforms must rely exclusively on a certified EU age verification solution using an EU proof of age attestation, provided by an independent third party. ID scans and face-based age estimation would not count there.
  • Other methods elsewhere (Art. 29(4)). For other duties, providers may use other solutions, if those meet Articles 27 and 28, the zero-knowledge sentence included.
  • Machine-readable lists (Art. 30(1)). The Commission would publish lists of certified proof-of-age attestation providers and of certified EU age verification solutions.

The catch: "zero knowledge proof" is never defined

The proposal does not define the term. On 12 November the European Data Protection Supervisor (Opinion 36/2026) "very much welcomes" the requirement and asks for a definition in Article 3: a proof should show the statement (for example "over 18") and nothing more.

That definition decides whether what ships today passes.

What a verifier receives today

The EU Age Verification app presents a Proof of Age attestation as an ISO/IEC 18013-5 mdoc (CBOR). Its docType and namespace are both eu.europa.ec.av.1. For an 18+ check the verifier asks for one element and gets back:

  • age_over_18: true, an issuer-signed boolean, revealed by selective disclosure;
  • the issuer's signed Mobile Security Object (MSO), which holds digests of the elements and the device key;
  • a device signature over the session, which binds the presentation to the holder's device and to this request.

The verifier checks the issuer signature, matches the disclosed element against its digest, verifies the device signature, and checks that the issuer's certificate chains to an entry on the EU Age Verification trusted list.

This is data-minimal: no name, no birth date, no document number. It is not a zero-knowledge proof in the strict cryptographic sense. The verifier sees concrete signatures and a concrete device public key. The issuer mitigates linkability by issuing attestations in batches for single use, but the bytes themselves are not unlinkable.

What a ZK presentation changes

With a zero-knowledge presentation, the holder's device proves a statement such as "I hold an mdoc, signed by a key on the trusted list, whose age_over_18 element is true, and I control its device key", without revealing the issuer signature, the MSO or the device key. Two presentations of the same credential then look unrelated.

Google's open-source Longfellow ZK library is one implementation of this for ECDSA-signed mdocs. The EU age-verification reference work is preparing ZK presentations, but they are not what the app sends by default today.

What to plan for as a verifier developer

  1. Build around refreshable, machine-readable trust lists. Art. 30(1) formalises what already exists for proof-of-age issuers. Today's production EU Age Verification trusted list, reissued on 5 November 2026, names one issuer: Denmark's Agency for Digital Government (AltID). Its next scheduled update is 28 April 2027. Load it, verify its signature, refresh it, and fail closed when it cannot be read.
  2. Keep the presentation format pluggable. Your verifier will likely need to accept plain mdoc presentations and ZK proofs side by side for a while, over OpenID4VP and the W3C Digital Credentials API. Separate "who is trusted" (trust lists) from "how the proof is checked" (mdoc signatures today, a ZK verifier tomorrow).
  3. Expect certification questions. The text does not say whether a hosted verifier serving many platforms must be certified as an "EU age verification solution" itself. The implementing acts under Art. 30(2) that would answer it do not exist yet.
  4. Comment while you can. The Commission's Have Your Say page for the proposal takes feedback; the Commission's press release gives 26 November 2026 as the closing date (the portal shows 3 December, so plan for the earlier date). Useful points from a builder's view: define ZKP, describe a certification route that small vendors can afford, and adopt the implementing acts well before the obligations apply.

Where we stand

At eIDAS Pro we verify the EU proof-of-age attestation from the EU Age Verification app today, over av:// links and the Digital Credentials API, tested end to end with the EU reference app. Those presentations are the plain mdoc kind described above. Verifying zero-knowledge age proofs is on our roadmap for Q1 2027; it is not available today.

The full post, with the Parliament timeline, the EDPS and NGO positions and what it means for webshops, is on our blog: The EU KIDS Act Wants Zero-Knowledge Age Checks. Here Is Where the Real Debate Is.

The EU KIDS Act is a Commission proposal and may change substantially. This is technical information, not legal advice.

Top comments (0)