Software Developer Blockchain Enthusiast
Software Developer Blockchain Enthusiast
Subscribe to Tushar Ojha
Subscribe to Tushar Ojha
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Finished with week 2 of Ethereum India Fellowship’3 and I am super excited to share the progress, plan & updates in this blog.
The developer identity is a privacy-focused verifiable identity for developers that can be used to hold claims / certificates for their achievements & activities. This includes:
Participating or Winning at a Hackathon
Doing a new course / tutorial
Finishing a internship
Receiving grants & completion badges
DAO contributions
On-chain reputation, etc.
If you would like to know more about why this is important or what is Ethereum India Fellowship, I would recommend you reading my first week’s article:
This week I planned out the working & idea of how identity system should work, and here it is:
Developer Identity will have 2 parts i.e. Public profile & Private profile.
Public profile basically represents the data available on-chain about the developer activities like opensource contributions, personal details, social connections, SBTs, POAPs etc.
The public profile should be controlled by the private-key holder, having access to private claims received on the device. To improve UX at scale, this will be in form of a mobile application.
The purpose of private profile is to manage the public profile and hold Verified Credentials. These VCs are held off-chain on the mobile device using PolygonID wallet technology integrated.
Developer can use both public & private data to validate / prove the authenticity at any point without the need to disclose all the information to everyone.
So, this week a couple of things happened:
On 16th Feb, Polygon ID team released new version of their software and now opensource everything that is necessary to build a prototype.
Started with the public page for developer profile, the purpose is to onboard and show data that is verified.
Implemented the biconomy SDK for smooth login & gasless user registry.
Getting contributions data on-chain & the graph is verified as it is coming from Sadaiv CI’s github contribution backup contract.
On Friday, I checked details of Polygon ID new version release and features provided.
The aim for next week (20th to 24th Feb) is to:
Start working on mobile app and try to integrate Polygon ID Wallet SDK in Flutter
Figure out the problem of onboarding via Web3Social Auth SDK but gasless transactions are not possible with Biconomy in Flutter
Go through docs for Polygon ID issuer server
Launch Github contribution contracts to polygon mainnet (as alpha version
More UI to see next week ✨
Never Stop Building ⚒️
Tushar Ojha
Finished with week 2 of Ethereum India Fellowship’3 and I am super excited to share the progress, plan & updates in this blog.
The developer identity is a privacy-focused verifiable identity for developers that can be used to hold claims / certificates for their achievements & activities. This includes:
Participating or Winning at a Hackathon
Doing a new course / tutorial
Finishing a internship
Receiving grants & completion badges
DAO contributions
On-chain reputation, etc.
If you would like to know more about why this is important or what is Ethereum India Fellowship, I would recommend you reading my first week’s article:
This week I planned out the working & idea of how identity system should work, and here it is:
Developer Identity will have 2 parts i.e. Public profile & Private profile.
Public profile basically represents the data available on-chain about the developer activities like opensource contributions, personal details, social connections, SBTs, POAPs etc.
The public profile should be controlled by the private-key holder, having access to private claims received on the device. To improve UX at scale, this will be in form of a mobile application.
The purpose of private profile is to manage the public profile and hold Verified Credentials. These VCs are held off-chain on the mobile device using PolygonID wallet technology integrated.
Developer can use both public & private data to validate / prove the authenticity at any point without the need to disclose all the information to everyone.
So, this week a couple of things happened:
On 16th Feb, Polygon ID team released new version of their software and now opensource everything that is necessary to build a prototype.
Started with the public page for developer profile, the purpose is to onboard and show data that is verified.
Implemented the biconomy SDK for smooth login & gasless user registry.
Getting contributions data on-chain & the graph is verified as it is coming from Sadaiv CI’s github contribution backup contract.
On Friday, I checked details of Polygon ID new version release and features provided.
The aim for next week (20th to 24th Feb) is to:
Start working on mobile app and try to integrate Polygon ID Wallet SDK in Flutter
Figure out the problem of onboarding via Web3Social Auth SDK but gasless transactions are not possible with Biconomy in Flutter
Go through docs for Polygon ID issuer server
Launch Github contribution contracts to polygon mainnet (as alpha version
More UI to see next week ✨
Never Stop Building ⚒️
Tushar Ojha
No activity yet