Minimal Anti-Collusion Infrastructure (MACI) is an on-chain voting protocol which protects privacy and minimizes the risk of collusion and bribery.
MACI blog, resources, and documentation for developers and integrators can be found here: https://maci.pse.dev/
We welcome contributions to this project. Please join our
Discord server (in the #🗳️-maci
channel) to discuss.
Below you can find a list of the packages included in this repository.
package | npm | tests |
---|---|---|
maci-circuits | ||
maci-cli | ||
maci-contracts | ||
maci-core | ||
maci-crypto | ||
maci-domainobjs | ||
maci-integrationTests |
The base branch of the project is dev
, which is used for ongoing development.
This project uses tags for releases. View all MACI releases.
To contribute to MACI, create feature/fix branches, then open PRs into dev
. Learn more about contributing.
For installation and local development instructions, please see our installation docs.
This repository is organized as Lerna submodules. Each submodule contains its own unit tests.
audit
: Documentation surrounding the audit performed on v1crypto
: low-level cryptographic operations.circuits
: zk-SNARK circuits.contracts
: Solidity contracts and deployment code.domainobjs
: Classes which represent high-level domain objects particular to this project.core
: Business logic functions for message processing, vote tallying, and circuit input generation throughMaciState
, a state machine abstraction.cli
: A command-line interface with which one can deploy and interact with an instance of MACI.integrationTests
: Integration tests which use the command-line interface to perform end-to-end tests.
Please refer to the testing documentation for more information.
Run docker build -t maci .
to build all stages.
To run a specific build step docker build --target circuits -t maci .
Note: a cached version of builder
job must be on your system prior as it relies on existing artifacts
CI pipeline ensures that we have automated tests that constantly validate. For more information about pipeline workflows, read our CI documentation.