- From: Adrian Gropper <agropper@healthurl.com>
- Date: Mon, 26 Sep 2022 16:32:02 +0200
- To: Snorre Lothar von Gohren Edwin <snorre@diwala.io>
- Cc: "John, Anil" <anil.john@hq.dhs.gov>, W3C Credentials Community Group <public-credentials@w3.org>
- Message-ID: <CANYRo8i6LEg7ykGgJ9nGf-mq8mcKyYQY6A=pgcG+WpELa8dyEg@mail.gmail.com>
There’s a world of difference between a user’s generic wallet and that user’s client. The wallet tends to be a hardware security module often with a biometric component and some payment features. All of this is generic to any use-case and does not benefit much from domain-specific verifiable credentials (education, healthcare, transport, etc…). The user’s client is the entity that can add value to interaction with issuers and verifiers as servers. There could be different clients for education, healthcare, transport, etc.. and each could store or access some or all of a user’s VCs regardless of which wallet is being used to authenticate and sign an issue or presentation. This perspective does not preclude clients that include an (otherwise generic) wallet functionality. It does require that these integrated wallet+client expose a standardized API at their wallet-client interface so that users are not locked-in. Adrian On Mon, Sep 26, 2022 at 3:51 PM Snorre Lothar von Gohren Edwin < snorre@diwala.io> wrote: > > > On Fri, Sep 23, 2022 at 2:58 AM John, Anil <anil.john@hq.dhs.gov> wrote: > >> >> >>How wallets can signal intent and capability to an Issuer and Verifier >> such that they can make a risk-based decision to interact with that wallet >> >> >>I would like to better understand what you mean. Is this about metadata >> (capabilties) or risk signals? >> >> >> >> Wallet to Issuer >> >> - I support FIPS compliant cryptography >> - I support storage of data in a hardware element >> - I can dance under the pale moonlight but not in sunlight >> >> >> >> Wallet to Verifier >> >> - I support selective disclosure capability Y >> - I support credential aggregation capabilities >> - And so on … >> >> >> >> Best Regards, >> >> >> >> Anil >> >> >> > > > What Anil talks about here is something that fits very well into this RWoT > advanced reading: > https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/discovery-handshake.md > > > > -- > > *Snorre Lothar von Gohren Edwin* > Co-Founder & CTO, Diwala > +47 411 611 94 > www.diwala.io > <https://streaklinks.com/BN225CWHB2FziTYaxQzXhRKo/http%3A%2F%2Fwww.diwala.io%2F> > <http://www.diwala.io/> > *Stay on top of Diwala news on social media! **Facebook > <https://streaklinks.com/BN225CSJycgec4gkDQHavtQj/https%3A%2F%2Fwww.facebook.com%2Fdiwalaorg>* > * / **LinkedIn > <https://streaklinks.com/BN225DrrK6MhRwMQ0ATUuqo_/https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fdiwala>* > * / **Instagram > <https://streaklinks.com/BN225CSu7jvCHcEJiQuxVE0C/https%3A%2F%2Fwww.instagram.com%2Fdiwala_%2F>* > * / **Twitter > <https://streaklinks.com/BN225CeFhaqKZZ-hpQWKUxo5/https%3A%2F%2Ftwitter.com%2FDiwala>* > ᐧ >
Received on Monday, 26 September 2022 14:32:25 UTC