Confimo

Screenshots

Problem Statement

[Issues] The main dilemmas of Web2, or traditional, credential issuance are privacy infringement, data security issues, inefficiency, lack of portability, and loss.Data securityFor example, people are afraid of mapped their SNS accounts and Wallet address without any permissions. It’s important to keep data security.Privacy concernPrivacy concern is also important. Even though we have several off-chain credential projects, most projects do not protect users' privacy. Users need to share social media authentications to get credential data. We think that is a centralized way to get credentials.So here is why decentralized off-chain credential data is needed.Confimo Identity holder: User Verifier: Web3 Project Issuer: ConfimoExisted project Identity holder: User Verifier and issuer: Credential ProjectVerifier creates off-chain credentials and set up issuance process, then Confimo carries out the issuance process and issue off-chain credentials.Existed projects need to verify and issue off-chain credential at the same time because they need to verify SNS accounts.In our system, we assume SNS verified since Web3 projects have done giveawaysSince Confimo uses Web3 Project as a verifier, we don’t need to get SNS accounts to issue credentials. This produces the pure decentralized credential issuance system.[Technology we used]Polygon ID: We use Polygon ID for credential. Users create DID and ask claim after receiving giveaways from Web3 projects. We issue credential based on their community activities.Worldcoin: Web3 projects can get KYC to avoid scammers and bots for rewards.

Solution

Our biggest challenges werePolygon ID is not fully developedSince Polygon ID cannot set up number variable for data schema, we had to implement two transactions to issue credentials.Scalability of worldcoinWe use worldcoin as KYC, it’s important that Worldcoin gets enough user tractions.