3 ms·
What would you do with <UUID>? How would you verify that you are actually <UUID> or 18 years old?
by delusional 1y ago
What would you do with <UUID>? How would you verify that you are actually <UUID> or 18 years old?
- Tadpole9181 1y agoZero knowledge proofs from a provider who has your ID allows validation without data leaking. Though creates other issues with, i.e. selling validation tokens.
- delusional 1y agoWhat I'm gathering from that description is a flow that would involve three parties: Me, the restricted resource, and an ID validator. When I wanted to access the restricted resource, they'd ask for a valid token that I would then go to my ID validator to get since they've already identified me, they'd then pass that valid token back to me which I could pass to the restricted resource. They'd presumably then save that token as proof that they did their legally required validation. Is that roughly correct? I think that's the model they're working on in the EU using Bitstring Status List, OpenID for Verifiable Presentations, and ISO 18013-5. If you want to know more there's a reference implementation: https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework https://github.com/eu-digital-identity-wallet/eudi-doc-archi...
- Tadpole9181 1y agoJust about, yup! I don't know about your specific link there, but the "zero knowledge" part comes from the token sent to the provider being non-reversible. A token cannot be used to identify the person who generated the token, even by ID validator. This works because the token is just used as material in (simplified) a hash function.