Final review before the Amoy deploy: hidden re-votes, a tally proved on chain, security and quality by CodeInIA · Pull Request #1 · CodeInIA/votain

feat(tally): a proof of correct decryption anyone can check

claude

committed

ce6907a

fix(contracts): close the pre-Amoy review findings

claude

committed

5738f35

fix(backend): server-fixed World ID action, honest credentials, bounded writes

claude

committed

c7510fe

fix(frontend): verifiable results, no invented receipt, safer identities

claude

committed

82fdbc4

feat(tally-cli): prove when publishing, and --verify with no key

claude

committed

6056c98

chore: CI lint and e2e, Node 24 / npm 11, honest README and known limits

claude

committed

d6251b7

Merge dev into final-revision-before-amoy-deploy

claude

committed

353e3fb

feat(frontend): recovery phrases from the EFF short wordlist, 124 bits

claude

committed

4e75fb8

test(frontend): phrases in the new word list in the last three suites

claude

committed

2892fb5

feat(circuits): ballot and tally circuits, trusted setup and generated verifiers

claude

committed

28e9ae2

feat(contracts): hidden re-votes, on-chain aggregate, proved tally

claude

committed

9e80094

feat: frontend, backend and tally CLI on the hidden-revote ballots

claude

committed

84f24d3

docs, ci: circuits job, hidden re-votes and honest limits

claude

committed

7f1ca92

fix: seed windows sized for proving, CLI exits after --verify, localized epoch refusal

claude

committed

5c918d7

fix(seed): ballots may be absent from a spec

claude

committed

5661e24

test(circuits): compile before the witness tests, never skip them

claude

committed

ca486d0

ci(circuits): generate phase 1 once and cache it on its own

claude

committed

5c23b95

Navigation Menu

Repository navigation

Final review before the Amoy deploy: hidden re-votes, a tally proved on chain, security and quality - #1

Final review before the Amoy deploy: hidden re-votes, a tally proved on chain, security and quality#1
CodeInIA merged 33 commits into
devfrom
final-revision-before-amoy-deploy

Commits on Sep 24, 2026

feat(tally): a proof of correct decryption anyone can check

fix(contracts): close the pre-Amoy review findings

fix(backend): server-fixed World ID action, honest credentials, bounded writes

fix(frontend): verifiable results, no invented receipt, safer identities

feat(tally-cli): prove when publishing, and --verify with no key

chore: CI lint and e2e, Node 24 / npm 11, honest README and known limits

Merge dev into final-revision-before-amoy-deploy

feat(frontend): recovery phrases from the EFF short wordlist, 124 bits

test(frontend): phrases in the new word list in the last three suites

feat(circuits): ballot and tally circuits, trusted setup and generated verifiers

feat(contracts): hidden re-votes, on-chain aggregate, proved tally

feat: frontend, backend and tally CLI on the hidden-revote ballots

docs, ci: circuits job, hidden re-votes and honest limits

fix: seed windows sized for proving, CLI exits after --verify, localized epoch refusal

fix(seed): ballots may be absent from a spec

test(circuits): compile before the witness tests, never skip them

ci(circuits): generate phase 1 once and cache it on its own

Commits on Sep 27, 2026

fix(contracts): refuse a deployment before its first transaction

fix(circuits): compile on Windows with the native circom

fix(frontend): quote paid ballots at each election's circuit size

fix(frontend): read failures, the hourly limit and gaps found testing end to end

fix(frontend): steady local RPC proxy, and no chain reads for demo elections

Commits on Sep 28, 2026

fix(frontend): scale an unmeasured circuit size by its circuit, not its options

feat(frontend): replace a ballot straight away through the previous epoch

docs(frontend): terms, how it works and privacy say what the contracts do

docs: the current ballot scheme, the Amoy deploy steps and the last-hour limit

chore(deps): update every package to its latest release

perf(frontend): import Poseidon by arity, not from the package root

docs: Mermaid architecture diagrams in every README

docs: two ballots within an hour, not one, now that the app uses both epochs

docs: the hand-drawn diagrams in the dev docs become Mermaid

docs: future work, and the one tally limit the docs did not state

docs: future work, taking the per-user gas off the platform