Kode Company
Back to Portfolio
E-Governance & EdTechE-Governance / Campus E-Voting

DigiVote

Digital College Election Management System

End-to-end campus election platform combining frozen voter eligibility, anonymized ballot separation, SHA-256 Merkle Tree integrity verification, and automated result publication.

Industry
Higher Education (EdTech)
Domain
E-Governance / Campus E-Voting
Application Type
Web Application (REST API + SPA)
Target Users
College Admins, Returning Officers, Students
Kode Company branding — Build. Solve. Evolve. (DigiVote)

Project Overview

DigiVote replaces paper ballots and manual vote counting in college elections with a controlled digital election workflow. Administrators configure elections, define multi-position contests, import student directories, and lock eligibility criteria before voting opens.

To balance verifiable integrity with voter secrecy, the system decouples the voter register (which records who participated) from the anonymous ballot store (which records what was selected) with no foreign keys or shared timestamps linking the two records. When an election closes, ballot hashes are organized into a Merkle Tree checkpoint before automated counting.

Designed specifically for higher-education campus governance rather than statutory public elections, DigiVote enforces strict server-side UTC voting windows, single-vote database constraints, and deterministic vote tallying.

Business Challenges

Manual tallying is slow and vulnerable to human counting mistakes

Counting physical paper slips across departments delays announcements and introduces reconciliation errors.

Preventing duplicate votes across concurrent login attempts or multiple devices

Paper sign-off sheets struggle to synchronize live eligibility and per-position ballot locks.

Department, programme, and academic-year eligibility changes mid-election

Static printed lists fall out of sync with active student records.

Balancing ballot secrecy with post-election tamper detection

Physical ballot boxes provide no cryptographic audit trail once reopened for counting.

Solution & Engineering Approach

DigiVote structures campus elections into an auditable multi-stage pipeline with frozen eligibility snapshots, idempotent ballot submission transactions, separated voter/ballot storage, and Merkle root integrity checkpoints.

End-to-End Platform Workflow

  1. 1Election Configuration (Draft -> Scheduled)
  2. 2Eligible Voter Snapshot & Candidate Registration
  3. 3Server-Time Controlled Open Voting Window
  4. 4Transactional Unlinked Ballot Storage
  5. 5Election Close & Shuffled Merkle Tree Root
  6. 6Verified Automated Tally & Read-Only Archive

Key Capabilities & Functional Modules

Election Lifecycle & Governance Controls

Deterministic state progression locking rules once polls open.

  • Managed election lifecycle from DRAFT and SCHEDULED through OPEN, CLOSED, RESULT_PUBLISHED, ARCHIVED, or CANCELLED.
  • Supports class-representative, departmental, and college-wide contests with configurable positions and seat counts.
  • Automatically freezes election configuration and eligible voter lists when polls open so mid-election profile edits cannot alter access.

Student Directory & Candidate Administration

  • Bulk student import via CSV with validation and duplicate record checks across department, programme, class, and year.
  • Rule-based eligibility per position plus candidate registration with manifestos and photos tied to eligible groups.
  • Explicit handling for withdrawn candidates without purging audit records once campaigns begin.

Privacy Separation & Cryptographic Tamper Evidence

  • Two-factor student login combining institutional ID/password with SMS OTP verification via Twilio.
  • Atomic database transaction simultaneously marks voter participation and inserts an unlinked UUID v4 ballot record.
  • Unique database constraint on (election_id, position_id, voter_id) plus request idempotency keys block double clicks and network retries.
  • Ballots store no insertion timestamps or sequential IDs, eliminating correlation between vote timing and voter identity.
  • Post-close SHA-256 hashing with random nonces constructs a balanced Merkle Tree checkpoint reconciled directly against voter-register counts.

Automated Counting & Turnout Monitoring

  • Conceals per-candidate tallies from all roles—including administrators—until the election officially closes.
  • Provides real-time turnout percentage tracking by department and class during active voting windows.
  • Produces deterministic, re-runnable vote counts verified against the recorded Merkle root prior to result publication, with support for configurable tie-resolution and abstain policies.

User Roles & Operational Responsibilities

Super Admin

Configures institutional governance policies, college settings, and administrator accounts.

Election Admin / Returning Officer

Builds elections, positions, candidate lists, and eligibility filters; monitors turnout; closes voting and publishes verified results.

Student Voter

Authenticates with college credentials and OTP, reviews eligible contests, casts confidential per-position votes, and receives submission confirmation.

Architecture Rules & Edge-Case Resilience

  • Server UTC clock authority governs poll opening and closing regardless of client device timezone settings.
  • Count reconciliation guarantees stored ballot totals match voter-register marks so unauthorized row insertion or deletion triggers an alert.
  • Append-only audit logging captures administrative configuration changes, election extensions, cancellations, and verification runs without linking voter identities to ballot contents.

Confirmed Technology Stack

Backend & Security

  • Java
  • Spring Boot
  • RESTful APIs
  • Spring Security
  • JWT
  • BCrypt

Frontend

  • React.js

Database & Integrity

  • PostgreSQL
  • SHA-256 Ballot Hashing (Random Nonce)
  • Merkle Tree Verification

Messaging & OTP

  • Twilio

Intended Operational & Governance Impact

Intended architectural and operational benefits based on system design goals

  • Eliminates manual ballot counting delays and calculation errors through automated, reproducible tallying.
  • Enforces strict voter eligibility and one-vote-per-position rules transactionally at scale.
  • Protects voter confidentiality via schema separation while supporting cryptographic tamper detection after polls close.
  • Establishes a central, read-only institutional archive of past campus elections and turnout metrics.

Have a similar project in mind?

Schedule an architectural review or scoping discussion with Kode Company's engineering team.

Agile Development Cycles
Full Code Ownership
Dedicated Kerala & Global Engineers
Start a ConversationBrowse Full Portfolio