av-doc-technical-specification

https://github.com/eu-digital-identity-wallet/av-doc-technic... https://www.forbes.com/sites/federicoguerrini/2025/08/10/who...

https://github.com/eu-digital-identity-wallet/av-doc-technic... > Since Proof of Age Attestations are designed for single use, the system must support the issuance of attestations in batches. It is recommended that each batch consist of thirty (30) attestations. It sounds like application would request batch of time-limited proofs from government server. Proofs gets burned after single use. Whether or not you've used any, app just requests another batch at a set interval (e.g. 30 once a month). So you're rate limited on the backend. Edit: seems like issuing proofs is not limited to the government, e.g. banks you're client of also can supply you with proofs? (if they want to partake for some reason). I guess that would multiply numbers of proof available to you.

The EU Digital Identity Wallet isn't zero knowledge. I mean it's just not. It relies on Google Play Integrity Attestation on Android and the iOS equivalent on Apple devices because those give it a revocation mechanism, and those aren't zero knowledge. https://github.com/eu-digital-identity-wallet/av-doc-technic... It says that it wants to be zero knowledge, but it has no zero knowledge implementation and no plan of how it even possibly could be zero knowledge, and it never will precisely because that is incompatible with the revocation requirements set down by the EU.