RunasSudo
/
Eos
1
Fork 0
Code Issues Pull Requests Activity
Modular verifiable elections: Eos Voting
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
178 Commits
3 Branches
0 Tags
0 B
 
 
 
 
 
 
Tag: Branch: Tree: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
RunasSudo 8333dd7c2d
Fix BLT export format 		2 years ago
docs Update README 6 years ago
eos Fix BLT export format 2 years ago
eosweb Allow hiding voters and/or votes 2 years ago
.babelrc Update for Transcrypt/Python 3.7 4 years ago
.gitignore Update for Transcrypt/Python 3.7 4 years ago
HOWTO.md Document new npm dependencies 4 years ago
Procfile Use gunicorn for Heroku 6 years ago
README.md Add link to technical report 5 years ago
build_js.sh Update for Transcrypt/Python 3.7 4 years ago
js.html Fix unit tests 2 years ago
local_settings.example.py Tidy docs 4 years ago
package-lock.json Support null-encrypted election in web UI 2 years ago
package.json Support null-encrypted election in web UI 2 years ago
requirements.txt Update to Transcrypt/Python 3.9 2 years ago
runtime.txt Update for Transcrypt/Python 3.7 4 years ago
test.sh Implement a basic bitstream 6 years ago

README.md

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!