README: update info on zk-SNARKS
Use logger and close TUI (if present) when handling panics
Use syncer hooks instead of recurring updates for TUI
Start and join events for keys msgs must belong to the same election
Use t.Fatal instead of panicking in tests
Insert panic to help root out bug
Use cached list of hash seeds
Fix voter JSON marshalling
Do not proceed to ballot TUI if we're missing proving keys
TUI: notify user when keys are being sent
Use one witness for evals circuits
This ensures the coefficients for any given voter are used consistently for
every input s/he evaluates.
Redact all events (except Sum) we sent once the election is over
In case tallyard has terrible cryptography, this will protect most people who
are casually using the software.
Remove infinite retries for reading proving keys
It seems this was fixed in gnark-crypto v0.4.0 [0]:
point.SetBytes can now be called concurently with same byte slice input
[0]: https://github.com/ConsenSys/gnark-crypto/releases/tag/v0.4.0
Upgrade gnark and gurvy (now gnark-crypto)
Implement zero-knowledge proofs for evaluations and summations
Candidates had to be limited to 5 since 5*5=25 is the largest square less than
32, thu number of bytes in a BLS12-381 point:
https://github.com/ConsenSys/gurvy/blob/e350ead0219d4f30aa72ec85d1857b573d2f136a/bls381/fr/element.go#L596
Don't participate in election if we didn't join
Don't participate in elections with fewer than two voters
Don't allow zero for inputs