Re: No Phone Home statement by ACLU, EFF, Brave, CDT, etc. from Matteo Frigo on 2025-06-05 (public-credentials@w3.org from June 2025)

Received on Thursday, 5 June 2025 14:20:14 UTC This archive was generated by hypermail 3.0.0: Thursday, 5 June 2025 14:20:15 UTC

Good point. Our paper is really about how to implement a ZK presentation of the existing MDOC flow, but other possibilities exist. Hopefully the next few paragraphs will clarify what I have in mind. Let's agree that server retrieval is a bad idea, and let's work in a world where server retrieval is removed from the MDOC standard. I claim that a sufficiently evil issuer can still communicate information to the relying party even without server retrieval, and that this problem is not MDOC-specific (SD-JWT would have the same problem). All that is needed is some sort of steganographic channel…

related reading

• Zero Knowledge Proofs: An illustrated primer – A Few Thoughts on Cryptographic Engineeringblog.cryptographyengineering.com
• thesis.pdfaayushg.com
• 0xPARC0xparc.org
• ZK-Friendly Hash Functions | Zellic — Researchzellic.io
• Zero-knowledge proof - Wikipediaen.wikipedia.org
• 2010.pdfeprint.iacr.org
• Aleo: Can You Keep a Secret?notboring.co
• Topic G - Zero Knowledge Proof · eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework · Discussion #408 · GitHubgithub.com
• eudi-doc-architecture-and-reference-framework/docs/discussion-topics/g-zero-knowledge-proof.md at main · eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework · GitHubgithub.com
• STARK-paper.pdfstarkware.co
• Thinking in Zero Knowledge — yush_gmirror.xyz
• eudi-doc-standards-and-technical-specifications/docs/technical-specifications/ts4-zkp.md at main · eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications · GitHubgithub.com