DAO v1.1 Public Testing Report

CKB Community Fund DAO
12

Hey @_magicsheep & @Yeti

Let’s also remember that the DAO V1.1 about to be launched on 16 March had:

  1. Centralization issues deriving from Whitelist
  2. A double counting vulnerability, similar to Mod Hack
  3. A SQL injection
  4. Many more issues

Status:

  • 2, 3, 4 have been mostly addressed :white_check_mark:
    1. is currently not addressed :cross_mark:

The tool you just revealed could finally address (part of) 1. Mentioning its existance without releasing leaves 1 still unaddressed.

So to reply:

  • You don’t need to pass my audit and you could choose a less strict auditor.
  • On my side, I will release a public audit of such tool once you open-source it.
  • Keeping the tool closed-source does not help DAO v1.1 positioning.

Allowing a Fair Vote is the basic of Voting Systems.

Not perfection defined as: attacker being able to take control of crucial votes like Meta Rule changes and Stewards elections. See: DAO v1.1 Public Testing Report - #2 by phroi

In good consience, I need to take every possible step to make sure that this doesn’t happen.

Phroi

6 Likes
Personal Opinion on DAO governance