Hey Paul -- this solution is not ACA-py based, what you see here is a prototype that shares the same backend as our MATTR VII platform and leverages a browser-based solution for credential exchange known as "CHAPI" -- the Credential Handler API over at W3C. The decision to use CHAPI (which was a consensus amongst DHS SVIP cohort members) was largely due to the fact that CHAPI was a relatively easy way to have multiple vendors interoperate with independent technical stacks. To facilitate CHAPI we're using what's known as a polyfill which allows implementers to build and use in-browser functionality prior to browsers deciding to natively support those features. We are hoping to achieve more direct interoperability with projects like ACA-py in the future as part of the upcoming interop targets for AIP 2.0. You can read more about CHAPI here: w3c-ccg.github.io/credential-handler-api/ And you can find the polyfill here: github.com/digitalbazaar/credential-handler-polyfill
Nice demo. Is it an ACA-py based solution?
Hey Paul -- this solution is not ACA-py based, what you see here is a prototype that shares the same backend as our MATTR VII platform and leverages a browser-based solution for credential exchange known as "CHAPI" -- the Credential Handler API over at W3C. The decision to use CHAPI (which was a consensus amongst DHS SVIP cohort members) was largely due to the fact that CHAPI was a relatively easy way to have multiple vendors interoperate with independent technical stacks. To facilitate CHAPI we're using what's known as a polyfill which allows implementers to build and use in-browser functionality prior to browsers deciding to natively support those features. We are hoping to achieve more direct interoperability with projects like ACA-py in the future as part of the upcoming interop targets for AIP 2.0.
You can read more about CHAPI here: w3c-ccg.github.io/credential-handler-api/
And you can find the polyfill here: github.com/digitalbazaar/credential-handler-polyfill