- From: Wayne Chang <wyc@fastmail.fm>
- Date: Wed, 10 Jun 2020 19:50:16 -0400
- To: "Nikos Fotiou" <fotiou@aueb.gr>, "W3C Credentials CG" <public-credentials@w3.org>
Received on Wednesday, 10 June 2020 23:50:42 UTC
Hey Nikos, thanks for sharing the idea. This is one of those questions where you'd probably need to specify the exact data structures and algorithms to make sure no one is misinterpreting your steps. By "verifiable representation" did you mean verifiable presentation, or is that something specific to your use case? In general it sounds like instead of putting the data directly into the VC, you'd like to put a reference to that data instead. Then, a verifier who can also access the data can check that the issuer authorized certain actions or statements related to that data. How close is this? Some examples would certainly help. Best, - Wayne On Wed, Jun 10, 2020, at 7:39 PM, Nikos Fotiou wrote: > > Hi, > We were thinking about VCs that support selective disclosure of claims without ZKP (we do not care about unlikability). A trivial approach that came up is the following: the issuer organizes all claims in a Merkle tree, includes the root of the Merkle tree (only) in the VC, and sends the VC and the tree to the holder. Then, the holder can include the VC and the corresponding Merkle membership proof in the verifiable representation. > > Does this sound reasonable? > > Best, > Nikos >
Received on Wednesday, 10 June 2020 23:50:42 UTC