Dear Shri Amitbhai Shah
Some 13 years back , through my following email , I had suggested that we
change over to mobile based voting for all elactions ( Central + States + Municipal
+ Panchayat ) :
> http://www.hemenparekh.in/2013/08/votesapp.html ... 18 Dec 2012
Since then, I have sent several reminder mails ( listed below )
I believe Election Comission has also made some attempts at mobile based voting
Now that we are seriously considering " One Nation , One Election " system, I
believe it is also the most opportune moment to move from Polling Booth based
elections to Mobile based elections
I present below, a very COMPREHENSIVE system design for VotesApp , developed
by Claude.ai
No doubt , this REFORM would require full support of all Political Parties / Election
Commission / Supreme Court / Citizen
I urge you to circulate this mail to all the concerned stakeholders for a public
debate / arriving at a PROCESS CONSENSUS and a TIME FRAME, before
conducting a PILOT PROJECT in one of the forthcoming State Elections
As a very FIRST STEP , this proposal may be uploaded / published on Election
Commission website and comments invited from citizen
The following chart which shows at a glance, the SAVINGS of Man-hours and
Money, by implementing VotesApp , would convince all concerned to whole-
heartedly support my suggestion
with regards,
Hemen Parekh
www.HemenParekh.ai / www.YourContentCreator.in / www.IndiaAGI.ai / 20 March 2026
===================================================
CC :
Shri Gyanesh Kumar [ Chief Election Commissioner / ]
Hon Chief Justice of India
===================================================
Claude replied :
Great proposal from Hemen Parekh !
The VotesApp idea is ahead of its time — Aadhaar-linked mobile voting with selfie
verification.
Let me build you a comprehensive system architecture for this.
Here's the full comprehensive breakdown:
Following User Interfaces ( Mobile Screens ) are extremely user-friendly :
These are the various layers of work-flow :
VotesApp — Complete System Architecture
Software Stack
Mobile (Android / iOS)
- React Native or Flutter (single codebase for both platforms)
- Available on: Google Play, App Store, GetJar, EC official site
- Pre-loaded on government devices (Aakash tablets, future schemes)
Backend Microservices
- Language: Go (for high concurrency — critical on election day spikes) + Python for AI/ML workloads
- Framework: gRPC internally, REST + GraphQL for clients
- Container orchestration: Kubernetes on NIC's MeghRaj sovereign cloud
Databases
- Voter registry: PostgreSQL with HA replication (never loses a row)
- Vote ledger: Permissioned blockchain (Hyperledger Fabric) — append-only, immutable, auditable
- Sessions / OTP: Redis Cluster
- Selfie hashes: Object store (S3-compatible) — faces never stored raw, only cryptographic hashes
Security
- End-to-end encryption: Ballots encrypted with ElGamal / homomorphic encryption so votes can be tallied without decrypting individual votes
- Zero-knowledge proofs: Voter can verify their vote was counted without revealing who they voted for
- Hardware Security Modules (HSM): All keys managed in HSM — tally keys split among EC officials (multi-party threshold)
- TLS 1.3 on all transport
AI / Face Match
- Selfie liveness detection (prevents photos of photos)
- Face matching against Aadhaar ABIS (Automated Biometric Identification System) via UIDAI API
- On-device preprocessing → cloud match (selfie never stored post-match)
Key Design Decisions aligned with Hemen Parekh's proposal
| Proposal Feature | Implementation |
|---|---|
Aadhaar-linked registration | UIDAI API with demographic + biometric verification |
Mobile number binding | Telecom API + OTP; vote only castable from registered SIM |
Underage prevention | Date of birth verified via Aadhaar — server-enforced, not just UI |
Selfie match (2015 addition) | Liveness check + ABIS face match at both registration AND vote time |
One vote only | Vote ledger checks voter ID before accepting — app hard-locked after |
Physical booth exclusion | EC voter rolls updated in real-time; polling officer app cross-checks |
Long-press candidate details | Candidate assets/criminal record pulled from EC affidavit API |
NOTA option | Fully supported in ballot UI |
Booth capture impossible | No physical location — attack surface is cryptographic, not physical |
Scale Planning (election day)
900M+ eligible voters;
peak concurrency could hit 50M+ votes/hour.
The architecture handles this via: horizontal pod autoscaling on Kubernetes, Redis
caching for candidate lists, async vote processing via message queues (Kafka),
and CDN edge nodes for static assets. Vote casting itself is sub-100ms — the
blockchain write happens asynchronously after the voter gets their confirmation.
==============================================
My Past Emails on this matter :
No comments:
Post a Comment