How harpreetvirkk/hypervoter works
Project type and purpose
• This is a blockchain-based E-Voting application built on Hyperledger Fabric.
• It comprises two main parts:
• Chaincode (the “smart contract” in Fabric) under chaincode/hypervoter/javascript
• A Node.js application serving static HTML/JS frontends (EC dashboard, voter dashboard, public bulletin)
File structure
• Top-level directories:
• chaincode/hypervoter/javascript – Fabric chaincode implementing vote asset logic
• hypervoter/javascript – Node.js “client” application using Fabric SDK, serves UI
• Shell scripts in hypervoter/ start and teardown the Fabric test network (“basic-network”)
• Static HTML under hypervoter/javascript/public for three user‐facing apps:
– EC-dashboard (Election Commission interface)
– voter-dashboard (voter registration & voting)
– public-bulletin (view results)
• Config files: package.json for npm, ESLint, EditorConfig, .gitignore, .sh for network orchestration
README for additional insights
• HyperLedger Fabric v1.4.6, “basic-network” with:
1. Orderer
2. Certificate Authority
3. 1 Org (org1) with 1 peer
4. CouchDB state database
5. CLI container for admin tasks
• Asset model: voteID→{ownerId, hasVoted}
• Endpoints invoked via Fabric SDK to submit/query transactions