- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sat, 12 Aug 2023 12:37:02 -0400
- To: Orie Steele <orie@transmute.industries>
- Cc: Ganesh Annan <gannan@digitalbazaar.com>, W3C Credentials CG <public-credentials@w3.org>
On Tue, Aug 8, 2023 at 12:30 PM Orie Steele <orie@transmute.industries> wrote: > Last time I checked the chapi demo site required the wallet to implement both DID Auth with Verifiable Presentations and Ed25519Signature2020, is that still the case? DID Auth has always been optional in the CHAPI Playground, you can turn the requirement to do it on and off in the CHAPI UI based on the workflow that you want to demonstrate. Verifying the DID Auth happens using whatever verifier back-end you pick in the CHAPI Playground. For example, if you select the verifier that's built into the website, it currently accepts Ed25519Signature2018, Ed25519Signature2020, and eddsa-2022. We plan to add all of the cryptosuites that are going through standardization at W3C in time. We are also reaching out to the 9+ verifiers listed here as well to integrate them, and so verification will support whatever cryptosuites they support as well: https://w3c-ccg.github.io/vc-api-verifier-test-suite/#Verify%20Credential%20-%20Data%20Integrity In other words, the CHAPI Playground DID Auth and Data Integrity cryptosuites are only limited by whatever cryptosuites the integrated issuers and verifiers have implemented. The vast majority of them have implemented Ed25519Signature2020 at this point in time, and based on our discussions with them, are going to transition to the W3C Data Integrity cryptosuites when those enter the Candidate Recommendation phase at W3C (within the next couple of months). -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Saturday, 12 August 2023 16:37:43 UTC