DAOs And On-Chain Governance
You learn what a decentralized autonomous organization is, how it makes decisions with votes and delegation, and how it manages shared funds. You also study the common ways DAO governance fails so you can design around them.
You Will Be Able To
- Define a DAO and list the parts it is built from.
- Trace a proposal from idea to executed on-chain transaction.
- Compare token voting, delegation, and multisig control.
- Describe how a treasury is held and spent safely.
- Diagnose plutocracy, voter apathy, and governance attacks in a real example.
What A DAO Is
A DAO, short for decentralized autonomous organization, is a group that holds shared resources and makes decisions through rules written in smart contracts. Members do not rely on a single manager. Instead, a program on a blockchain counts votes and, when a proposal passes, can move funds or change settings without anyone's extra permission.
The word 'autonomous' is easy to overstate. People still write proposals, argue in forums, and run the projects that the DAO funds. What the code automates is narrow and important: who may vote, how votes are counted, and what happens to the money when a vote ends. Think of a DAO as an organization whose bylaws are executable.
In week 4 you studied consensus, where a network agrees on the state of a ledger. A DAO adds a second layer on top. The chain agrees on what happened. The DAO decides what the group wants to do next.
The Parts Of A DAO
Most DAOs share a small set of components. Learning them makes any new DAO easy to read, because only the details change from one project to the next.
Membership defines who can take part. It may come from holding a token, owning a non-transferable badge, or being approved by existing members. The week 6 identity tools matter here, since a DAO that wants one person to hold one vote needs some way to check personhood.
- Membership: a token, a badge, or an invitation.
- Proposals: a written request with executable actions attached.
- Voting: a rule for counting support within a time window.
- Execution: a contract that performs the passed actions.
- Treasury: the funds the DAO controls.
- Off-chain space: a forum and chat where discussion happens.
Proposals And Voting
A typical proposal moves through stages. Someone posts an idea in a forum and collects feedback. The author then submits a formal proposal on chain, including the exact transactions to run if it passes. A voting period opens, often lasting several days. Members cast votes for, against, or abstain. If the proposal reaches a quorum (a minimum amount of participation) and enough support, it passes. A timelock then delays execution for a short while, so members can react if something looks wrong.
Token voting is the most common rule: one token equals one vote. Its strength is that it is simple and hard to fake. Its weakness is that influence follows money. Other rules exist, such as one person one vote with an identity check, or reputation that grows with contributions. Week 9 explores these alternatives in depth.
Votes can happen on chain, where each vote is a transaction and pays a fee, or off chain, where members sign messages that cost nothing and a trusted tool counts them. Off-chain voting is cheaper and raises participation. On-chain voting gives stronger guarantees because the result executes automatically. Many DAOs combine the two: a free signal vote first, then a binding on-chain vote.
- Discussion
- Draft proposal
- Voting period
- Timelock delay
- Execution
The timelock gives people time to react before money moves.
Delegation
Most token holders cannot read every proposal. Delegation lets a holder assign their voting power to another address, called a delegate, who votes on their behalf. The holder keeps the tokens and can change delegate at any time. Compound and Uniswap use designs of this kind, and the Ethereum standard ERC-20 Votes records voting power over time to support it.
Delegation works like a representative democracy. It concentrates attention in people who study proposals, and it makes quorum easier to reach. It also creates a new risk, because a few popular delegates can hold large blocks of power. Healthy DAOs publish delegate statements, track delegate voting history, and make it simple to re-delegate.
A variation is liquid democracy, where delegation can chain: A delegates to B, and B delegates to C. Members can also vote directly on any issue and override their delegate. This keeps expertise available without giving anyone permanent authority.
Treasuries
The treasury is where the stakes are highest. It may hold the DAO's native token, stablecoins, and other assets. The safest pattern keeps funds in a smart contract wallet that only releases money when a passed proposal calls it, or when a small group of signers approves.
A multisig wallet requires, for example, three of five signers to approve every transaction. Safe, formerly known as Gnosis Safe, is a widely used implementation. Multisigs suit small teams, day to day payments, and emergency responses. Their trade-off is that the signers are a small trusted group. Many DAOs therefore use a multisig for operations with spending limits and require full votes for large moves.
Good treasury practice is plain. Keep a public budget. Publish regular reports. Separate working funds from long-term reserves. Hold part of the reserves in assets that do not collapse with the DAO's own token. Pay contributors through clear grants or streams that can be paused when milestones are missed.
How DAOs Fail
Studying failure teaches more than studying success. Several patterns repeat across DAOs.
Plutocracy appears when voting power follows tokens. A few large holders can pass any proposal, and smaller members stop believing their votes matter. Voter apathy follows: turnout is often low, since reading proposals takes time and one vote rarely changes the outcome. Low turnout makes it cheaper for an organized minority to dominate.
Governance attacks exploit the rules. In a flash loan attack, an attacker borrows many tokens for one transaction, votes, and returns them. Delaying snapshots to a past block and adding timelocks defend against this. In 2016, The DAO, an early investment fund on Ethereum, lost a large amount of funds to a flaw in its contract code, which led to a contested network split. The event showed that code errors and governance decisions become tangled when money is at stake.
Other failures are social. Proposals can be vague. Core teams may keep real control through hidden keys. Contributors burn out. Disputes lack a clear process. A DAO is a human institution first, and code only records what the humans agreed.
- Plutocracy: money decides outcomes.
- Voter apathy: low turnout hands power to a few.
- Governance attacks: flash loans, rushed proposals, hidden keys.
- Social breakdown: unclear roles and unresolved disputes.
| Failure | What goes wrong | Common mitigation |
|---|---|---|
| Plutocracy | Votes follow money | Delegation, caps, other voting rules |
| Apathy | Few people vote | Delegates, simple ballots |
| Rule attack | Rules are gamed | Timelocks, audits, snapshots |
| Treasury theft | Keys or code abused | Multisig, limits |
Each row is a pattern to look for in any DAO you study. Source: Course synthesis
Design Habits For Healthier Governance
A few habits improve almost any DAO. Start small, with a clear purpose, since a DAO that tries to govern everything often governs nothing. Use a forum stage before voting so that proposals arrive polished. Set quorum and thresholds that fit real turnout instead of copying another DAO's numbers.
Add safety rails: a timelock before execution, a guardian role that can pause a proven emergency, and spending limits. Publish the powers of every special role, along with the plan to remove those powers over time. Offer onboarding, because a member who cannot understand a proposal will not vote.
Measure what matters. Track turnout, the share of power held by the top ten addresses, and the number of proposals that reach a result. These numbers show the health of the DAO in the same way that revenue shows the health of a shop. Next week you will see mechanisms that respond directly to plutocracy and Sybil attacks.
Key Terms
- DAO
- A group that holds shared funds and decides through rules enforced by smart contracts.
- Proposal
- A formal request, often with executable transactions, that members vote on.
- Quorum
- The minimum amount of participation needed for a vote to count.
- Delegation
- Assigning your voting power to another address that votes for you.
- Timelock
- A delay between a passed vote and its execution that gives members time to react.
- Multisig
- A wallet that needs approval from several signers before it moves funds.
- Treasury
- The pool of assets a DAO controls.
- Plutocracy
- Rule by the wealthy, seen in DAOs when voting power follows token holdings.
- Flash loan attack
- Borrowing a large amount of tokens within one transaction to win a vote or exploit a rule.
Exercise: Audit A Real DAO
- Pick one DAO with a public governance page, such as Uniswap, Compound, Gitcoin, or ENS.
- Find its governance forum and read three recent proposals. Note the stages each one went through.
- Open its voting tool (for example Tally or Snapshot) and record turnout and the result for those three proposals.
- Find the top ten delegates or holders and estimate the share of voting power they hold together.
- Locate the treasury address and note its approximate size and how funds are released.
- Write a one page report naming one strength, one weakness, and one change you would propose.
Further Reading
- DAOs are not corporations: where decentralization in autonomous organizations matters, Vitalik Buterin, vitalik.eth.limo blog, 2022
- Moving beyond coin voting governance, Vitalik Buterin, vitalik.eth.limo blog, 2021
- Compound Governance documentation, Compound Labs, docs.compound.finance
- Gnosis Safe (Safe) documentation, Safe, docs.safe.global
- The Network State, Balaji Srinivasan, 2022 (chapter on governance and founders)