A DAO's resilience level is determined by the framework, which evaluates the risk of its core governance protections — the weakest one defines the stage.
STAGE 0 [HIGH RISK]
STAGE 1 [MEDIUM RISK]
STAGE 2 [LOW RISK]
pending Criteria
4 fixes to reach Stage 2
Review the current setting and recommended fix for each metric.
Interface Resilience
Current
The Uniswap governance interface on tally has a secure HTTPS connection and is signed with DNSSEC.
Fix
The domain should be protected with standard security certificates, made public by its provider. Ideal security here includes a verified front-end, deployed in an immutable manner, linked to an ENS record by the DAO in a domain like vote.DAO.eth and made available through .limo or .link or equivalent.
Vote Mutability
Current
The DAO does not allow changing votes once they have been cast.
Fix
The ability to change a vote during the voting period must be provided by the DAO. This mechanism allows voters to withdraw their votes and stop a malicious proposal if the governance interface is compromised.
Voting Delay
Current
The Voting Delay is set to 1 day and 19 hours.
Fix
The waiting period between the proposal submission and the snapshot of voting power must be more than two days. In addition, the DAO needs to have an activation plan to contact delegates and stakeholders to mobilize their votes in case of an attack.
Voting Period
Current
The Voting Period is set to 5 days and 6 hours.
Fix
The period between the start and end of a proposal must be at least seven days.
Framework Overview
detailsThese metrics define the DAO's risk level. Select a metric to explore it, or open the full framework for more context.
MEDIUM RISK
LOW RISK