-
Notifications
You must be signed in to change notification settings - Fork 157
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
71fd332
commit 3a0c732
Showing
1 changed file
with
104 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,104 @@ | ||
--- | ||
slug: 2024-team-roadmap | ||
title: New year, new MACI | ||
authors: | ||
name: Sam Richards | ||
title: MACI team lead | ||
url: https://x.com/samonchain | ||
image_url: https://avatars.githubusercontent.com/u/8097623?v=4 | ||
tags: [maci, roadmap] | ||
--- | ||
|
||
Greetings anons, | ||
|
||
Happy 2024 and welcome to the new MACI documentation website and blog! Moving forward, we’ll post our latest project news and development updates here. | ||
|
||
We have a few exciting announcements to share, but first, a quick review: | ||
|
||
## Overview of MACI | ||
|
||
### WTF is MACI? | ||
|
||
**Minimal Anti-Collusion Infrastructure (MACI) is an on-chain voting system which protects privacy and minimizes the risk of collusion and bribery.** | ||
|
||
MACI is a set of smart contracts and zero-knowledge circuits upon which developers can build applications, such as voting applications or quadratic funding platforms. It was originally [proposed by Vitalik Buterin](https://ethresear.ch/t/minimal-anti-collusion-infrastructure/5413) in 2019, then implemented and maintained by community members with support from the [Ethereum Foundation](https://ethereum.foundation/). It's now actively maintained within [Privacy & Scaling Explorations (PSE)](https://pse.dev/). | ||
|
||
Using MACI, **voting is private**, yet **voting results are public**. On-chain votes are encrypted, and no voter can prove how they voted, but final results are published publicly and verified on-chain with cryptographic proofs to prevent censorship, bribery, collusion, fraud, and other nefarious acts common in public polling processes. | ||
|
||
To understand the promise of on-chain voting, start with [Vitalik's post on blockchain voting](https://vitalik.eth.limo/general/2021/05/25/voting2.html). For a general overview, brief history, and context on the importance of MACI, check out the [Release Announcement: MACI 1.0](/blog/maci-1-0-release) by Wei Jie, one of the creators. He also created a helpful [overview of MACI video](https://www.youtube.com/watch?v=sKuNj_IQVYI). Kyle Charbonnet wrote a great [Technical Introduction to MACI 1.0](/blog/maci-1-0-technical-introduction) that provides a walkthrough on how MACI operates. I also recently presented an [introduction to MACI](https://app.streameth.org/zuzalu/zuconnect_hackathon/session/maci_workshop) at Devconnect 2023. | ||
|
||
### MACI Vision | ||
|
||
MACI is a public good that is quickly becoming a core piece of infrastructure for Ethereum-based applications to support on-chain voting while protecting user privacy. | ||
|
||
**Our MACI team’s vision is to build the most secure e-voting solution in the world.** | ||
|
||
Let's hop in to our updates to see how we plan to execute on this bold vision. | ||
|
||
## Project updates | ||
|
||
New year, new team, new roadmap! | ||
|
||
### 1) New team | ||
|
||
Over the past few months we've undergone a lot of changes within MACI's core team. I'd like to take this chance to introduce and welcome our new core members! | ||
|
||
MACI is now maintained and will be continuously be improved by our core team, which consists of: | ||
|
||
- [ctrlc03](https://github.com/ctrlc03) | ||
- [Sam Richards](https://github.com/samajammin) | ||
- [0xmad](https://github.com/0xmad) | ||
- [kittybest](https://github.com/kittybest) | ||
- [crisgarner](https://github.com/crisgarner) | ||
- [aguzmant103](https://github.com/aguzmant103) | ||
- [Vee](https://github.com/Vee-18) | ||
|
||
Now is a great time to mention that **we stand on the shoulders of giants**. Many gigabrains have made heroic advancements in this project - a big "thank you" to all those who have contributed to date! There are too many people to list here, but calling out a few notable players: | ||
|
||
- Vitalik, Barry, Wei Jei for the original idea, architecture, initial implementation, and ongoing guidance | ||
- Recent team members that helped launched our [v1.1.1 release](/blog/maci-v1-1-1-release) and have since moved on: Q, Jei, Chao, and Daehyun | ||
|
||
We're excited to carry the baton forward to bring the vision of MACI to reality! | ||
|
||
### 2) New roadmap | ||
|
||
As a team building in the open source space, we're taking a concerted effort to make our work more accessible and to foster more collaboration and feedback from our community. As part of this work, we're making our core team's roadmap public and will continue to do so. | ||
|
||
[Read our full 2024 roadmap here](/roadmap). | ||
|
||
TL;DR: We'll be focusing most of our time on: | ||
|
||
1. **Developer experience** (documentation, tooling, refactoring) so that MACI is easier for projects to integrate and use | ||
2. **Community engagement** (integration support, hackathon bounties, conference presentations) to more quickly iterate and improve based off feedback | ||
3. [**Quadratic Funding Experiments**](https://qf.pse.dev/) to advance real-world adoption of this technology | ||
|
||
We're happy to share that these efforts are already underway. We expect to release a new and improved version of MACI within the next month. We're exploring MACI integrations and are in discussions with projects including [Gitcoin Grants Stack](https://www.gitcoin.co/grants-stack) and [Optimism RetroPFG](https://community.optimism.io/docs/governance/retropgf-3/#) on how MACI could provide collusion resistance to those systems. Major shoutout to [clr.fund](https://clr.fund/#/) (who became the first production project to integrate MACI back in 2020)! We're actively working with clr.fund to help them upgrade their stack to the latest version of MACI. Expect to see announcements of upcoming MACI-enabled quadratic funding rounds soon! | ||
|
||
### 3) New documentation | ||
|
||
MACI now has a fresh new website, with [revamped documentation](/docs/introduction)! | ||
|
||
We immediately recognized the need for improved educational content about MACI, as it's a complex project with several core components (ZK circuits, Ethereum smart contracts, TypeScript libraries). Whether you're a developer looking to integrate MACI into your application, an open-source developer interested in contributing, or a product manager seeking to understand the high-level mechanics of MACI, we want to hear from you in order to continuously improve your onboarding experience. | ||
|
||
[Please take a look and let us know what you think](/docs/introduction). | ||
|
||
### 4) New community access | ||
|
||
Whether you're interested in contributing to MACI or looking to stay up-to-date on the latest happenings, it's now much easier to stay connected with us and the community. Here are some ways you can keep in touch: | ||
|
||
- [GitHub](https://github.com/privacy-scaling-explorations/maci): open an issue or PR or [join our discussions](https://github.com/privacy-scaling-explorations/maci/discussions) | ||
- [Discord](https://discord.com/invite/sF5CT5rzrR): join the [PSE server](https://discord.com/invite/sF5CT5rzrR) and hop in the `#🗳️-maci` channel to chat with our core team | ||
- [Twitter/X](https://twitter.com/zkmaci): follow our new handle [@zkMACI](https://twitter.com/zkmaci) for updates or to hit us up with feedback | ||
- This website: we'll continue to post updates here (at least 1 blog post every quarter, we promise 🤞)! | ||
|
||
Expect to see announcements around new MACI releases, integrations, event participation (quadratic funding rounds, conferences, hackathons), and grant RFPs. | ||
|
||
We look forward to collaborating closely with our open source community this year! | ||
|
||
## How does that sound? | ||
|
||
Questions? Concerns? Ideas? We’d love to hear from you! | ||
|
||
If there is a feature you think we should work on, or an initiative you'd like to collaborate with us on, please let us know! We welcome input from anyone in the community. | ||
|
||
Onward and upward 🚀 |