What a DAO actually automates
A DAO (decentralized autonomous organization) uses smart contracts to encode rules for proposing changes, voting on them and executing the result — commonly changing protocol parameters, upgrading contracts or spending from a treasury. The 'autonomous' part is partial: humans still write proposals and often control admin keys during the earliest stages, but execution of a passed vote can be enforced purely by code.
- •Governance token balance usually determines voting weight.
- •Proposals are typically posted off-chain for discussion before an on-chain vote.
- •Treasuries are held in a multisig or governance-controlled contract.
Voting mechanics
A common flow: a proposal is submitted, a snapshot of token balances is taken at a specific block (preventing borrow-and-vote attacks), token holders vote for a set period, and if quorum and majority thresholds are met, the proposal queues for execution. Off-chain signaling tools record sentiment cheaply; on-chain votes carry binding weight but cost gas.
- •Quorum: minimum participation required for a vote to count.
- •Snapshot block: fixes voting power before the vote starts.
- •Delegation: holders can assign their voting power to another address without transferring tokens.
Timelocks as a safety valve
Even after a proposal passes, execution is usually delayed by a timelock contract — often 24-72 hours — before it can act on the protocol. This gives users a window to notice a malicious or buggy proposal and exit before it takes effect, acting as a check against both governance attacks and rushed decisions.
Governance risks
Low voter turnout can let a small, motivated group push through proposals. Flash-loan-funded voting was a real early attack vector before snapshot-block voting became standard. Plutocracy — where large holders dominate outcomes — is an open design tension, since token-weighted voting inherently favors whoever holds the most tokens.