W3C home > Mailing lists > Public > public-credentials@w3.org > March 2023

Re: CHAPI Playground's Latest Update - Verification Workflows

From: Ganesh Annan <gannan@digitalbazaar.com>
Date: Tue, 14 Mar 2023 12:21:43 -0400
Message-ID: <CALd_6=v5+YZpy0wUqGJRR4upVEoBXJMOXWMxdqFbW=9jeE9+hg@mail.gmail.com>
To: Orie Steele <orie@transmute.industries>
Cc: W3C Credentials CG <public-credentials@w3.org>
What Brian said is correct. The signed presentations can be viewed using
the JSON viewer on the Playground.

The VC API is the critical piece of software that standardizes the VC
Issuance and Verification APIs. This allowed the playground to seamlessly
connect to multiple Issuer Backends and the same will hold true for the
Verifier Backends.

On Fri, Mar 10, 2023 at 4:15 PM Orie Steele <orie@transmute.industries>
wrote:

> Can you talk about how the vc-api is useful or not useful, for
> implementers wishing to support these CHAPI flows?
>
> Specifically interested in the presentation to a verifier side.
>
> https://w3c-ccg.github.io/vc-api/#presenting
>
> Are any of the presentations in the CHAPI examples "authenticated" ?
>
> Or are they all "VerifiablePresentations" but without a "proof" ?
>
> Regards,
>
> OS
>
>
> On Fri, Mar 10, 2023 at 11:57 AM Ganesh Annan <gannan@digitalbazaar.com>
> wrote:
>
>> Announcement to the Community -- We're excited to announce the latest
>> update to the CHAPI Playground, which includes a new feature - Verification
>> Workflows You can now verify credentials presented from CHAPI-enabled
>> wallets.
>>
>> https://playground.chapi.io/verifier
>>
>> This feature is designed to help you test a complete lifecycle of a
>> Verifiable Credential.
>>
>> This is one of many updates that we're rolling out for the community in
>> the next few months. We will be adding support to the CHAPI Playground to
>> make it easy for others to add their verifier implementations – just like
>> the playground supports various issuer implementations today. We will
>> continue to add new Verifiable Credentials and make it easy for anyone to
>> contribute their own VC examples to be displayed on the site. Shortly, we
>> are planning to experiment with multiple types of protocols over CHAPI.
>> Stay tuned.
>>
>> If you have feature requests, please feel free to discuss them on this
>> mailing
>>
>> list or add them to:
>>
>> https://github.com/credential-handler/chapi.io/issues
>>
>> The team that put the CHAPI playground together is on the CCG and VC EDU
>>
>> mailing lists and are happy to answer any questions about current or
>> future
>>
>> functionality planned for the CHAPI Playground.
>>
>>
>> Instructions on using the new Verifier functionality is shown below for
>> those of you that would like to try it out:
>>
>> To start verifying VCs on the playground, please use the following
>> instructions:
>>
>> Wallet Sign Up
>>
>> 1. Sign up for any CHAPI-enabled digital wallet.
>>
>> For example, you could go to https://demo.vereswallet.dev/ and sign up:
>>
>> 2. Click "Get a Wallet".
>>
>> 3. Use an email address that you have access to. You can modify the email
>> address to create multiple accounts if you'd like:
>> myname+chapi@example.com (note the "+chapi" addition could have also
>> been "+2", "+3", and so on).
>>
>> 4. Make sure to "Allow" the wallet to handle credentials on your behalf.
>>
>> VC Issuance
>>
>> 1. Visit the playground by going to:
>>
>> https://playground.chapi.io/issuer
>>
>> 2. Click "Alumni" to load the alumni Verifiable Credential example into
>> the playground.
>>
>> 3. Click "Issue Verifiable Credential" and complete the issuance steps.
>>
>> VC Verification
>>
>> 1. Visit the playground's verifier:
>>
>> https://playground.chapi.io/verifier
>>
>> 2. Click "Alumni" to load the alumni credential request into the
>> playground.
>>
>> 3. Click "Request Verifiable Presentation" and complete the verification
>> steps.
>>
>>
>> Kind regards,
>>
>> Ganesh
>>
>>
>
> --
> *ORIE STEELE*
> Chief Technical Officer
> www.transmute.industries
>
> <https://www.transmute.industries>
>
Received on Tuesday, 14 March 2023 16:22:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 14 March 2023 16:22:08 UTC