Ariton: Known Customer Credential Mini App

Inspiration

The Ariton Community Super App has multiple Mini Apps, and I was inspired to make one specifically for the Known Customer Credential use case.

What it does

It informs the user what the app does, then allows to request permission to write (the app is made to be dynamic, but the hackathon scenario requires hosting an API and only a single DID can be used to request permission in this release). After permission, the user can edit some values to issue the KCC, which is generated, signed and saved to Alice's DWN. Then the app allows to retrieve and render all the KCCs that Alice have received.

How we built it

Built by relying on the existing Ariton app, which is built on Angular and TypeScript.

Challenges we ran into

Was not able to properly filter using "author" in the query, to only list certificates issued by the user of Ariton. Instead, all certificates are returned and shown.

Accomplishments that we're proud of

Perhaps it was the first successful delivery of the KCC VC to Alice's DWN?

What we learned

Learnt a bit about the KCC process and that a server API can be hosted to write role permissions to a user's DWN.

What's next for Ariton: Known Customer Credential Mini App

Modify the app to rely on the Ariton "Connect" request infrastructure, that relies on user's manual acceptance of permission (role assignment), and then individuals and companies can issue the KCC (and potentially other) VCs to the users that have approved.