The problem Sadaiv ID solves

Developers are the core part of the web3 ecosystem, but their work is at Risk

• Deplatforming: GitHub banned thousands of Developers in countries like Russia, Iran, Syria, etc.
• Lack of Privacy: GitHub can view private repositories and developer achievements are public.
• Censorship: GitHub owns the right to show, promote, host or take down any code repository.
• Certificates: Achievements like participation in competitions, or courses are unorganised.
• Unverifiable: Developer credentials are unverifiable as they are not standardised to be used.
• Volatile Storage: Certificates developer hold are prone to loss as they are stored locally on devices.

Building on-chain Developer Identity

Sadaiv protocol provides privacy-first self-sovereign on-chain developer identity using Polygon ID.

• Easily Verifiable
• Privacy-focused
• On-chain Graph

The developer identity aims to resolve the developers' issue of proof of work, as they need to manually provide their POW to get jobs, scholarships, and opportunities, and it will also help them get a clear reputation metric by collecting their contributions from different platforms on to the blockchain.

Multiple dapps can be built on top of this technology, like verifiable resumes, web3 fiverr, etc.

Challenges I ran into

Broadly there will be 3 important parts of the whole product:

• Public Profile website (on-chain profile): It’s like a unified public profile for developers where anyone can see details about an individual like hackathon participations, projects, GitHub contributions, jobs, etc.
• Private Wallet mobile app that holds all the new claims received and can choose to make them public or continue holding privately. These claims can be verified by scanning a simple QR code. This app will be built by leveraging Polygon ID Mobile SDK.
• JS SDK to easy the onboarding friction for developers building verifiers or issuers on top of this technology. People can use the SDK and set simple conditions to check for during off-chain verification of the zero knowledge proof generated by the users.

The most challenging was to build the issuer node locally and connecting the wallet SDK app with it.