# Helios Voting

Helios Voting is an open-source, web-based electronic voting system. Users can vote in elections and users can create elections. Anyone can cast a ballot; however, for the final vote to be counted, the voter's identification must be verified. Helios uses homomorphic encryption to ensure ballot secrecy.
It was created by Ben Adida, a software engineer involved in other projects such as Creative Commons and Mozilla Persona.

## Characteristic

Helios allows registered users to create elections. Each account requires an email address, name, and a password. The registered user can then create an election by specifying a name and time period. The user who created the election is known as the administrator of the election. Once an election is created, Helios provides a public key to the administrator. The administrator prepares the ballot and creates a voter roll—these can be edited at any time before voting starts. The administrator freezes the election when the election is ready for voters to cast ballots. When the election is frozen, no changes can be made to the ballot, voter roll, or election time frame.

### Source code

The front-end browser code is written in both JavaScript and HTML, while the back-end server code is written in Python. The Ballot Preparation System (BPS) guides voters through the ballot and records their choices. The process to create the ballot and process the votes is based on Benaloh's Simple Verifiable Voting Protocol.
Both frontend and backend are free software. The backend is released under the Apache 2.0 license. The frontend is released under the GNU GPL v3+.

### Voting process

A voter, from the voting roll created by the administrator, receives an email with the voter's username, a random password for that specific election, a URL to the voting booth, and an SHA-1 hash of the election parameters. The voter follows the link in the email and begins the voting process. Once the voter finishes and has reviewed the ballot, the voter seals the ballot which triggers Helios to encrypt it and display a ciphertext.
At this point the voter can either audit or cast the ballot. Auditing the ballot allows the voter to verify that the ciphertext is correct. Once ballot auditing is complete, that ballot is discarded (to provided some protection against vote-buying and coercion) and a new ballot is constructed. When the voter is ready to cast their ballot, they must provide their login information. Helios authenticates the voter's identity and the ballot is cast. All votes are posted to a public online bulletin board which displays either a voter name or a voter ID number with the encrypted vote.

### Tallying process

After an election ended, the Helios 1.0 system shuffled the ballots, decrypted all the votes, and made the shuffle publicly accessible for interested parties to audit. Auditing allowed anyone to verify that the shuffle is correct. Once a reasonable amount of time for auditing had passed, Helios decrypted the ballots and tallied the votes. Anyone could download the election data to verify that the shuffle, decryptions, and tally were correct. Helios 2.0, designed in 2008 and currently in use, abandoned the shuffling and switched to a homomorphic encryption scheme proposed by Cramer, Gennaro and Schoenmakers.

### System limitations

The Helios platform is intended to be utilized in low-coercive, small scale environments such as university student governments. The following limitations are known.

#### Privacy

* The centralized server must be trusted not to violate ballot secrecy, this limitation can be mitigated against by distributing trust amongst several stakeholders.
* Coercion and vote-buying are only ensured when material used to construct ballots (more precisely, nonces) are unknown to voters, e.g., when trusted devices are used to construct ballots.

#### Verifiability

* The ballot auditing/reconstruction device must be trusted to ensure successful ballot auditing (also known as cast-as-intended verifiability), this limitation can be mitigated against by distributing auditing checks amongst several devices, only one of which must be trusted.

### Security

* In 2010 researchers identified a ballot secrecy vulnerability.
* In 2011 and 2016 researchers identified cross-site scripting vulnerabilities. The first endangers sessions of administrators and was promptly patched. For the second, if the attacker is able to get a voter to click a specially crafted link, the voter will land on a modified HELIOS page which can violate ballot secrecy or manipulate votes. However, as of 2021 the vulnerability could not be recreated.

## History
### Adoption

Since 2009 the Universite Catholique de Louvain used Helios to elect its university president (of around 25,000 eligible voters, some 5,000 registered and 4,000 voted). In the same year also the Princeton University adopted it to elect student governments.
Since 2010, the International Association for Cryptographic Research has used Helios annually to elect board members.
In 2014 the Association for Computing Machinery used Helios for their general election.
During the COVID-19 containment measures in Malaysia (2020–2022), the Tamil Language Society & Hindu Society of University of Malaya, conducted their Executive Council Elections through Helios.