SigmaSoiBois presents SigmaZK.
Proof of Work in a Zero knowledge way
built on ☕ at ETHIndia.
- Use Polygon ID to have collab.land as an issuer and verifier whilst allowing for discod admins and community managers more power to manage their community.
- A PolygonID Based on the principles of Self-Sovereign Identity (SSI) and cryptography, Polygon ID is a decentralised and permissionless identity framework for web2 and web3 applications. The SSI framework lets individuals own and control their identities.
- Core components in the Polygon ID
- Issuer In our POC, the issuer is collab.land
- An entity that issues claims to the Holders.
- Verifier It requests the holder to send proof based on the claims they hold in their wallet.
- A core concept is that trust must exist between a verifier and issuer.
- Issuer In our POC, the issuer is collab.land
- Polygon ID
- collab.land
- MERN
- Typescript
- Digital Ocean
- Dune
- Let's assume the flow begins with Admins in charge of DAOs and NFT Communities.
- collab.land acts as the issuer and verifier in our case and Polygon ID is the bridge in between them.
- The flow of the app begins with the admins who are the enforcers in the DAOs or NFT Communities.
- Once they sign up and create a Polygon ID associated with an organisation, they can create a schema based on which the ZK system is to be implemented.
- The members of the DAO or NFt community can claim offer (verifiable credential) by scanning the QR provided or deep linking.
- We have assumed collab.land to be the issuer and the verifier. It looks up into the chain and validates the proof.
- Once the claim is verified, the associated benefits as new roles and more are assigned to people on discord.
- Extending this system to more sophististicated systems.
- Initially we planned on using Dune for analytics in our project. We implemented the same, but later came to realise that as ours is a zero knowledge system we couldn't have any deep level analytics on the same.
- We also planned on using push protocol that'd notify users when they had successfully claimed an offer. As Push protocol requires the wallet addresses of the people who use it and our system is a zero knowledge system, we had to scrape that plan as well.
SigmaZK
is available under the MIT license. See the [LICENSE
](Enter URL) file for more info.
Please read [Contributing.md
](Enter URL) for details on our code of conduct, and the process for submitting pull requests to us.
Many people have contacted us asking if they can use this code for their own websites. The answer to that question is usually "yes", with attribution. There are some cases, such as using this code for a business or something that is greater than a personal project, that we may be less comfortable saying yes to. If in doubt, please don't hesitate to ask us.
We value keeping this site open source, but as you all know, plagiarism is bad. We spent a non-negligible amount of effort developing, designing, and trying to perfect this iteration of our website, and we are proud of it! All we ask is to not claim this effort as your own.
Refer to this handy quora post if you're not sure what to do. Thanks!