Github verified Lens

You enter your email ID, and the GitHub repo link which you claim to have access. It asks you to sign from your Metamask, and autofills the lens id field without an option to edit. Once you add your claim, it shares a QR code, scanning which, it will direct you to the reclaim wallet app, where the ZK based verification is run on your local without revealing the user credentials. Once the verification is completed and you submit the claim. The GitHub lens verifier approves the claim and gives you the tick mark. If you don’t have access to a GitHub profile, and yet you submit your claim it generates a failed response which can't be submitted.

We have primarily used the Metamask SDK, the Lens protocol and the Reclaim SDK.

The metamask SDK makes it easier for us to connect to the blockchain through the browser extension. There is no need to share the private key. The SDK exposes a provider that can request transactions to be signed on the wallet.

Reclaim SDK is based on the Reclaim protocol that allows a person to export any data from any website on the internet and generate a zk-proof out of it. It is completely trustless and privacy preserving. Such a protocol puts the user in complete control of their data. They are reclaiming their data from websites' databases. This data is rightfully theirs and should have sovereignty over how and where this data is used.

This effectively means, every single website is now converted into an API. Being dependent on TLS 1.3, Reclaim protocol would always work, unless the website decides to change their underlying network structure model.

Lastly, once Metamask is connected, the Lens Client SDK is used to fetch the Lens ID owned by the address. Once we have that, we allow the user to uniquely generate a claim that they have contributed to a particular github repository. The Reclaim Wallet opens up where the user can claim and submit the proof on-chain.