ZeroVote uses cryptography to guarantee fair elections. No one sees results early. No one counts the votes. No one can corrupt the outcome. Ballots are timelock-encrypted. The decryption key doesn't exist until the reveal time. Code tallies votes deterministically. Zero-knowledge proofs guarantee validity. A Merkle tree makes tampering detectable. Everything is public. The person who creates an election has no more information than anyone on the internet.
Hey everyone, I'm Dylan, the builder behind ZeroVote.
Prediction markets have gotten very good at exposing who knows what before they should. During the Oscars, Polymarket lines were moving to winners before the envelopes opened. Someone in the counting process knew the results and was taking free money.
That's the same trust problem in every election. Board votes, union elections, shareholder proxies, HOA boards, political elections. Someone counts first. Someone knows first. Everyone else takes their word for it.
Most information asymmetries you can't fix with better software. But this one you can, because it's not a fact about the world. It's a design choice. Someone counts first because we built voting systems that way. You can build them so that no one does.
ZeroVote encrypts every ballot so the decryption key doesn't exist until the scheduled reveal time. When it does, everyone gets it at the same instant. The votes are tallied by code. No human touches the count. This isn't enforced by policy. It's enforced by the cryptography.
The verifier is open source. You can run the full pipeline yourself and check the result of any election on ZeroVote without trusting my server at all.
I wrote about the motivation and the technical design here: https://dylannikol.com/2026/04/1...
Would love your feedback.
Report
Reviews
No reviews yetBe the first to leave a review for ZeroVote
Prescene