# Proof of Work for Developers By [Tushar Ojha](https://paragraph.com/@tushar-ojha) · 2023-02-19 --- > If you believe in technology, then developers are the ones who are driving it. Developers are the core part of web3 ecosystem too. But each and every developer today is facing a problem of **Proof of Work**. I have been coding since age 12, and have participated and won multiple hackathons including ETH India but I can’t prove it to you. :( The developer identity is aimed to resolve the issue of developers, as they need to provide their proof of work manually to get jobs, scholarships, opportunities and helping them get a clear reputation metric by collecting their contributions from different platform to blockchain. ![Developer Identity System](https://storage.googleapis.com/papyrus_images/98dc66522a7eae3d29915378466e10bb724810c8b82649a070007e3f6494257a.jpg) Developer Identity System Sounds interesting? ------------------- I am are very very thankful to **ETH India** Team for allowing me to focus on the research and building the first version of the product during the **ETH India Fellowship**. The fellowship is 8-week programme that provides full mentorship & support with good stipend to help you focus and build your project. Btw here’s my proof of selection in the Fellowship: [https://opensea.io/assets/0xfE8321Df99317C365797c4f95C2dbd9BeEC8C694/43](https://opensea.io/assets/0xfE8321Df99317C365797c4f95C2dbd9BeEC8C694/43) But here are some of the problems associated with this SBT as a proof: * \*\*Public in nature \*\*These NFTs are soul-bound that means these are non-transferrable from one EOA to other but these are public anyone can explore these NFTs on Opensea or contract explorers to reach my public profile and I will end-up sharing more details about myself than I want to. Why can’t I just prove to anyone that I am a part of **ETH India Fellowship** without sharing my wallet address? * \*\*Transferability Risk \*\*Despite being more secure than traditional standards like ERC-721, SBTs are not completely soulbound and can still be transferred. This can happen through private key sharing, multi-sigs, smart contract exploitation, or threshold ECDSA. * \*\*No common registry \*\*ETH India is just one of the issuer of the SBTs that I own, I also own NFTs from BuidlersTribe but as there’s no common registry it is very hard to use these for autonomously or in-code and leverage these as proofs properly. But today, these SBTs have become more of show-off among peers then actually being utilised as **PoW**. * \*\*Limited off-chain scalability \*\*These SBTs as proofs can’t be utilised on full-capacity off-chain due to there presence on-chain. How to solve these issues? -------------------------- The goal is to build an easy to use infrastructure layer for developers & applications built for the devs. Many applications should be able to leverage the proofs data available to create economy and wealth opportunities for developers. ![Architecture Plan](https://storage.googleapis.com/papyrus_images/281d5e0a211730aa673658c4a286c0e5fb7b30d932082e8c53e7c5dc326ecaae.png) Architecture Plan We will be leveraging the powers of Polygon ID system and other technologies to build this PoW protocol for developers and later expand for other professional workers as well. Verifiable Claims is the way forward for your achievements, these are privacy-focused and you can choose to reveal the limited information to someone about it. [Read More](https://mirror.xyz/0xeee68aECeB4A9e9f328a46c39F50d83fA0239cDF/K63khDZank5wrfzCulDq5R6dfN2m4zGanO5lsAxfg-w) Plans & work done so far ------------------------ I have been thinking in this direction for quite some time now and in the course of next 8 weeks we will be shipping the first version for public ✨ **This week (6th Feb to 10th Feb)**: * Researched for Polygon ID & use case with deeplink support * Added integration to support Github authentication with web3auth & Biconomy SDK * Rewrote smart contract with structs for more metadata like name, commit message, others for getting the contribution graph of users on-chain * Started with writing dev profile website design **Next Steps:** * Work on profile section & decide on features to show on the landing page of the website * Finish onboarding page for devs to call registerDeveloper contract method from biconomy gasless fees infra ~ Posting this a bit late but getting on-track now :) Stay tuned for updates ✌🏼 --- *Originally published on [Tushar Ojha](https://paragraph.com/@tushar-ojha/proof-of-work-for-developers)*