-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merkle Accumulator for voter addresses in each proposal #354
Comments
The Issue with the standard merkle accumulator is that the proofs submitted by voters/relayers would change after every vote is cast. This makes the system susceptible to front running attacks which could lead to censorship. This paper seeks to address this issue: https://eprint.iacr.org/2015/718.pdf |
We would store a merkle root of the list of addresses who have voted. Then each time someone votes, they would send a merkle proof of exclusion from this list to prevent double voting. If the voter has not already voted, the proof would pass and then the merkle root would be updated to include the new voter.
Currently we write a new storage slot for each voter, whereas this approach would mean we just need a single slot containing the merkle root for all voters.
The text was updated successfully, but these errors were encountered: