@maci-protocol/website 0.0.0-ci.2df0337 → 0.0.0-ci.2ff3d96

package/LICENSE

@@ -1,7 +1,6 @@
 MIT License
 
-Copyright (c) 2020 Barry WhiteHat, Kendrick Tan, Kobi Gurkan, Kirill Goncharov
-Cory Dickson, Han Jian, Chih-Cheng Liang, and Koh Wei Jie
+Copyright (c) 2025 Ethereum Foundation
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/blog/2024-02-28-maci-v1.2.0.md

@@ -94,7 +94,7 @@ Following the successful completion of our [MACI trusted setup ceremony](https:/
 
 To accomplish this, we'll leverage the tooling of [P0tion](https://github.com/privacy-scaling-explorations/p0tion), which helps to streamline and automate Groth16 phase2 ceremonies.
 
-We'll update this page after the ceremony completes to include the production-ready zkey artifacts. In the meantime, the artifacts for v.1.1.1 can be found on our [website](/docs/security/trusted-setup), and the [`tallyVotes`](https://github.com/privacy-scaling-explorations/maci/blob/dev/circuits/circom/tallyVotes.circom) artifacts can still be used in production.
+We'll update this page after the ceremony completes to include the production-ready zkey artifacts. In the meantime, the artifacts for v.1.1.1 can be found on our [website](/docs/security/trusted-setup), and the [`tallyVotes`](https://github.com/privacy-scaling-explorations/maci/blob/main/circuits/circom/tallyVotes.circom) artifacts can still be used in production.
 
 ## Get Involved
 
@@ -106,7 +106,7 @@ For those looking to contribute directly, report bugs, or offer feedback, our [G
 
 For practical implementation insights, review our docs as well as the [clr.fund](https://github.com/clrfund/monorepo/) and [QF](https://github.com/quadratic-gardens/qfi) repositories as reference implementations. Both are quadratic funding implementations, a mechanism which otherwise is highly susceptible to collusion and bribery. Most notably, clr.fund is already working on integrating MACI v1.2.0, after having used v0.x until now. You can follow their development effort under this [GitHub branch](https://github.com/clrfund/monorepo/tree/feat/maci-v1).
 
-For any other questions or feedback, please reach out to us via [PSE's Discord](https://discord.com/invite/sF5CT5rzrR), in our [`#🗳️-maci` channel](https://https//discord.com/channels/943612659163602974/1164613809730748507). We're excited to connect and collaborate with you!
+For any other questions or feedback, please reach out to us via [PSE's Discord](https://discord.com/invite/sF5CT5rzrR), in our [`#🗳️-maci` channel](https://discord.com/channels/943612659163602974/1164613809730748507). We're excited to connect and collaborate with you!
 
 ## References
 

package/blog/2024-08-10-maci-v2.md

@@ -84,7 +84,7 @@ For those looking to contribute directly, report bugs, or offer feedback, our [G
 
 For practical implementation insights, review our docs as well as the [clr.fund](https://github.com/clrfund/monorepo/), [Allo Stack with MACI](https://github.com/gitcoinco/MACI_QF), and [maci-platform](https://github.com/privacy-scaling-explorations/maci-platform) repositories as reference implementations. The first two integrations are quadratic funding implementations, a mechanism which otherwise is highly susceptible to collusion and bribery.
 
-For any other questions or feedback, please reach out to us via [PSE's Discord](https://discord.com/invite/sF5CT5rzrR), in our [`#🗳️-maci` channel](https://https//discord.com/channels/943612659163602974/1164613809730748507). We're excited to connect and collaborate with you!
+For any other questions or feedback, please reach out to us via [PSE's Discord](https://discord.com/invite/sF5CT5rzrR), in our [`#🗳️-maci` channel](https://discord.com/channels/943612659163602974/1164613809730748507). We're excited to connect and collaborate with you!
 
 ## References
 

package/blog/2025-03-21-roadmap-2025.md

@@ -26,7 +26,7 @@ We are happy to announce that we completed the work on developing a service to a
 
 This server exposes a REST API, as well as some Websocket endpoints (for proof generation only). We soon will publish a detailed guide on how to use, and how to integrate it via its SDK -stay tuned for a separate blog post.
 
-For anyone interested in the code, you can find it [here](https://github.com/privacy-scaling-explorations/maci/tree/dev/apps/coordinator).
+For anyone interested in the code, you can find it [here](https://github.com/privacy-scaling-explorations/maci/tree/main/apps/coordinator).
 
 ### MACI Offchain voting support
 

package/blog/2025-08-18-maci-aragon-plugin.md

@@ -0,0 +1,107 @@
+---
+slug: maci-aragon-plugin
+title: MACI Aragon Plugin
+description: A MACI plugin for Aragon OSx to enable private voting in DAOs
+authors:
+  - name: ctrlc03
+    title: MACI former team lead
+    url: https://x.com/ctrlc03
+    image_url: https://avatars.githubusercontent.com/u/93448202?v=4
+  - name: John Guilding
+    title: MACI team lead
+    url: https://x.com/john_guilding
+    image_url: https://pbs.twimg.com/profile_images/1629144990914945024/C6_xsK78_400x400.jpg
+  - name: NicoSerranoP
+    title: MACI team member
+    url: https://x.com/NicoSerranoP
+    image_url: https://avatars.githubusercontent.com/u/38594836?v=4
+tags: [voting, security, anonymity, Aragon, MACI, development]
+excerpt: "A MACI plugin for Aragon OSx to enable private voting in DAOs"
+---
+
+Hey Anon,
+
+Welcome to another MACI blogpost. Today we are going to be looking at a voting plugin we have been developing to work with the [Aragon OSx stack](https://www.aragon.org/osx).
+
+As mentioned in our [latest roadmap blog post](https://maci.pse.dev/blog/2025-Roadmap#2025---what-will-we-focus-the-rest-of-the-year), our team decided to focus on supporting governance projects by integrating with tooling providers such as [Aragon](https://www.aragon.org/). Look out for further announcements over the next month. We're working on some exciting additions to the roadmap to accelerate private governance on Ethereum.
+
+So why integrate MACI with Aragon OSx? Our thesis is simple: \***\*private voting will increase voter participation and protect those voting. It will also lead to more honest and accurate outcomes as people can vote more honestly.\*\***
+
+Current public voting systems create barriers to honest participation. Voters face social pressure, fear of retaliation, and concerns about how their choices might affect future opportunities. Private voting removes these barriers, enabling DAOs to capture the true preferences of their communities.
+
+We chose to integrate with Aragon because their OSx platform provides an excellent foundation for custom DAO governance, and as a reputable team building in the open, they're the perfect partner for this integration.
+
+### The real cost of public voting
+
+While transparency is often celebrated in crypto, public voting creates serious barriers to honest participation that threaten the legitimacy of DAO governance.
+
+**Fear of retaliation keeps voters silent.** Large token holders can pressure smaller voters by threatening to exclude them from future opportunities, airdrops, or partnerships. When voting records are public, retaliation becomes easy to execute, leading many to abstain rather than risk consequences.
+
+**Social pressure distorts genuine preferences.** Voters often wait to see how others vote before casting their own ballot, leading to herding behavior that doesn't reflect genuine preferences. Some even [say](https://x.com/LefterisJP/status/1921562225333916094) governance voting has devolved into a game of politics. The "follow the whale" mentality and politics involved undermine the democratic ideals DAOs strive for.
+
+**Vote verification enables problematic markets.** When votes are public, it also creates conditions where governance power can be openly [traded](https://www.tronweekly.com/arbitrum-vote-buying-scandal-how-5-eth-shook/), as buyers can verify they received what they paid for.
+
+**Public real time results can enable whales intervention.** If the votes are public and visible in real time while the voting period is happening, whales (or users through token loans) could influence the decision by using their voting power to overpower the community decision.
+
+### Why MACI
+
+MACI (Minimal Anti Collusion Infrastructure) is a private voting protocol that aims to reduce collusion and coercion with receipt freeness - this makes it the logical next step for DAOs that really care about the problems highlighted above.
+
+In more detail, every vote is encrypted and can only be decrypted for tallying, by a trusted entity referred to as the coordinator. Voters can override their votes at any point during the voting period, and thus without a clear receipt for their vote, they are not able to prove beyond reasonable doubt that they actually voted for an option. This discourages bribers from buying votes and other voters from attempting to collude.
+
+While the coordinator can decrypt votes, they cannot produce an incorrect tally or censor votes, thanks to zero knowledge proofs and smart contracts.
+
+For more details about MACI and how it works, we recommend reading our other blogposts such as this introductory [article](https://maci.pse.dev/blog/maci-for-beginners) and our comprehensive documentation [website](https://maci.pse.dev/docs/introduction).
+
+### How does Aragon OSx work
+
+Aragon OSx is a smart contract framework that works on EVM compatible chains. DAOs can easily deploy custom governance stacks using Aragon OSx, and can benefit from several plugins to extend their functionality over time. This plugin architecture allows DAOs to customise their governance without rebuilding from scratch.
+
+A plugin is a smart contract with custom governance logic, limited in scope, and with single-purpose logic that can be used to extend OSx-based organisations. Examples include [token voting](https://docs.aragon.org/token-voting/1.x/index.html) and [multisig](https://docs.aragon.org/multisig/1.x/index.html), and now.. privacy-preserving voting through MACI.
+
+### How does the MACI plugin work
+
+The plugin allows DAO members to create new proposals by calling a smart contract function: `createProposal`. The function checks that the caller has enough governance tokens - this minimum amount is set by the DAO at deployment time. The plugin creates a new MACI poll that hosts the encrypted private votes for that particular proposal.
+
+The plugin then captures the current block number (minus one) as a snapshot to determine voter eligibility. Once they decide to vote, they can register their interest to vote via their DAO frontend (in MACI's context we call this process _join a poll_), and their voting power is determined by their token balance at the time of proposal creation. Voters can use their real wallet holding their tokens to register themselves by publishing a MACI public key created on their devices. After that, the voter can use any wallet to submit an encrypted message containing the registered public key and their selected option.
+
+Voters are then able to vote using their full voting power by choosing one of the options available, which at this time are Yes, No or Abstain. Voting is completely handled by MACI’s smart contracts, therefore voters do not actually ever interact with the DAO plugin.
+
+Once the proposal ends, MACI’s backend service (the [coordinator service](https://github.com/privacy-scaling-explorations/maci/tree/dev/apps/coordinator)), starts processing the votes, and generate zk-SNARK proofs to be validated on chain. Voters can be sure of the correct execution thanks to those proofs verifying on chain. Finally, the results are uploaded and the proposal execution can be triggered.
+
+The full flow can be observed in the diagram below:
+
+![new-flow-maci](https://hackmd.io/_uploads/Sktza18Xge.png)
+
+A proposal execution can range from transferring funds, calling a function on the DAO smart contract itself, calling out an external contract (for instance to initiate a token swap), or setting up a new plugin.
+
+An example proposal shown below, with a proposal requesting users to vote on whether they are happy to convert part of the DAOs USDC reserves to ETH.
+
+![dao1](https://hackmd.io/_uploads/rk7C3dHXll.png)
+
+The familiar voting interface makes privacy seamless - voters simply select their choice without needing to understand the cryptography running behind the scenes.
+
+![voting1](https://hackmd.io/_uploads/H1TR3OHXxg.png)
+
+### Implementation Considerations
+
+- **Network Support:** Currently compatible with all EVM chains such as Ethereum, Arbitrum, Optimism, and some zkEVM networks such as Scroll and Linea. [Here](https://maci.pse.dev/docs/supported-networks/) is a list of all compatible networks.
+- **Timeline:** Vote processing is not immediate due to the need to process votes offchain and to generate zk-SNARK proofs of correct execution. The time it takes to process votes can be reduced by using more powerful hardware.
+- **Reliance on trusted coordinator:** MACI in its current form relies on a trusted coordinator entity which can decrypt the votes - this is an automated piece of software that can run on a server or a Trusted Execution Environment for more security. The team is working on decentralising the coordinator entity and will soon begin working on an upgraded version that uses homomorphic encryption and threshold encryption to distribute the responsibilities across multiple entities. Please note that while the coordinator can see the votes, they cannot censor users nor provide incorrect results.
+- **Costs:** Using MACI can be more costly than traditional blockchain-based voting. While these costs are negligible in layer 2 networks, costs can increase in Ethereum mainnet. Please refer to our [costs](https://maci.pse.dev/docs/supported-networks/costs) section in the documentation website for more details on current benchmarks.
+
+### Next steps
+
+As DAOs evolve from experimental communities to serious organisations managing significant resources, governance systems must evolve too. The current landscape presents an ideal opportunity for DAOs to pioneer MACI, thus we are looking for forward-thinking DAOs to pilot MACI’s governance plugin - especially those facing challenges around voter participation, sensitive decision-making, or community pressure. Ready to be among the first? Reach out at [maci@pse.dev](mailto:maci@pse.dev) or join our [Discord](https://discord.com/invite/sF5CT5rzrR). Governance on Ethereum needs a privacy shake up, stay in the loop if you're interested in hearing what else the team has been working on.
+
+### References and resources
+
+- [MACI repo](https://github.com/privacy-scaling-explorations/maci)
+- [MACI voting plugin](https://github.com/privacy-scaling-explorations/maci-voting-plugin-aragon)
+- [MACI -Aragon sample frontend](https://github.com/privacy-scaling-explorations/maci-aragon-osx-gov-app)
+- [Aragon OSx](https://github.com/aragon/osx)
+- [Aragon docs](https://docs.aragon.org/)
+
+## Acknowledgements
+
+Thanks to the Aragon team for review.

package/blog/2025-09-05-maci-coordinator-service.md

@@ -0,0 +1,167 @@
+---
+slug: maci-coordinator-service
+title: MACI Coordinator Service
+description: Announcing our coordinator service for MACI
+authors:
+  - name: ctrlc03
+    title: MACI former team lead
+    url: https://x.com/ctrlc03
+    image_url: https://avatars.githubusercontent.com/u/93448202?v=4c
+  - name: NicoSerranoP
+    title: MACI team member
+    url: https://x.com/NicoSerranoP
+    image_url: https://avatars.githubusercontent.com/u/38594836?v=4
+tags: [voting, security, anonymity, MACI, coordinator]
+excerpt: "A MACI plugin for Aragon OSx to enable private voting in DAOs"
+---
+
+Hey Anon,
+
+Welcome back to our MACI blog.
+
+Today, we are excited to officially announce something we have referenced frequently: the Coordinator Service.
+
+If you ever used MACI, for instance to run a Retroactive Public Goods Funding (RPGF) or Quadratic Funding (QF) round, you might be aware of how tedious it was to operate. The manual process of running scripts to finalise a round and calculate the tally as well as all of the zk-SNARK proofs could require some time and technical expertise. All these steps had to be done in the terminal and you needed to be familiar with MACI's inner workings to understand the process.
+
+**Fear no more - the coordinator service is here to make your life easier.**
+
+## The vision: MACI for everyone
+
+Our goal is ambitious, yet simple: **completely eliminate the need for any technical knowledge to use MACI**. No more terminal commands, no more manual proof generation, no more complex scripts. Just configure once, run inside a Docker container on your server, and enjoy the full power of MACI's privacy-preserving voting infrastructure.
+
+## Technical implementation
+
+The service was built with the following technologies for reliability and scalability:
+
+- TypeScript for type-safe, maintainable code
+- Nest.js framework for enterprise-grade architecture
+- REST API for standard CRUD operations
+- WebSocket endpoints for real-time updates during intensive computations
+- MACI SDK package to have all the logic and functions ready to use
+- Docker-ready for simple deployment anywhere
+
+The core functionalities of the service are as follows:
+
+- Deploy a MACI [subgraph](https://github.com/privacy-scaling-explorations/maci/tree/dev/apps/coordinator/ts/subgraph) to query on-chain data easily
+- [Deploy](https://github.com/privacy-scaling-explorations/maci/tree/dev/apps/coordinator/ts/deployer) the MACI smart contracts, including polls
+- [Finalise](https://github.com/privacy-scaling-explorations/maci/tree/dev/apps/coordinator/ts/proof) polls by processing votes and tallying the results
+- [Schedule](https://github.com/privacy-scaling-explorations/maci/tree/main/apps/coordinator/ts/scheduler) polls for automatic finalization when the voting period ends
+- [Health](https://github.com/privacy-scaling-explorations/maci/tree/main/apps/coordinator/ts/health) endpoint to check everything is setup and working
+
+Let's dive into more details in the following sections.
+
+### Subraph deployment
+
+The endpoint to deploy a subgraph requires some configuration in the `.env` file, as well as an HTTP request to the endpoint responsible for this `https://coordinator.maci.vote/v1/subgraph/deploy`. Make sure you have an account in [The Graph](https://thegraph.com/studio/) to setup your `.env` file before starting the coordinator service.
+
+### Contracts deployment
+
+There are two endpoints in this module: deploy maci (`https://coordinator.maci.vote/v1/deploy/maci`) and deploy poll (`https://coordinator.maci.vote/v1/deploy/poll`). This will take care of all contracts deployment and configuration. It is worth pointing out that you should read the [coordinator service API documentation](https://coordinator.maci.vote/api) and the [MACI guides](https://maci.pse.dev/docs/core-concepts/workflow) to understand the roles of each contract (MACI, poll, policy, initialVoiceCredit).
+
+You can deploy one MACI contract (and its internal smart contracts) that will have one gatekeeper policy (e.g. FreeForAll) for all voters to sign up. After that you can deploy multiple polls with different settings (start date, end date, gatekeeper policy, etc). Each voter will have to join each poll to be eligible to participate in. The poll's gatekeeper will check the voter eligibility to join the poll.
+
+### Finalisation
+
+This step includes three separate actions:
+
+1. Merge - calculate the state merkle tree root and store a commitment to its root (`https://coordinator.maci.vote/v1/proof/merge`)
+2. Process - fetch all smart contracts events to reconstruct the state locally and process all votes. This includes decrypting votes, checking validity, and finally tallying them. zk-SNARK proofs are generated for each batch of votes processed (`https://coordinator.maci.vote/v1/proof/generate`)
+3. Submit - submitting all of the zk-SNARK proofs on chain to prove that the poll was processed correctly. Finally, submit the tally results on chain so that they can be seen by everyone (`https://coordinator.maci.vote/v1/proof/submit`)
+
+We chose to separate each action into its own endpoint to avoid long-running computations that could lead to network errors or timeouts.
+
+### Schedule
+
+After finishing up the finalisation module, we realized that it would be a lot easier for users to create polls and schedule the finalization process. This removes the need for users to manually call the finalization endpoints described above.
+
+1. To schedule a deployed poll you can use `https://coordinator.maci.vote/v1/scheduler/register`.
+2. To check if a poll is scheduled you can use `https://coordinator.maci.vote/v1/scheduler/status`
+3. To delete a scheduled poll you can use `https://coordinator.maci.vote/v1/scheduler/delete`
+
+## How to use
+
+### Run it from source
+
+1. Clone the MACI repository: [https://github.com/privacy-scaling-explorations/maci](https://github.com/privacy-scaling-explorations/maci)
+2. Install dependencies and build the project
+
+```bash
+pnpm install
+pnpm run build
+```
+
+3. Download the zkeys for the coordinator
+
+```bash
+pnpm run download-zkeys:ceremony:coordinator
+```
+
+4. Generate a coordinator MACI keypair. Remember to store those values for later.
+
+```bash
+pnpm run generate-maci-keypair
+```
+
+5. Move to the coordinator service directory
+
+```bash
+cd apps/coordinator
+```
+
+6. Configure your `.env` file. Make sure to configure it with your own secure values. The coordinator MACI private key from the previous step should be set here
+
+```bash
+cp .env.example .env
+```
+
+7. Start the service
+
+```bash
+pnpm run start
+# or
+pnpm run start:prod
+```
+
+### Run it with Docker
+
+1. Clone the MACI repository: [https://github.com/privacy-scaling-explorations/maci](https://github.com/privacy-scaling-explorations/maci)
+2. Go inside the project directory
+
+```bash
+cd maci
+```
+
+3. Build the docker image and run the container
+
+```bash
+# Build docker
+docker compose -f apps/coordinator/docker-compose.yml build
+
+# Run container detached
+docker compose -f apps/coordinator/docker-compose.yml up -d
+```
+
+## Usage notes
+
+1. You can check out the documentation while the service is running in [http://localhost:3001/api](http://localhost:3001/api)
+
+2. We have a [e2e.deploy.test.ts](https://github.com/privacy-scaling-explorations/maci/blob/main/apps/coordinator/tests/e2e.deploy.test.ts) file that performs a complete process: deployment, voting and finalization. You can use it to guide yourself.
+
+## Future work
+
+We are researching about different cryptographic methods to decentralize the coordinator. The idea is to eliminate reliance on a single centralized service for finalizing polls. A group of people would be able to spin up their own coordinator services and finalize the poll in a multi-party computation. For more info check out our MACI v4 research.
+
+## Conclusion
+
+The MACI Coordinator Service represents a significant leap forward in making MACI accessible to everyone. Whether you're running a small community poll or a large-scale funding round, the coordinator service handles the complexity so you can focus on what matters - empowering your community with private, secure voting.
+
+Ready to get started? Head over to our documentation and deploy your first MACI round today!
+
+Please reach out if you would like to integrate the service into your frontend.
+
+## References
+
+- [MACI repo](https://github.com/privacy-scaling-explorations/maci)
+- [Sample frontend](https://github.com/privacy-scaling-explorations/maci-aragon-osx-gov-app) using the coordinator service
+- [Code examples](https://github.com/privacy-scaling-explorations/maci-aragon-osx-gov-app/blob/main/plugins/maciVoting/contexts/CoordinatorContext.tsx)
+- [Documentation](https://maci.pse.dev/docs/category/coordinator-service)

package/docusaurus.config.ts

@@ -46,7 +46,7 @@ async function getConfig(): Promise<Config> {
             routeBasePath: "docs/",
             sidebarPath: "./sidebars.ts",
             editUrl: ({ versionDocsDirPath, docPath }) =>
-              `${GITHUB_URL}/edit/dev/website/${versionDocsDirPath}/${docPath}`,
+              `${GITHUB_URL}/edit/dev/apps/website/${versionDocsDirPath}/${docPath}`,
             remarkPlugins: [remarkMath],
             rehypePlugins: [rehypeKatex],
             includeCurrentVersion: false,
@@ -59,7 +59,7 @@ async function getConfig(): Promise<Config> {
           blog: {
             showReadingTime: true,
 
-            editUrl: ({ blogDirPath, blogPath }) => `${GITHUB_URL}/edit/dev/website/${blogDirPath}/${blogPath}`,
+            editUrl: ({ blogDirPath, blogPath }) => `${GITHUB_URL}/edit/dev/apps/website/${blogDirPath}/${blogPath}`,
             remarkPlugins: [remarkMath],
             rehypePlugins: [rehypeKatex],
             onUntruncatedBlogPosts: "ignore",
@@ -204,9 +204,15 @@ async function getConfig(): Promise<Config> {
         phpLoader: "matomo.php",
         jsLoader: "matomo.js",
       },
+      mermaid: {
+        theme: { light: "neutral", dark: "forest" },
+      },
     } satisfies Preset.ThemeConfig,
+    markdown: {
+      mermaid: true,
+    },
+    themes: ["@docusaurus/theme-mermaid"],
   };
-
   return config;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maci-protocol/website",
-  "version": "0.0.0-ci.2df0337",
+  "version": "0.0.0-ci.2ff3d96",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -21,30 +21,31 @@
     "types": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@docusaurus/core": "^3.7.0",
-    "@docusaurus/preset-classic": "^3.7.0",
-    "@docusaurus/theme-classic": "^3.7.0",
-    "@docusaurus/theme-common": "^3.7.0",
-    "@easyops-cn/docusaurus-search-local": "^0.49.1",
+    "@docusaurus/core": "^3.8.1",
+    "@docusaurus/preset-classic": "^3.8.1",
+    "@docusaurus/theme-classic": "^3.8.1",
+    "@docusaurus/theme-common": "^3.8.1",
+    "@docusaurus/theme-mermaid": "^3.8.1",
+    "@easyops-cn/docusaurus-search-local": "^0.52.1",
     "@mdx-js/react": "^3.1.0",
     "clsx": "^2.1.1",
     "docusaurus-plugin-image-zoom": "^3.0.1",
     "docusaurus-plugin-matomo": "^0.0.8",
     "gray-matter": "^4.0.3",
     "prism-react-renderer": "^2.4.1",
-    "react": "^19.1.0",
-    "react-dom": "^19.1.0",
+    "react": "^19.1.1",
+    "react-dom": "^19.1.1",
     "rehype-katex": "^7.0.1",
     "remark-math": "^6.0.0"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "^3.7.0",
-    "@docusaurus/tsconfig": "^3.7.0",
-    "@docusaurus/types": "^3.7.0",
-    "@types/node": "^22.14.0",
-    "@types/react": "^19.1.0",
+    "@docusaurus/module-type-aliases": "^3.8.1",
+    "@docusaurus/tsconfig": "^3.8.1",
+    "@docusaurus/types": "^3.8.1",
+    "@types/node": "^24.2.0",
+    "@types/react": "^19.1.9",
     "ts-node": "^10.9.2",
-    "typescript": "^5.8.3"
+    "typescript": "^5.9.2"
   },
   "browserslist": {
     "production": [
@@ -59,7 +60,7 @@
     ]
   },
   "engines": {
-    "node": ">=18.0"
+    "node": "20"
   },
-  "gitHead": "5402e150a9069c30d2722295409526a4434cedc7"
+  "gitHead": "15b078262657bdf19c45585e21799cbf63d8b2b0"
 }

package/src/pages/roadmap.md

@@ -8,14 +8,14 @@ description: An outline of the 2024 MACI team & product roadmap
 _This public roadmap is part of our core team's efforts to make our work more accessible and to foster more collaboration from our open source community. We plan to re-assess & iterate on our roadmap over time, and will update this document when we do._
 
 :::info
-This document aims to outline the 2024 MACI roadmap. Our roadmap is under constant discussion and evolution (e.g. see our [Q1](/blog/2024-team-roadmap) and [Q2](/blog/2024-q2-roadmap) updates) but we try our best to maintain this page to provide a high-level overview. Please join the conversation in our [latest GitHub discussion](https://github.com/privacy-scaling-explorations/maci/discussions/1381) if you have feedback!
+This document aims to outline the 2025 MACI roadmap. Our roadmap is under constant discussion and evolution (e.g. see our [high level 2025 roadmap](/blog/2025-roadmap) updates) but we try our best to maintain this page to provide a high-level overview. Please join the conversation in our [discord server](https://discord.com/invite/sF5CT5rzrR) if you have feedback!
 
-**Last updated: 2024-04-16**
+**Last updated: 2025-04-23**
 :::
 
 ## Team description
 
-The MACI core team is a small collaborative engineering team building various projects within [Privacy & Scaling Explorations (PSE)](https://pse.dev/). Our sustained focus is on MACI: an on-chain voting protocol that provides greatly increased collusion resistance & privacy. We also allocate a significant portion of our time to support the practical adoption of this technology by supporting community leaders to run democratic governance and public funding initiatives, like Quadratic Voting (QV), Quadratic Funding (QF), and Retroactive Public Goods Funding (RPGF) grant rounds.
+The MACI core team is a small collaborative engineering team building various projects within [Privacy & Scaling Explorations (PSE)](https://pse.dev/). Our sustained focus is on MACI: an on-chain voting protocol that provides greatly increased collusion resistance & privacy. We also allocate a portion of our time to support the practical adoption of this technology by supporting community leaders to run democratic governance and public funding initiatives, like Quadratic Voting (QV), Quadratic Funding (QF), and Retroactive Public Goods Funding (RPGF) grant rounds.
 
 ## MACI mission & vision
 
@@ -29,8 +29,8 @@ Short term, our vision is to empower developers to build with MACI to create col
 
 1. ~~2021: MACI integrated by an ecosystem project~~ (✅, [clr.fund](https://github.com/clrfund/monorepo/))
 2. ~~2023: MACI integrated by a PSE project~~ (✅, [QF](https://github.com/privacy-scaling-explorations/qf))
-3. 2024: MACI integrated by an additional external project
-4. 2025: MACI used by multiple DAOs for governance applications & QF integrations
+3. ~~2024: MACI integrated by an additional external project~~ (✅, [PriVote](https://github.com/PriVote-Project), [Gitcoin](https://github.com/gitcoinco/MACI_QF))
+4. 2025: MACI used by multiple DAOs for governance applications
 5. 2028: MACI used in smaller municipal elections (counties, provinces, etc)
 6. 2030: MACI used in national elections
 
@@ -38,110 +38,69 @@ Short term, our vision is to empower developers to build with MACI to create col
 
 1. ~~2021: release MACI v1.0~~ (✅)
 2. ~~2023: build technical feasibility for 10K concurrent voters on the platform~~ (✅)
-3. 2024 Q1: release MACI v1.2, with revamped documentation & educational resource
-4. 2026: build technical feasibility for 100K concurrent voters on the platform
-5. 2028: build technical feasibility for 1M concurrent voters on the platform
+3. 2024:
 
-# 2024 workstreams
+- ~~Q1: release MACI v1.2, with revamped documentation & educational resource~~ (✅)
+- ~~Q3: release MACI v2.0, with cleaner code and improved UX~~ (✅)
 
-_To achieve our mission, we’re focused on 4 major workstreams that comprise our roadmap._
+4. 2025: release MACI v3.0, with new features for a more scalable and flexible platform
+5. 2026: build technical feasibility for 100K concurrent voters on the platform
+6. 2028: build technical feasibility for 1M concurrent voters on the platform
 
-## 1) MACI Developer Experience (DX)
+# 2025 workstreams
 
-~_50% of team’s total bandwidth_
+In 2025, we are focusing on several initiatives to support the practical adoption of MACI.
 
-We believe that MACI is only useful to the extent that people use MACI & build on MACI.
+## 1) MACI v3.0
 
-Despite the power of MACI, not a single project has yet integrated MACI v1.x in a production environment. We view this as a failure, and we want to fix this. **The goal of this workstream is to make MACI as easy to understand and easy to integrate as possible.**
+This new version comes with features that have been requested in the past, such as polls being more customisable, in terms of voice credits assigned to voters, and gatekeeping mechanisms.
 
-### Initiatives within this workstream:
+At a high level, the new features/improvements are:
 
-- Implement & release a MACI v1.2 ([#856](https://github.com/privacy-scaling-explorations/maci/issues/856))
-  - Refactor the codebase for improved quality, readability & modularity
-  - Add code comments (with [TypeDoc](https://typedoc.org/) & [NatSpec](https://docs.soliditylang.org/en/latest/natspec-format.html)) to improve productivity
-  - Improve tooling (e.g. cross-platform support) for ease of integration & performance
-- Improve/create documentation for developer onboarding & education
-  - Revamp documentation stack (via Docusaurus) with versioning & additional resources
-  - Voter & coordinator guides to understand full poll lifecycle
-- Build app templates & tutorials that can serve as reference implementations
+- Custom voice credits per poll
+- Custom gatekeeping per poll
+- Replacement of vote merkle trees for more efficient hash-chains
+- Offchain voting via MACI's relayer service
 
-**References**
+## 2) Coordinator Service
 
-- [MACI v1.2 Refactoring Plan](https://github.com/privacy-scaling-explorations/maci/issues/856)
-- [MACI development team sprint board](https://github.com/orgs/privacy-scaling-explorations/projects/40)
-- [MACI v1.1.1 refactor milestone](https://github.com/privacy-scaling-explorations/maci/milestone/5)
+The coordinator service is a service to automate MACI coordinator functionality. This includes:
 
-## 2) MACI Community Engagement
+- Contract deployment
+- Subgraph deploying
+- Proof generation
+- Proof and results submission
 
-_~15% of team’s total bandwidth_
+This service exposes a REST API, as well as some Websocket endpoints (for proof generation only). Our goal is to release an efficient and easy to use service that can be used by any application that builds atop of MACI.
 
-We want to proactively support adoption of MACI. **We’ll create an open source community where integrations & contributions are actively encouraged!**
+## 3) Integration with DAO's tooling provider
 
-This workstream relates closely to improving DX but focuses on areas that will require active maintenance, support & engagement from our team vs. improving code, documentation & educational resources that will be available online 24/7/365.
+As an effort to support DAO governance, and help solve their issues with bribery and collusion, MACI is focusing on integrating with DAO's tooling providers.
 
-The hope here is that close interactions with integration developers & Ethereum community members will help us gather insightful user feedback so that we iterate faster to improve MACI as a product. We’ll be rolling out an agile scrum development workflow that should allow us to rapidly respond to input from the community to guide our roadmap & product direction.
+To start with, MACI is integrating with [Aragon](https://aragon.org/) by building a voting [plugin](https://github.com/privacy-scaling-explorations/maci-voting-plugin).
 
-### Initiatives within this workstream:
+In the future, we plan to continue working with other partners such as [Agora](https://www.agora.xyz/), and help them offer DAOs secure and private voting.
 
-- Allocate team bandwidth to be available to respond to the community
-  - Support MACI integrations (starting with [clr.fund](http://clr.fund/) v1.x integration)
-  - Revamp GitHub repo maintenance ([MACI GH processes](https://github.com/privacy-scaling-explorations/maci/issues/757))
-  - Establish & respond to public channels ([Discord](https://discord.com/invite/sF5CT5rzrR), [Twitter](https://twitter.com/zkMACI))
-- Proactively engage with the ecosystem to identify collaboration opportunities (conference talks, hackathon bounties, social media)
-- Update our development processes to quickly react to user needs & input
+## 4) Coordinator decentralisation
 
-## 3) Quadratic Funding Experiments
+It's no secret that one of MACI long standing issues has having a centralised coordinator. They are able to see all of the votes in cleartext, which allows them to collude with bribers themselves, as well as voters. As we look to tackle use cases such as DAO governance where large quantities of money are involved in proposals, we need to ensure that collusion between the coordinator and voters/bribers is reduced. This can be accomplished in several ways:
 
-_~30% of team’s total bandwidth_
+- Use Multi Party Computation (MPC)
+- Use Homomorphic Encryption (HE)
+- Use a Trusted Execution Environment (TEE)
 
-We’re building technical infrastructure, operational expertise & a network of communities to create a scalable way to enable community organizers to run QF rounds. The mission of our QF project has been to serve as a reference implementation on how to integrate MACI as well as support the practical adoption of this community-funding technology.
-
-[Read more about our QF initiatives here](https://qf.pse.dev/about).
-
-### 2024 goal
-
-- Help run 12 QF/QV rounds
-
-### Initiatives within this workstream:
-
-- Build an evaluation framework of QF rounds, to increase our sophistication around how we measure success
-- Landscape analysis of QF & capital-allocation projects to better understand how our efforts fit in within the broader ecosystem
-- Update & expand our [QF website](https://qf.pse.dev/), with public launch to generate inbound interest
-- Explore community collaboration opportunities (running QF rounds)
-- Exploring project collaboration opportunities (supporting MACI/QF integrations)
-
-**References**
-
-- [GitHub](https://github.com/privacy-scaling-explorations/qf)
-- [Website](https://qf.pse.dev/)
+We plan to research the best approach and start the implementation within the year.
 
 ## Future R&D
 
 While not prioritized as an upcoming workstream, we think it’s worth calling out important areas of research & development that we’re excited to work on in the future:
 
-### MACI Coordinator Service
-
-- The primary responsibility of the Coordinator Service will be to:
-  - offload and automate the tasks performed by the human coordinator
-  - minimize proving time by parallelizing SNARK proof generation and making MACI easier to adopt
-- [GitHub repo](https://github.com/privacy-scaling-explorations/maci-coordinator)
-
-### QF stack
-
-- To serve as a reference implementation on how to integrate MACI as well as support the practical adoption of this community-funding technology.
-- Improvements
-  - Support QF (as of now only supports QV functionality)
-  - Make it easier for operators to run rounds
-  - Make it easier for end users to use
-- [GitHub repo](https://github.com/privacy-scaling-explorations/qf)
-
 ### MACI improvements
 
-- Unconditional Voter Privacy (e.g. [ElGamal Key Change Mechanism](https://github.com/privacy-scaling-explorations/maci/issues/796))
 - Scaling explorations, like SNARK Folding Schemes (e.g. [Nova integration](https://github.com/privacy-scaling-explorations/maci/issues/904))
 - Different matching mechanisms (e.g. [Group Wise Matching in Quadratic Funding](https://github.com/privacy-scaling-explorations/maci/issues/905))
-- Gas-less MACI for voters
-- Gas efficiency
+- Re-implementation of previously removed features such as [Topup](https://github.com/privacy-scaling-explorations/maci/issues/1384) and [Subsidy](https://github.com/privacy-scaling-explorations/maci/issues/1348)
+- [Benchmarks](https://github.com/privacy-scaling-explorations/maci/issues/1197) for the whole stack
 
 ## Feedback