-
Regarding software and operators, we have now sourced a development team to do this. We have gone with the developers behind https://www.privote.live/. This team has a track record of delivering good frontend work and has strong familiarity with the MACI protocol.
-
We now have a commitment of $10,000 from PSE in the EF to support this domain.
-
I could be in favour of keeping this broad or narrowing scope. A broad scope would maximise the range of privacy projects helped. I see the benefit of supporting infra, wallets, journalism etc. That said, it would make collecting impact metrics more difficult, which is an area of improvement for this proposal. We view privacy as a whole a very important problem to solve which aligns with Gitcoin positioning itself to solve Ethereum’s hardest problems, so would initially suggest not going super narrow. Here are some suggestions for narrowing the scope, in order of preference:
a. Privacy infra and wallets
b. Privacy infra
c. Privacy in wallets
Therefore, the scope can be limited to “Privacy Infra and Wallets”. Feel free to provide pushback on this.
- Given the suggestion for narrowing scope above, I would say beyond number of $ donated:
a. Adoption metrics for new privacy features in infra and wallets e.g. dollars deposited, transaction volume, No. of users using the feature. Note that this metric would be feasible for new features funded by the round, but it would be difficult to measure whether funding contributed to existing features.
b. Existing GG24 success measurement framework