Decentralized voting engine for creating and hosting elections. Anyone can create and hold elections, in an open, transparent and trustless manner.
How the system works
An election overseer or administrator can create an election easily by simply passing in the following:
i. An election id
ii. Token name for vote tag
iii. Token symbol
iv. Election title
v. Date and time for start of election in unix time
When the needed data are provided, a new voting instance is created for that election. The details of the election are recorded and accessible. But no voting can hold just yet until the contesting candidates are added and the start election button clicked. The technical parts have been perfectly abstracted out for easy use of the newest web3 user.
Only an election administrator or the overseer can add candidates. Candidates refer to the persons that will be contesting for positions in the election. These candidates will be displayed on that particular election instance where they are added. Each candidate will be displayed on the election page with the following params:
i. age
ii. wallet address
iii. full name
iv. position
v. brief description of the person
Candidates already added can be disqualified from contesting by calling the 'remove_candidate' function which is available as a button in the admin page.
Control election flow
start vote: This function kicks off the voting process. It is only after the administrator starts the process that verified voters can cast their votes. To start the process the administrator will need to pass the time when the voting will end. This is to enable the system to track the duration and capture moments during the voting process.
end vote: This signals the end of the voting process. At the click of this button, no one can cast votes anymore, and the election is basically complete. Therefore this button is only available to the election administrator.
The Sigma voting engine by design is built to resolve the problem of multiple registration by an individual, and by extension, multiple voting. The design thinking was to eliminate voting fraud totally, while keeping the entire process open, transparent and credible. We also plan to add features that will enable diaspora voting too. Voter registration on Sigma begins with verification.
Verification
Verification on the platform was concieved to start as an offchain process that ensures that the voter seeking to get verified is truly a bonafide citizen of the country, club or group hosting the election. We plan to make the system robust that every administrator that set verification parameters and conditions, but for now no such checks have been implemented. For now we make do with this, while we continue to release new updates and also wait for approval from the NCC ministry for access to endpoints for validation using BVN, NIN, Passport and Drivers license.
How to:
Simply click on the particular election to open up the election page, then click on the "verify" button. A wallet modal that pops up select the wallet you have, then sign the verification message. This will get you verified onchain and you are eligible to vote in that election, you will get a non-transferable token which will serve as your voting pass.
Voting
All verified voters for every election instance are eligible to vote in that election. On an election page, simply tap on vote button and then sign the transaction in your wallet. If the process is successful you'll see an update on the election display banner, after the transaction has been confirmed on chain, the number of votes for each candidate will be updated and the winner will be updated in real time. In the next release, we are working on a proof of participation NFT. After voting you get a "voted" NFT minted to your wallet which serves as a proof that you participated in the election.
Voting on Sigma is as open as daylight. Once a voter successfully casts a vote, the election core functions are invoked to update the leaderboard. It's safe to say that winner emerges in real time as the voting proceeds, and whoever is on top at the end becomes the winner of the contest. There's no need for personnels to count or collate elections manually.
We will keep building and updating the algorithms of the system as we monitor how elections are being conducted and managed by the administrators. If the systems gets abused or if administrators starts playing shady games, we will implement features that will give more administrators power to oversee the process and make decisions based on a consensus. (For now moderator do not interfer in the processes).
In the hallowed spirit of open source that is the tradition of web3 builders, the Sigma team is making this entire codebase open source.
Make sure you have scarb and other necessary tools installed. If you are new to Starknet, you can get started with the tools here: https://book.starknet.io/ch02-01-basic-installation.html
i. Clone this repository into your local machine: git clone https://github.com/OkoliEvans/Sigma_stark.git && cd Sigma_stark
ii. Run scarb build to build the program, and then you can continue on your machine.
We highly appreciate and welcome pull requests or issues from everyone that will help to improve the system, we apreciate especially PRs that will pinpoint bugs in the smart contracts, and of course in the other codes as well :)
Factory Contract deployed on Starknet: 0x03d499bbe9a1f95e49c03275dd772b84f6aa41d529a4e931c449999e65e58789
SMX token deployed on Starknet: 0x062df1f543b13e0da5abd2a90910fa7a2fe44c6a5f70849b298c6b2a219783a1
Note: SMX token is a limited transaction token only meant for gatekeeping on voting systems, and as such does not have any monetary value.