- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 7 Aug 2024 09:36:08 -0400
- To: W3C Credentials CG <public-credentials@w3.org>
On Tue, Aug 6, 2024 at 6:37 PM Golda Velez <gvelez17@gmail.com> wrote: > I didn't see in the quick read thru which are the libraries devs can use to make something similar to the VC Playground in our apps? Some documentation with code examples exists here (for issuers, wallets, and verifiers): https://chapi.io/ There is demo issuer website code here: https://github.com/credential-handler/chapi-demo-issuer There is demo wallet website code here: https://github.com/credential-handler/chapi-demo-wallet There is demo verifier website code here: https://github.com/credential-handler/chapi-demo-verifier Those are the basic components that constitute a VC Playground-like website. However, there is A LOT more going on under the hood -- like full blown VC API implementations, and OID4 implementations, and browser-to-browser CHAPI stuff, and browser-to-native CHAPI stuff, and cross-device presentation flows. While some flows, such as the CHAPI ones, are fairly easy to put together in a day or two, other flows, such as the OID4 ones, take weeks of dedicated development (or longer) to get right. The goal of the VC Playground is to enable implementers to test their implementations against other implementations in the ecosystem using multiple formats and multiple protocols; it's optimized to demonstrate interop, to play around (thus the name), not necessarily to show what production deployments look like. With all of that said, I'm unsure if I actually answered your question. Did I? :) -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Wednesday, 7 August 2024 13:36:49 UTC