MACI primary sources

Reviewed: 2026-05-10 UTC

Core protocol framing

https://maci.pse.dev/
- Official site and documentation entrypoint; frames MACI as public-good infrastructure for private onchain voting.
https://maci.pse.dev/docs/introduction
- Best single-page explanation of MACI’s core mechanism: encrypted votes, zk-verified tallying, receipt-freeness, collusion resistance, and the trusted-coordinator model.

https://maci.pse.dev/roadmap
- Most useful source for where the project is headed now: custom voice credits, custom gatekeeping, relayer support, coordinator service, DAO integrations, and explicit coordinator-decentralization research.

https://raw.githubusercontent.com/privacy-scaling-explorations/maci/main/README.md
- Shows MACI as a multi-package middleware stack spanning circuits, contracts, cryptography, SDK, subgraph, coordinator service, and relayer.
https://github.com/privacy-scaling-explorations/maci
- Canonical codebase for the actively maintained protocol.

https://raw.githubusercontent.com/privacy-scaling-explorations/maci-platform/main/README.md
- Useful because it states plainly that MACI Platform is no longer maintained, clarifying the difference between the protocol and the older full-stack application shell.
https://github.com/privacy-scaling-explorations/maci-platform
- Repository for the deprecated platform layer.

MACI’s distinctive mechanism is receipt-free voting with zk-verified tally correctness, not generic “private governance.”
The trusted coordinator is the critical control surface. MACI improves privacy and anti-bribery, but does not erase coordinator trust.
The roadmap makes clear that operational services — relayer, coordinator service, and DAO-tooling integrations — are part of the project’s real product surface.
MACI is best compared against governance stacks where voter privacy, voter admission, tally publication, and operator trust are split across different layers instead of collapsed into one generic “voting app.”