Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.

L2 Dai is not censorship-resistant #83

Open
brianmcmichael opened this issue May 19, 2022 · 2 comments
Open

L2 Dai is not censorship-resistant #83

brianmcmichael opened this issue May 19, 2022 · 2 comments

Comments

@brianmcmichael
Copy link
Contributor

In the L2 Dai implementation, governance has the ability to burn Dai in any address.

This enables Dai censorship of a user's wallet by governance, which means that we can't make the claim that L2 Dai is censorship-resistant as it is on L1.

This needs a broad team, and potentially MKR holder, discussion.

if (from != msg.sender && wards[msg.sender] != 1) {

@krzkaczor
Copy link
Contributor

krzkaczor commented May 20, 2022

As long as the bridge is governance controlled, what's the difference between:

  1. Governance removing liquidity from L1Escrow
  2. Governance diluting L2DAI by minting an arbitrary amount of DAI
  3. Governance burning users' funds (what you brought up here)

In my opinion, there is not too much difference between these after all. The solution is always the same -- removing governance control over the construct. This will be possible to do (and always was planned) once we are done with moving MCD to L2.

@hexonaut
Copy link
Contributor

To be fair the point about burning is unique as single addresses can be targeted which is not the case with minting or stealing from everyone. Agree overall this is not a problem though as we will remove governance's ability to access the erc20 dai contract once MCD is deployed. At that point it should only be mint/burn able through the daiJoin contract same as L1.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants