- From: Brent Zundel <brent.zundel@evernym.com>
- Date: Mon, 6 Apr 2020 10:10:26 -0600
- To: Kyle Den Hartog <kyle.denhartog@mattr.global>
- Cc: W3C Verifiable Credentials Working Group <public-vc-wg@w3.org>
- Message-ID: <CAHR74YX-THPggwMbN2yWbfBwDOSObB+WrQ8rk7pvSNZ=h+OT=w@mail.gmail.com>
If I recall correctly, the idea was that you could have a VC signed with a ZKP signature encoded as JSON, which is then encoded as a JWT. I think it would be roughly equivalent to having a ZKP VC as a payload on a JWT encoded message, so I'm not sure if I'm right here. Oliver Terbu may have more information on this. On Tue, Mar 31, 2020 at 7:29 PM Kyle Den Hartog <kyle.denhartog@mattr.global> wrote: > I was looking at the implementation guide and it says that JSON+JWTs can > support ZKPs. I interpret this to mean that it can support attribute based > credentials where I can sign attributes individually. As far as I know, > there's no registered algorithms in JOSE registries that support ZKPs. > Additionally, when I looked into this as well, I couldn't figure out a way > to do this because the payload and headers have to be concatenated and > base64url encoded, meaning you can't individually sign attributes. If I'm > overlooking something though I'd appreciate being corrected. Even better if > someone has an implementation of this working available, I'd love to learn > from it. > > Thanks, > Kyle > > This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. > >
Received on Monday, 6 April 2020 16:11:17 UTC