Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
electusvoting
Advanced tools
git clone https://github.com/chaitanyapotti/Voting.git
cd Voting
npm install
The protocol level contracts use OpenZeppelin extensively for referencing standard EIPs. Electus Voting utilizes OpenZeppelin's implementations for EIP-165. Please refer to OpenZeppelin's github page here
To use with Truffle, first install it and initialize your project with truffle init
.
npm install -g truffle
mkdir myproject && cd myproject
truffle init
After installing either Framework, to install the Voting library, run the following in your Solidity project root directory:
npm init -y
npm install --save electusvoting
After that, you'll get all the library's contracts in the node_modules/electusvoting/contracts
folder. You can use the contracts in the library like so:
import 'electusvoting/contracts/poll/IPoll.sol';
contract MyContract is IPoll {
...
}
#Linting To lint solidity, use
node ./node_modules/solhint ./contracts/poll/BasePoll.sol
For linting Solidity files you need to run Solhint with one or more Globs as arguments. For example, to lint all files inside contracts directory, you can do:
solhint "contracts/**/*.sol"
To lint a single file:
solhint contracts/MyToken.sol
To disable linting for next line, use
// solhint-disable-next-line
Unit test are critical to the Electus Voting framework. They help ensure code quality and mitigate against security vulnerabilities. The directory structure within the /test
directory corresponds to the /contracts
directory. OpenZeppelin uses Mocha’s JavaScript testing framework and Chai’s assertion library. To learn more about how to tests are structured, please reference Voting's Testing Guide.
To run all tests:
Start ganache-cli or other testrpc
npm run test
truffle test
Electus Voting is meant to provide secure, tested and community-audited code, but please use common sense when doing anything that deals with real money! We take no responsibility for your implementation decisions and any security problem you might experience.
The core development principles and strategies that Electus Voting is based on include: security in depth, simple and modular code, clarity-driven naming conventions, comprehensive unit testing, pre-and-post-condition sanity checks, code consistency, and regular audits.
If you find a security issue, please email chaitanya.potti@gmail.com.
For details about how to contribute you can check the contributing page
FAQs
Standard implementation and interface for Voting
We found that electusvoting demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.