Voter Registration
Online or agent-assisted registration assigns each voter to a single polling station. One voter, one station, one entitlement.
Technical Whitepaper
A Secure Voting System Using Encrypted QR Codes and Blockchain Principles
Biometric authentication, encrypted vote casting, a write-once hash-chained ledger and read-only observer oversight — engineered as one architecture rather than four products.
Contents
- Abstract
- 1. Introduction
- 2. System Architecture
- 3. Cryptographic Identity
- 4. Vote Casting
- 5. Hash Ledger
- 6. Observer Oversight
- 7. Finalisation
- 8. Design Limits
- 9. Conclusion
Document control
Technical whitepaper — public summary
[PLACEHOLDER — version, date, author]
Full paper on request
Abstract
Abstract
This whitepaper presents a cryptographically secure, blockchain-inspired voting architecture addressing the core challenges of modern elections: security, transparency, trust and accessibility.
The system integrates biometric authentication, encrypted vote casting, hash-chained vote logging and observer dashboards, and is adaptable to both in-person and remote voting scenarios. The architecture is designed to be tamper-evident, read-only and fully auditable, with no single point of failure and no path for manual intervention in the record once a vote has been committed.
1. Introduction
Traditional voting systems are vulnerable to tampering, duplication, voter exclusion and delayed tallying. Each of these is, at root, the same problem in a different place: a record exists that somebody can alter, and no independent party holds the evidence needed to notice.
This architecture ensures that each voter is authenticated, each vote is immutable once committed, and results are publicly auditable in real time. It provides a write-once voting record, prevents unauthorised data alteration, and is resistant to single-point failure by design rather than by operational discipline.
Section 2
Voting System Architecture
Seven integrated modules. Each has a defined interface, and no module can rewrite what a module before it has committed.
Cryptographic Key Generation
Each voter receives a unique cryptographic key tied to their identity and polling station. Once generated it is non-modifiable.
Offline Biometric Verification
On polling day voters are verified by 1:1 biometric matching against a QR-coded voter ID, with no dependency on a live network link.
Vote Casting & Cryptograph Generation
Encrypted votes are captured and represented as cryptographs carrying a unique vote ID. Read-only from the moment of submission.
Ledger Construction
Votes are chained into a tamper-evident, write-once hash structure that offers no overwrite path.
Observer Dashboard
Real-time read-only access enables transparent oversight with no capability to modify any record.
Finalisation & Reporting
Results are tallied, signed, timestamped and distributed securely. No manual entry is accepted at any point in the reporting path.
Detail
Sections 3 to 7 describe each stage in the terms a commission’s technical committee will want to interrogate.
Request the full paper3. Cryptographic Key and Identity Control
Each voter is assigned a unique cryptographic key during registration. The key is linked to their name, their polling station and a cryptographic ID, so that a vote can be located by any of these references without that lookup revealing how the vote was cast.
This guarantees each voter is uniquely represented in the system — the property that makes duplicate voting detectable rather than merely discouraged. Once generated, the key is non-modifiable and exists solely to establish vote origin.
4. Vote Casting and Cryptograph Generation
Following biometric verification, the voter casts a vote on a secure device. The system generates a cryptograph containing an anonymised voter ID, the encrypted vote, the polling station ID, a timestamp and a unique vote ID.
The cryptograph is issued to the voter by SMS or email, or held in a secure station file for voters without digital contact details. It is read-only and cannot be edited after submission.
On voter receipts. A receipt that proves how a person voted
would enable vote-buying and coercion, which is why secrecy and verifiability are
usually treated as being in tension. The cryptograph is designed to resolve that
tension: it allows a voter to confirm that their vote was recorded and is included in
the ledger, without disclosing their choice to anyone who demands to see it.
5. Hash-Chained Ledger
Each vote cryptograph is hashed and appended to the previous vote in a blockchain-style ledger. Every block contains the vote hash, a timestamp, the device signature and a hash link to the block before it.
The chain ensures that no past record can be altered without invalidating every entry that follows it. This write-once structure prevents overwriting, and the ledger is redundantly stored so that no single component failure or single administrator can compromise it.
6. Real-Time Observer Oversight
Authorised observers access a real-time, read-only dashboard showing activity across all polling stations. They can verify voter checks, ledger integrity and system performance without seeing voter identities or vote content.
No observer holds write access. This matters more than it may appear: an oversight mechanism that could alter the thing it oversees is not oversight, and a commission will be asked to prove the distinction.
7. Result Finalisation and Reporting
At the close of poll the ledger is sealed with a final hash block. Results are automatically tallied, signed, timestamped and submitted to the electoral commission. Voters receive result summaries for their own polling unit, which places the local figure in the hands of the people best placed to notice if it is wrong.
The reporting module is read-only. There is no post-election path by which a total can be adjusted without the adjustment being evident in the chain.
Section 8
Design limits: what this architecture does and does not prove
We publish this section because a commission’s technical advisers will raise these points, and it is better that we raise them first. A whitepaper that claims to solve everything is one that has not been reviewed by anyone qualified to disagree with it.
What the ledger proves
- That a committed record has not been altered since it was committed.
- That the sequence and count of committed records is intact.
- That any alteration is detectable by any party holding a prior copy.
- That no administrator can silently insert, remove or reorder a vote.
What it does not prove
- That the record captured matched the voter’s intent at the moment of casting.
- That the casting device was free of compromise before the vote was encoded.
- That an eligible voter was not prevented from reaching the polling station.
- Anything at all about conduct outside the system — intimidation, procedural abuse, or litigation.
The voter-verified record
The gap between those two columns is the reason a voter-verified physical record is offered as a configurable deployment option rather than treated as obsolete. Where a commission’s legal framework requires a recountable artefact — and many do — the system produces one at the point of casting, which the voter confirms before the vote is committed to the ledger.
The two mechanisms answer different questions and are strongest together. The paper record establishes that the digital record reflects voter intent; the hash chain establishes that the digital record has not since been changed. Neither substitutes for the other.
Deployment configurations
| Configuration | Recountable artefact |
|---|---|
| Ledger with voter-verified paper record Recommended where law requires a recount capability |
Yes — per vote |
| Ledger with polling-unit paper summary Signed unit-level totals retained at HQ |
Yes — per unit |
| Fully digital ledger Requires a legal framework that accepts a digital record as definitive |
Digital evidence only |
The configuration is the commission’s decision and its legal advisers’, not ours. Our obligation is to state the trade-off accurately before it is taken.
Section 9
Conclusion
This architecture delivers verifiable, secure and fully auditable elections. It supports secure in-person and remote voting, prevents duplication, and integrates transparency tools sufficient to satisfy public and international scrutiny.
It is designed for national scalability and democratic resilience: a tamper-evident, write-once infrastructure with no single point of failure and no manual manipulation path. Where a commission requires a voter-verified physical record, the architecture accommodates it as a first-class configuration rather than as a concession.