Kcc-tbd

Inspiration

I was inspired to work on this project due to the significant challenges a lack of access to proper KYC (Know Your Customer) documents can create. Having personally experienced the frustration of misplacing my identification documents, I know first-hand how disadvantageous it can be to navigate essential services without them. It can hinder everything from opening a bank account to verifying your identity online, creating unnecessary barriers in both personal and professional life.

Technologies like Decentralized Identifiers (DiD) and Verifiable Credentials have the potential to solve these issues by ensuring secure, user-controlled, and verifiable digital identities. These protocols empower individuals to manage their own identity data and enhance privacy and security by reducing reliance on centralized institutions. I am grateful for the opportunity to learn about and build with these cutting-edge technologies and I’m excited about their potential to create more equitable access to identity verification and digital trust.

What it does

The API simply takes in a customer's Did and uses it to generate an access token. Once the token is generated, it can then be used to sign operations such as creating a Known Customer Credential (KCC) for a user and storing the KCC in the user's DWN.

The code that converts the customer's DID to an access token serves as a way to mirror how real-life applications could use the same approach to build a middleware layer using customerDid to authenticate users within their application.

How we built it

The project was built using Javascript and then deployed to production using Firebase Cloud functions

Challenges we ran into

No challenges, the documentation for KCC and Verifiable Credentials on the Tbd website was very straightforward and helpful. The instruction guide for the project were also very useful.