Protect Privacy: Payments and Governance & Voting

Hey everyone :wave: Community Development will be involved in a privacy-focused virtual hackathon. Edited:

Thanks for everyone’s ideas!

The Gitcoin Privacy Hackathon is LIVE! We’re looking for proof of concepts for privacy in two tracks: Governance & Voting and Payments. 8,000 Dai up for prizes. Tons of ideas and use cases to get you started:

  1. Some ideas from Privacy in Payments (More in the link):
  • How to transfer Dai from the protocol in such a way that it goes to its intended recipient, but where others are not able to see the eventual destination address.
  • Ability to generate “clean addresses”: a simple way for users to send funds to a new address without revealing their assets or past purchasing history.
  1. Some ideas for Privacy in Governance & Voting (More in the link):
  • Tooling for the darkspell mechanism described in MIP15: Dark Spell Mechanism. How do you share information and manage ownership with community actors without compromising the security and trust of the protocol?
  • A way to provably stake MKR on an outcome, a specific smart contract construct, a MIP, etc, without publicly revealing the address of the staker.
4 Likes

Hi @rawhaus,

good initiative this.
Private invoicing is one thing.
Clean addresses would be pure heaven. Both for DAI and MKR. I guess Tornado.Cash could to some degree clean DAI, but not MKR.
Would it be possible to have a clean Maker governance voting record?
Why: imagine a scenario in the not too distant future where various factions of Delegated Voting has turned non-constructive and are only flinging dirt at each other. In that case it is better to have a more anonymous governance voting as it makes it easier to concentrate on the actual issues at hand and not on who-voted-what earlier.

3 Likes

Anything related to privacy would be wonderful! Both of your examples would be great! But isn’t this something that needs to be handled at the base layer within the ethereum protocol? I’ve heard you can do layer 2 privacy solutions, but I don’t really understand how you keep privacy with a transparent base layer.

Hi @befitsandpiper

You can’t keep the privacy, other than the actual identification of the real user, if available to the database. You can identify information, and recache it or rewrap it into another solution from the same contract on-chain i would say.

1 Like

Some ideas / possibilities below. I’m not sure how essential any of these are with regards to governance right now, though.

  1. Optionally voting without revealing the voting addresses. This would include the cold wallet used to deposit MKR in the Chief (not sure if this is even possible.) And the hot wallet used to vote (might be more possible?)

  2. Voting without revealing the poll option / executive voted for. Pretty sure this is also quite difficult.

  3. How to attach a pseudonymous identity to a voting address without revealing the true identity covered by the pseudonymous one. (This is more in the realm of general op-sec.)

  4. How to combine the above with delegation? How to ensure delegates are safe from influence but still credible and trustworthy?

  5. Specifically any tooling that may be of beenfit to the darkspell mechanism described here: MIP15: Dark Spell Mechanism.

  6. How to transfer DAI from the protocol in such a way that it goes to its intended recipient, but where governance is not able to see the eventual destination address.

  7. A method to pay DAI into the protocol in such a way that the primary address of the sender is not visible.

  8. (Speculative) A way to provably stake MKR on something (an outcome, a specific smart contract construct, a MIP, etc) without publically revealing the address of the staker.

3 Likes

The Gitcoin Privacy Hackathon is LIVE! We’re looking for proof of concepts for privacy in two tracks: Governance & Voting and Payments. 8,000 Dai up for prizes. Tons of ideas and use cases to get you started:

  1. Some ideas from Privacy in Payments (More in the link):
  • How to transfer Dai from the protocol in such a way that it goes to its intended recipient, but where others are not able to see the eventual destination address.

  • Ability to generate “clean addresses”: a simple way for users to send funds to a new address without revealing their assets or past purchasing history.

  1. Some ideas for Privacy in Governance & Voting (More in the link):
  • Tooling for the darkspell mechanism described in MIP15: Dark Spell Mechanism. How do you share information and manage ownership with community actors without compromising the security and trust of the protocol?

  • A way to provably stake MKR on an outcome, a specific smart contract construct, a MIP, etc, without publicly revealing the address of the staker.