W3C home > Mailing lists > Public > public-credentials@w3.org > May 2022

Re: [EXTERNAL] [jfraichot@learningmachine.com] Re: Universal signature verifier

From: Markus Sabadello <markus@danubetech.com>
Date: Thu, 5 May 2022 22:59:22 +0200
Message-ID: <e445532e-689e-91dd-69f4-d5090b205a9b@danubetech.com>
To: public-credentials@w3.org
Hello Julien,

Our verifier can be extended in some ways (adding proof types, 
revocation mechanisms, etc.), but it doesn't really have the same 
modular architecture as the Universal Resolver.
To be transparent, our verifier is just one out of many in the 
community, probably even less advanced than other implementations out 
there; and it's a proprietary product, not an open-source project.
Even if we made it open-source, I think it would be quite an effort to 
transform it into the kind of community-driven project you are envisioning.

But I really like the general idea..

Some of the libraries we use in our verifier are open-source, see here:
https://gitlab.grnet.gr/essif-lab/infrastructure_2/danubetech/SSI_Java_Libraries_project_summary

Markus

On 05.05.22 14:30, Julien Fraichot wrote:
>
> Thanks Markus,
>
> Yeah I expect it couldn’t be a one man/team job to maintain all the 
> various options, which is why I was thinking something along the lines 
> of the Universal Did Resolver, where implementers would add their own 
> driver. For instance, I don’t believe MerkleProof2019 is widely used, 
> but having such a universal verifier would allow more systems to 
> support seamlessly verification for Blockcerts’ implementation of 
> Verifiable Credentials. Conversely (and this is where it interests 
> me), our wallet could support a broader range of Verifiable 
> Credentials if I didn’t have to deterministically decide which 
> verification suites to support.
>
> Is your verifier working in such a way? Is it open source?
>
> *From: *Markus Sabadello <markus@danubetech.com>
> *Date: *Wednesday, 4 May 2022 at 14:55
> *To: *public-credentials@w3.org <public-credentials@w3.org>
> *Subject: *[EXTERNAL] [jfraichot@learningmachine.com] Re: Universal 
> signature verifier
>
> *CAUTION: *This email originated from outside of Hyland. Do not click 
> links or open attachments unless you recognize the sender and know the 
> content is safe.
>
> Hello Julien,
>
> We (Danube Tech) have a "Universal Verifier" here:
> https://univerifier.io/
>
> But I don't claim that it actually supports all the credential formats 
> and signature suites in existence...
>
> Especially considering that at the last Internet Identity Workshop a 
> lot of different formats were identified:
> https://docs.google.com/document/d/1aNHvPhFv85HHlG8Ry2etrw15KdY830oAL804rMFY9bY/
>
> all the best,
> Markus
>
> On 04.05.22 20:01, Julien Fraichot wrote:
>
>     Hi,
>
>     I am wondering if similar to the Universal DID Resolver, a
>     Universal Signature Verifier exists?
>
>     In my ideal world it’d be a service to which we can send a VC, and
>     where the pipeline decides to which Verification Suite to address
>     that document. Again, ideally most or all of the signature suites
>     defined here could be verifiable:
>     https://w3c-ccg.github.io/security-vocab
>
>     Maybe this is pretty naïve but it feels that way we could better
>     support the various signing possibilities, and would alleviate
>     having to integrate deterministically verification suites into our
>     various project specific libraries, or having to inject them for
>     verification (/a la/ vc.js).
>
>     --
>
>     Julien Fraichot
>
>     Developer – Hyland Credentials
>
>     ----------------------------------------- Please consider the
>     environment before printing this e-mail
>     -----------------------------------------
>
>     CONFIDENTIALITY NOTICE: This message and any attached documents
>     may contain confidential information from Hyland Software, Inc.
>     The information is intended only for the use of the individual or
>     entity named above. If the reader of this message is not the
>     intended recipient, or an employee or agent responsible for the
>     delivery of this message to the intended recipient, the reader is
>     hereby notified that any dissemination, distribution or copying of
>     this message or of any attached documents, or the taking of any
>     action or omission to take any action in reliance on the contents
>     of this message or of any attached documents, is strictly
>     prohibited. If you have received this communication in error,
>     please notify the sender immediately by e-mail or telephone, at +1
>     (440) 788-5000, and delete the original message immediately. Thank
>     you.
>
> ----------------------------------------- Please consider the 
> environment before printing this e-mail 
> -----------------------------------------
>
> CONFIDENTIALITY NOTICE: This message and any attached documents may 
> contain confidential information from Hyland Software, Inc. The 
> information is intended only for the use of the individual or entity 
> named above. If the reader of this message is not the intended 
> recipient, or an employee or agent responsible for the delivery of 
> this message to the intended recipient, the reader is hereby notified 
> that any dissemination, distribution or copying of this message or of 
> any attached documents, or the taking of any action or omission to 
> take any action in reliance on the contents of this message or of any 
> attached documents, is strictly prohibited. If you have received this 
> communication in error, please notify the sender immediately by e-mail 
> or telephone, at +1 (440) 788-5000, and delete the original message 
> immediately. Thank you.
Received on Thursday, 5 May 2022 20:59:37 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 5 May 2022 20:59:38 UTC