If you’re looking for the Helios source code, it’s available via the (so far fantastic) git version control system hosted by GitHub:
and the tickets are tracked by Lighthouse. Anyone who finds a bug or has a feature request is free to enter the info directly into Lighthouse:
To date, Helios has done all of the key management for you, which is really handy when you don’t want to deal with that messiness. And in any case, while a malicious Helios could find out how you voted, it could never fake the tally, thanks to the Helios Verification Specs.
But you might not want Helios to know the secret key to your election. You might want to manage it yourself. Now you can.
However, there is really no way to tally the election if you lose your key. With great power comes great responsibility. So be careful.
Helios is meant to be verified by anyone. You can go write your own code to verify that Helios is running your election properly. Ah, but to write code, you need specs. So here is the Helios Verification Specification. Feedback welcome!
So with Helios Voting launched a couple of weeks ago, much interest expressed by various folks regarding Helios, and much hacking to keep improving the feature set, it’s time for the Helios Voting blog! Subscribe to stay afloat of Helios Voting developments.
And, of course, go create an election at any time.
