Modular verifiable elections: Eos Voting
Go to file
2019-03-06 13:06:01 +11:00
docs Update README 2017-11-24 00:24:08 +11:00
eos Implement task timeout 2019-03-06 13:06:01 +11:00
eosweb Add run task CLI option 2019-02-17 15:04:59 +11:00
.babelrc Update for Transcrypt/Python 3.7 2019-01-14 17:54:31 +11:00
.gitignore Update for Transcrypt/Python 3.7 2019-01-14 17:54:31 +11:00
build_js.sh Update for Transcrypt/Python 3.7 2019-01-14 17:54:31 +11:00
HOWTO.md Document new npm dependencies 2019-01-14 18:20:25 +11:00
js.html Bring JS version of eos.core.objects up to date with Python 2017-09-25 11:47:29 +10:00
local_settings.example.py Tidy docs 2018-12-30 13:44:59 +11:00
package-lock.json Update for Transcrypt/Python 3.7 2019-01-14 17:54:31 +11:00
Procfile Use gunicorn for Heroku 2017-11-28 14:04:18 +11:00
README.md Add link to technical report 2018-01-20 21:56:19 +10:30
requirements.txt Explicitly specify oauthlib 2 2019-01-14 18:20:19 +11:00
runtime.txt Update for Transcrypt/Python 3.7 2019-01-14 17:54:31 +11:00
test.sh Implement a basic bitstream 2017-09-26 21:14:30 +10:00

Eos: Modular verifiable elections

Work in progress – Both API and GUI are sufficiently complete to have seen experimental use

Comparison with competitors

Helios Eos
Usable Yes Kinda
Good Yes Not really
Eye Candy No Yes!

Screenshot

Why create Eos? – Read here for some background.

Cryptographic details and references

Eos aims to be implementation-agnostic with respect to cryptographic details, with the included eos.psr package providing an example implementation.

For details of the implementation, refer to the Eos Voting Technical Report.

Mother of all disclaimers

This is a fun side-project of mine, and should in no way be considered to be a serious attempt to build a production-ready election system suitable for real world deployment. Not even crypto experts are quite up to the task, and I am most certainly not a crypto expert, nor am I anything resembling a professional in any field even tangentially related to cryptographic elections.

I cannot guarantee the security of this implementation whatsoever. In fact, I would go so far as to guarantee that this software has so many holes it gives Swiss cheese a run for its money. That said, please feel free to roast Eos on the issue tracker!