Competitive Landscape: Auditable Voting Systems & UI Patterns

A research overview of existing voting tools, cryptographic voting schemes, and blind signature applications — compiled to inform the design of auditable-voting.

I. General Engagement Tools (No Cryptographic Verification)

These tools excel at UX but offer no cryptographic guarantees of anonymity or verifiability.

UX patterns worth borrowing:

• One question at a time (Typeform, GOV.UK/HMRC) — reduces cognitive load
• Progress indicators — linear step-by-step flow builds trust
• Mobile-first simplicity — large hit targets, minimal clutter

II. E-Voting with End-to-End Verification

Helios Voting

The most widely-used open-audit voting system.

• Protocol: Homomorphic encryption (ElGamal), not blind signatures
• Claim to fame: 2,000,000+ votes cast; used by IACR, Princeton, etc.
• Architecture: Centralized server, requires login (Google/GitHub)
• UX problem: Originally forced users to choose "Audit" vs "Cast" mid-flow, causing confusion

KIT's Helios Usability Redesign

Researchers at Karlsruhe Institute of Technology redesigned Helios with a key insight:

"Automatic Audit" mode — verification runs silently in the background. Users never see the complexity.

This proves that cryptographic voting CAN be usable if the UI hides everything.

References:

• Helios: Web-based Open-Audit Voting (USENIX 2008)
• KIT E-Voting Research

III. Blind Signature Ecosystem: Cashu

Cashu is a Chaumian ecash protocol using blind signatures — the same cryptographic primitive as auditable-voting. These wallets prove blind signatures can be invisible to end users.

Key UX Patterns from Cashu Wallets

1. Users see "balance" and "send" — not blind signature mechanics
2. Cryptographic operations happen invisibly
3. Recovery via seed phrase (familiar from Bitcoin wallets)
4. One-tap token minting/spending

Critical insight: eNuts and Minibits demonstrate that blind signature wallets can achieve mainstream usability. A voting system could model the voter experience as "spending an anonymous token into a public bucket."

Links:

• Cashu Protocol
• eNuts GitHub
• Minibits
• Nutshell GitHub

IV. Academic Blind Signature Voting Schemes

FOO Scheme (Fujioka, Okamoto, Ohta — 1992)

The foundational protocol for blind signature voting.

• Mechanism: Voter obtains blind signature from administrator, then anonymously submits ballot
• Properties: Eligibility verification + vote anonymity + double-vote prevention
• UI: None — exists only as academic papers and CLI prototypes

David Wagner's Chaumian Variant (1996)

• Mechanism: Blind Diffie-Hellman Key Exchange
• Used by: Cashu protocol
• Reference: Wagner's 1996 cypherpunks post

The gap: No blind-signature voting system has a polished, production-ready UI. This is the opportunity for auditable-voting.

V. Comparison Matrix

VI. Design Patterns for Cryptographic Voting UI

Based on the above research:

For Voters

For Organisers

Borrow from Non-Voting Tools

VII. Next Steps

1. Look at Cashu wallet UIs (eNuts, Minibits) for token handshake patterns
2. Study GOV.UK design system for accessible form fields
3. Build a 3-screen mockup: Question → Signing Animation → Receipt

References

• auditable-voting GitHub
• Helios Voting
• Helios GitHub
• Cashu Protocol
• Cashu NUTs Specification
• eNuts GitHub
• Minibits Wallet
• GOV.UK Design System

Compiled for the auditable-voting project. Feedback welcome.