DAO Governance Calculator

Calculate voting power, quorum, and proposal thresholds

Your Voting Power

Quorum Requirements

Proposal Threshold Check

Uniswap
Quorum: 4%
Threshold: 2.5M UNI
Compound
Quorum: 4%
Threshold: 65K COMP
Aave
Quorum: 10%
Threshold: 100K AAVE
ENS
Quorum: 5%
Threshold: 1M ENS

Vote Outcome Simulator

DAO Governance FAQ

I have 0.1% voting power - does my vote matter?

More than you think. Most DAO votes pass or fail by small margins because turnout is low (often 5-15% of supply votes). Your 0.1% could be 1-2% of actual votes cast. Plus, close votes happen - Uniswap's BNB deployment passed by ~0.4%. Every vote counts when participation is low.

Can whales control DAO decisions?

In token-weighted voting, yes - large holders have more power. A16z famously controls significant UNI voting power. But: 1) Whales often disagree with each other. 2) Reputation matters - unpopular votes hurt credibility. 3) Some DAOs use quadratic voting to reduce whale dominance. It's a real problem without perfect solutions.

Should I delegate or vote myself?

Delegate if: you don't have time to research proposals, you trust someone's judgment, you want to support active community members. Vote yourself if: you have strong opinions, the proposal directly affects you, you enjoy governance. You can delegate and still override on specific votes in most DAOs.

What happens to my tokens when I vote?

Nothing - they stay in your wallet. Voting is usually just signing a message (off-chain) or calling a contract (on-chain). No lock-up unless the DAO specifically requires it. Some DAOs do have vote-escrow models (like veCRV) where you lock tokens for more voting power, but that's opt-in.

Why do proposals need timelocks?

Security. The timelock (usually 24-48 hours) between vote passing and execution gives everyone time to react. If a malicious proposal somehow passes, users can exit before it executes. Also lets devs catch bugs. Compound's timelock saved them from a $80M bug in 2021 - they fixed it before execution.

Snapshot vs on-chain voting?

Snapshot: Free (gas-less), fast, but not binding - requires trusted multisig to execute. Good for temperature checks and non-critical votes. On-chain (Governor contracts): Costs gas, slower, but trustless execution - code runs automatically if vote passes. Most DAOs use both: Snapshot for discussion, on-chain for final decisions.

Recommended Tools

💬 User Comments

Share your thoughts and feedback about this tool

Please login to leave a comment

No comments yet. Be the first to share your thoughts!

×

Rate this tool

Select a rating