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.
Submit
To enter a submission for this hackathon, provide the DWN Record ID of the KCC.
Resources
- Alice’s DID:
did:dht:rr1w5z9hdjtt76e6zmqmyyxc5cfnwjype6prz45m6z1qsbm8yjao - web5/credentials SDK
- web5/api SDK
- How to create a DID and DWN with Web5.connect()
- Obtain Bearer DID - required to sign KCC
- Known Customer Credential Schema
- How to issue a VC with Web5
- Example of issuing a KCC with Web5
- Example of issued KCC
- How to install a DWN Protocol
- How to store a VC in a DWN
Contact Us
If you have any questions or need any help, please reach out to us in our #kcc-hackathon channel on Discord.
Top comments (0)