MACI Platform is most useful as the deployable application shell around MACI, not as the privacy protocol itself. The key split is interface + registry / poll contracts + subgraph + coordinator workflow.
The official announcement makes the lineage explicit: MACI Platform began as a fork of EasyRetroPGF, then diverged into a broader platform for secure voting and funding. That makes it a valuable bridge object between retro-funding round kits and MACI-native privacy tooling.
Electorate construction is a first-class control surface. The announcement explicitly lists open participation, EAS attestations, Semaphore groups, Hats, and Zupass credentials as gatekeeping options.
The setup docs show just how much operator authority sits outside the cryptography: coordinator key generation, zkey download, round metadata upload, deploy-config editing, subgraph deployment, admin address selection, EAS schema choice, and network configuration all materially shape a round.
The voting docs show the user-facing flow remains poll-specific and operationally bounded: voters must sign up to MACI, add votes to a ballot, and submit transactions in batches constrained by gas limits.
The results docs make the coordinator dependency concrete: after voting ends, the operator must merge signups and messages, generate proofs, and submit results onchain before the public can inspect them in the interface.
The README’s maintenance warning matters. MACI Platform is no longer maintained, which makes it a poor default recommendation but a very good analytical reference for the middleware layer between MACI and real-world round operations.
Specific source signals worth retaining
Announcement post: clearest statement of intended audience, gatekeeper flexibility, EasyRetroPGF lineage, and the long-run vision of a community-deployable secure-voting platform.
README: clearest compact description of architecture and the explicit notice that the project is no longer maintained.
Setup docs: strongest evidence that MACI Platform is really an operator stack with many configuration chokepoints, not just a privacy-preserving UI.
Voting docs: useful confirmation of participant signup, ballot construction, and submission constraints.
Results docs: strongest concise source for the merge → prove → submit-onchain finalization path.
Why this entry belongs in the corpus
It provides a concrete comparison layer between MACI, clr.fund, and EasyRetroPGF instead of flattening privacy-preserving funding/voting into one brand or protocol.
It helps answer where practical authority sits in private voting rounds: coordinator keys, gatekeeper policy, app deployment, registry approval, subgraph/indexing, and result publication timing.
The reusable insight is that stronger cryptographic privacy does not remove the application-shell control plane; it often makes that layer more important.