- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 8 May 2024 08:00:00 -0400
- To: W3C Verifiable Credentials Working Group <public-vc-wg@w3.org>
Hey VCWG, The California DMV just launched OpenCred[1], an open source Verifiable Credential Verifier software system. https://github.com/stateofca/opencred This system is designed to make it easy for organizations (verifiers) to validate credentials from individuals (holders), with their consent, in a secure and verifiable way. It has support for many of the W3C, IETF, and OpenID standards and specifications in incubation, including the Verifiable Driver’s License specification[2] that is being incubated in the Credentials Community Group, which supports the expression of the ISO-18013-5 Mobile Driver’s License (mDL) attributes as a Verifiable Credential. This is a big deal. More than 39 million people live in California. More than 27 million people have a California driver’s license, and the state recently launched a digital driver’s license program[3]. Free and open source software that can verify these digital credentials lowers the bar for these digital credentials to be deployed throughout California and the rest of the United States. The standards compliant, open source, OpenCred platform provides this functionality to enable Verifiers in the U.S., and globally, to accept Verifiable Credentials issued by the California DMV and other similar Verifiable Credential issuing agencies across the US. The platform provides the following feature set to start: * Docker-based deployment to popular on-premise, hybrid, and cloud environments such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure. * Horizontal scaling to support tens of millions of verifications per day. * Customizable colors, brand images, and page text. * Support for the W3C Verifiable Credentials Data Model and W3C Decentralized Identifiers. * Support for workflows as an OpenID Connect Identity Provider or using an HTTP API for non-OpenID systems. * Open digital wallet selection support through the Credential Handler API (CHAPI) * Presentation protocol support for Verifiable Credential Exchanges API (VC API) and OpenID for Verifiable Presentation (OID4VP). * Native/local verifier support that is not dependent on any external services. * Remote/external verifier support using either the Verifiable Credential Verification API (VC API) or Microsoft Entra * Storage of historical DID Documents to enable local auditing A huge shout out to the people that made this happen (many of them from this Working Group and the Credentials Community Group): * Brian Richter, Nate Otto, and Kayode Eizike who did the bulk of the work to build out OpenCred, * Dave Longley, Mandy Venables, Matt Collier, Ganesh Annan, Dave Lehn, Tashi Gyeltshen, Andrew Jones, and the rest of the Digital Bazaar team who did DevOps and built the Bedrock and Digital Bazaar libraries, upon which OpenCred is based, * Simon Bihel, Tiago Nascimento, Timothée Haudebourg, Jacob Healy, Wayne Chang, and the rest of the Spruce team who were our tireless partners on the digital wallet front, And last but certainly not least, Steve Gordon, Ajay Gupta, Savita Farooqi, Ajay Khanna, and the rest of the California DMV team that had the foresight to create, fund, and see such an initiative through to completion. This is an empowering opportunity for the ecosystem. There are a number of additional exciting announcements to come over the next several months that will build on this announcement. Please feel free to reach out, either publicly or privately, with any questions that you may have. -- manu [1] https://github.com/stateofca/opencred [2] https://w3c-ccg.github.io/vdl-vocab/ [3] https://www.sfchronicle.com/bayarea/article/dmv-mobile-digital-drivers-license-18350598.php -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. https://www.digitalbazaar.com/
Received on Wednesday, 8 May 2024 12:00:52 UTC