Blockchain-Based Secure Voting System: A Research Study

This research project studies the application of blockchain technology to electronic voting systems, focusing on the properties of immutability, transparency, and voter verifiability that a distributed ledger can offer over traditional centralized voting databases.

A prototype is implemented using a permissioned blockchain (Hyperledger Fabric) where each vote is recorded as a signed transaction, and voter identity is decoupled from vote content using a commitment scheme to preserve ballot secrecy while still allowing each voter to verify their vote was correctly recorded.

The study evaluates the system against key criteria from election-security literature — coercion resistance, double-voting prevention, and auditability — and benchmarks transaction throughput and latency to assess feasibility for elections of varying scale, concluding with a discussion of current limitations for large-scale public elections.

Detailed Project Description

Blockchain-Based Secure Voting System: A Research Study digitises the day-to-day records and workflows of an organisation so data is stored once, retrieved instantly and reported accurately.

How It Works
1. Role-based login separates admin, staff and end users.
2. Each module (records, bookings, transactions, reports) provides full CRUD operations with validation.
3. Data lives in a relational database with proper relationships between entities.
4. Reports and search views summarise the stored information.

Technology Roles
- Blockchain
- Hyperledger Fabric
- Cryptography
- Smart Contracts

Implementation Steps
1. Define requirements and draw the ER / class diagram and screen flow.
2. Set up the environment (Hyperledger Fabric, Docker, Node.js) and create the project skeleton.
3. Design the database schema / data model and seed it with sample data.
4. Implement the core modules with validation and role-based access where needed.
5. Build the user interface and connect it to the backend / data layer.
6. Test each module (unit + manual), fix edge cases and secure inputs (SQL injection, XSS, auth).
7. Prepare documentation, screenshots and a demo build.

Key Features
- Role-based access
- CRUD modules
- Search and filters
- Reports / export
- Validation and error handling

Expected Output
On completion the student will have a multi-user application with organised records and printable/exportable reports.

Deliverables
- Complete source code with comments
- Database schema / data model and screen flow
- Project report with screenshots and results
- Demonstration-ready build