Rules, Regulations &
High-Security Protocols
Democratic processes require maximum trust. Block Vote implements cutting-edge cryptographic structures, offline synchronization models, and anti-coercion layers to protect every voter.
Cryptographic Security
Institutional-grade cryptographic safeguards enforcing absolute voter privacy and integrity.
One-Way Cryptographic Nullifiers
Each eligible voter maps to a unique, salted hash computed server-side: NullifierHash = keccak256(orgSlug || email || serverSecret). This acts as a single-use ticket on the Ethereum blockchain. It is mathematically impossible to link a nullifier back to a real email address, ensuring absolute anonymity while preventing duplicate voting.
Key Integrity Checks
- •Stored as bytes32 on-chain to ensure collision resistance.
- •Salted with a secure server-side secret.
- •Prevents linkage between a voter's identity and their selected candidate.
Biometric Sybil Defense & Liveness Verification
Before a vote is relayed, the voter must perform a 3D facial liveness check. A facial similarity comparison verifies the selfie against their registered face and cross-compares it with the faces of all users who have already voted in the active election. If a similarity >= 85% is detected on another cast ballot, the transaction is rejected.
Key Integrity Checks
- •Checks for head rotation, lighting, and blink detection.
- •Face parameters normalized locally to prevent camera distance bias.
- •De-duplicates voters to block Sybil attacks using multiple email aliases.
2-of-3 Guardian Upgrade Governance
To eliminate administrative centralization, all core smart contract upgrades require on-chain multi-signature approval. The Voting contract follows the UUPS proxy standard, where logic upgrades cannot be finalized unless at least two of the three independent Guardian public addresses sign the co-proposal.
Key Integrity Checks
- •Enforced directly within the Solidity _authorizeUpgrade execution path.
- •Guardian actions are public and logged on the blockchain ledger.
- •Guarantees that no single administrator can change the voting rules mid-election.
System Deployment & FAQs
Answers to critical questions regarding the implementation and verification of this voting architecture.
How are gangster-controlled locations physically protected?
Besides digital protections (like dummy votes and re-voting), physical booths in high-risk zones use armored, portable voting kiosks. These kiosks require active 3D face liveness checks, meaning gangs cannot submit photos, videos, or pre-recorded biometric details of citizens. Real-time GPS and network heartbeat monitoring automatically alert central authorities if a kiosk is tampered with or moved.
What happens to data when an offline booth syncs?
When an offline booth is brought back to a location with internet access, the cached block of vote payloads is uploaded to the Next.js backend server. The backend validates each transaction signature on the server, verifies that the voter nullifiers have not already cast votes on-chain, and passes them to the smart contract relayer queue for serialized, collision-free writing onto the Ethereum ledger.
Is the biometric data stored on the public blockchain?
No. To preserve absolute privacy, raw images and biometric ratios are never recorded on the public ledger. Facial comparisons are executed off-chain inside secure server-side API environments. Only the hashed metadata CID (IPFS) and the cryptographically secure Nullifier Hash are stored on-chain to block Sybil attacks.
Can a voter verify their vote was counted?
Yes. After voting, voters receive a transaction hash via email (or a printed receipt in offline areas). By visiting the /verify page, they can query the blockchain directly. The interface fetches the transaction data, confirming the block number, timestamp, and that their nullifier was registered, without exposing their ballot choices.
Ready to integrate Block Vote?
Launch elections with institutional-grade cryptographic protections. Protect voter freedoms anywhere, anytime.