There will be a few key assumptions made, so we’ll highlight which additional nuances to address in order to fully decentralize the private voting process. This will show how we disassociate voter identity from the knowledge that the voter has been authorized to vote in its current round. Part 1: We analyze Zero Knowledge Proofs (ZKPs) on-chain with pre-generated values. This blog post will be part of a three-part series: These addresses are the default in the Remix VM provider.
The first row is the public address of the account signing the transaction. This process can be generalized using a ZK-Snark library such as This is particularly useful for creating a decentralized voting protocol that verifies live events. It is a way to encourage people to vote without revealing their identities. This is an example of a voting contract that gives each voter a chance to win a lottery (another real-life use case would be a boardroom vote in a corporate setting). Throughout the following explanation, we will use the example of an on-chain anonymous voting election with three running candidates: Alice, Bob, and Charlie. We will need to use Zero Knowledge Proofs to substantiate this function. However, this voting needs to be done in private, which is difficult on an open platform such as Ethereum.
The Proof of Trust (PoT) Protocol enables network participants, or Delegates, to individually input data and achieve distributed consensus on a live verifiable event. This is crucial to ensuring that delegates can act independently and cannot be compromised. This is a post that iCash CTO Ling Qing Meng and I worked on together to explain how our team developed a voting system that maintains the anonymity for our Delegates using Zero Knowledge Proofs.
0 kommentar(er)
