Skip to content

Commit

Permalink
Merge branch 'dev' into refactor/mp-tally-subsidy
Browse files Browse the repository at this point in the history
  • Loading branch information
kittybest committed Jan 11, 2024
2 parents e5743ba + a96ad6a commit 0808323
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 10 deletions.
16 changes: 8 additions & 8 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"prettier": "^3.1.1",
"prettier-plugin-solidity": "^1.3.1",
"solhint": "^4.1.1",
"typedoc": "^0.25.4",
"typedoc": "^0.25.7",
"typedoc-plugin-markdown": "^3.17.1",
"typescript": "^5.3.3"
},
Expand Down
3 changes: 2 additions & 1 deletion website/blog/2021-10-12-maci-v1.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,8 @@ A suggested upgrade to MACI is to use ElGamal re-randomisation for anonymity of

We are working on tooling that makes it easier for coordinators to interface with deployed contracts and manage tallies for multiple polls. This will allow users to generate proofs and query inputs and outputs from existing circuits through an easy-to-use API. We hope that this will drive more adoption of MACI and offload the need for bespoke infrastructure.

###Trusted setup
### Trusted setup

Unlike other ZKP projects, MACI does not have an official trusted setup. Instead, we hope to assist teams implementing MACI in their applications to run their own trusted setup. For instance, clr.fund recently completed a trusted setup (on a previous version of MACI) for a specific set of circuit parameters. Other teams may wish to use a different set of parameters on MACI 1.0, which calls for a different trusted setup.

## Conclusion
Expand Down

0 comments on commit 0808323

Please sign in to comment.