TBD's Challenge: Known Customer Credentials
Tracks: Reusable Identity
Register: DevPost
Informational Session: Watch the recording
DIF Hackathon Discord Channel: #tbd
Website: TBD (Block)
Overview
tbDEX is an open messaging protocol that enables liquidity seekers to connect with liquidity providers. This means that as a liquidity provider, your business can be the backend supplier in several payment applications.
Performing KYC on repeat customers every time they attempt to transact with you from a different payment app would be a pain. To avoid this, you will use the Web5 SDK to issue a Known Customer Credential (KCC) to a customer, Alice, who you have already completed KYC on. You will store the JWT representing the KCC in Alice’s Decentralized Web Node so that she can present it to your business from any payment app.
Challenge
- Create a Decentralized Identifier (DID) and DWN to use as the Issuer.
- Bonus: Use the DIF community DWN instance hosted by Google Cloud.
- Issue Alice a KCC that includes
evidence
. Note that for this challenge, you do not need to implement an actual identity verification flow. - Install the VC Protocol onto your DWN so that you can communicate with Alice’s DWN.
- Obtain permission to write to Alice’s DWN by sending a GET request to https://vc-to-dwn.tbddev.org/authorize?issuerDid=${issuerDidUri}
- Store the VC JWT of the KCC as a private record in Alice’s DWN.
Submission Requirements
For this challenge, only the DWN Record ID of the KCC is required for submission. To work around the DevPost submission process, do the following:
- Enter the DWN Record ID of the KCC in the "Please provide a written description of how DIDs and VCs were used" field
- Enter "N/A" into the other required fields labeled:
- "Provide a URL to your public code repository."
- "Include a text description that should explain the features and functionality of your project."