---
title: "DAO Governance Models: Voting vs Multisig"
description: "DAO governance models compared for product teams: token voting, delegation, reputation and multisig, the control you keep, and why low turnout breaks them."
canonical_url: "https://builderscamp.com/guides/glossary/dao-governance-models"
date_published: "2026-09-27"
date_modified: "2026-09-27"
author: "Andre Albuquerque"
publisher: "Builders Camp"
guide_class: "glossary"
---

# What are DAO governance models?

**TL;DR:** DAO governance models trade control against participation: token-weighted voting is open but concentrates power in large holders, reputation-based systems resist buying influence but are harder to run, and multisigs are fast and safe but put a few signers in charge. Low turnout breaks all of them, so choose the model by which failure your product can least afford.

A DAO governance model decides who can change the product and how fast. For a product team, that is a roadmap question dressed up as a political one. The most useful single finding comes from a 2025 review in ACM's Distributed Ledger Technologies journal by [Jungnickel and colleagues](https://dl.acm.org/doi/10.1145/3777416): "reputation and share-based models can mitigate the centralization seen in token-based systems, though all models suffer from low member engagement."
So the choice is not between a good model and bad ones. It is between different ways of failing, and which failure your product can survive.

## What are the main DAO governance models?

Five patterns cover most live DAOs. Each answers the same two questions differently: how does someone get voting power, and how much control does the core team keep?

| Model | How voting power is acquired | Control kept by core team | Participation it invites | Typical failure mode |
|---|---|---|---|---|
| Token-weighted voting | Buying or earning tokens | Low once tokens are spread | Open to any holder | Whales decide, most holders never vote |
| Delegated token voting | Holders lend votes to delegates | Low to medium | Active delegates, passive holders | A few delegates hold most of the power |
| Share-based membership | Proposing to join, usually with a tribute, and receiving shares | Medium | Smaller, committed group | Slow growth, gatekeeping |
| Reputation-based | Earned through contribution, not transferable | Medium | Contributors only | Hard to measure contribution fairly |
| Multisig control | Appointed signers | High | Very little direct participation | Signers become a de facto board |

Real protocols often combine them: token voting for decisions, a timelock before execution like the one Compound documents, and a multisig or security council that can pause the system in an emergency.

## How does token-weighted voting work, and where does it fail?

In token-weighted voting, one token is one vote, so power follows holdings. [ethereum.org's DAO page](https://ethereum.org/en/dao/) gives MakerDAO as the example: MKR is widely available on decentralised exchanges and anyone can buy into having voting power over the protocol. That openness is the appeal, since anyone can join governance without asking.

The failure is concentration. Vitalik Buterin wrote in [Moving beyond coin voting governance](https://vitalik.eth.limo/general/2021/08/16/voting3.html) that a governance token "is a bundle of two rights that are combined into a single asset": an economic interest in the protocol and the right to govern it. A holder who only cares about price can still vote on product changes, and a large enough holder can decide them alone.

Delegation is the usual patch. [Compound's governance docs](https://docs.compound.finance/v2/governance/) let holders delegate votes to themselves or any address, and set concrete thresholds: an address needs 25,000 COMP delegated to create a proposal, and a proposal needs a majority and at least 400,000 votes in favour, then waits 2 days in a timelock. Delegation raises participation on paper while concentrating real power in a few active delegates.

## How is reputation-based governance different from token voting?

Reputation-based governance ties voting power to contribution instead of capital. ethereum.org states that "Reputation cannot be bought, transferred or delegated; DAO members must earn reputation through participation." That removes the whale problem at the source: nobody can buy their way into control.

The cost moves to measurement. Someone has to decide what counts as contribution and how much each kind is worth, which is itself a governance decision. Reputation also does not transfer ownership, so contributors get a say without an economic stake. For a product team, reputation governance fits a community of builders and researchers better than a protocol whose users mostly hold and trade.

## When does multisig control make sense for a product team?

A multisig requires several signers to approve a transaction before it executes. ethereum.org describes DAO funds living in a wallet shared by 5 to 20 active community members who are trusted and usually publicly known, and who execute the result of a community vote. [ethereum.org's smart contract docs](https://ethereum.org/en/developers/docs/smart-contracts/) add the security argument: multisigs divide responsibility so that losing a single private key does not lead to an irreversible loss of funds.

Multisig control is the honest choice early. When a protocol is weeks old, the team is still fixing bugs and the token is held by a few people, pretending that token holders run things adds risk without adding legitimacy. Say publicly who the signers are, what they can do, and what would trigger handing more control to holders.

## Why is low turnout the failure mode every DAO model shares?

Low turnout turns every model into rule by whoever shows up. The Jungnickel review found low member engagement across all the models it examined, and argued this suggests an over-reliance on direct democracy. When few people vote, a small coordinated group can pass a proposal, and a necessary fix can struggle to reach quorum.

Compound's 2021 incident shows why this matters to a product manager. Proposal 62 updated a core contract and, [as The Register reported](https://www.theregister.com/2021/10/01/compound_crypto_bug/), a bug then distributed roughly $90m worth of COMP that should not have gone out. Governance had approved the change, and governance was also the only route to fix it.

The fixes are product work: delegation so passive holders still count, cheap or free voting for small holders, notifications when a vote touches someone's position, and a quorum set against the supply that realistically votes. Treat voter turnout like any engagement metric and design for it.

## How should a product team choose a DAO governance model?

Choose by the failure you can least afford. Four questions settle most cases:

- **What is at stake if a bad proposal passes?** If users hold large deposits, keep a timelock and an emergency pause even under token voting, and accept the centralisation that implies.
- **Who actually understands the product?** If the people with context are contributors rather than holders, reputation or delegated voting to named experts beats one-token-one-vote.
- **How fast do you need to ship?** If the product changes weekly, a multisig with a public plan for handing over control is more honest than governance theatre.

Whichever you pick, write down what would make you change it. A governance model that cannot evolve becomes the thing users complain about in every forum thread, and managing that community is [stakeholder management](https://builderscamp.com/guides/glossary/stakeholder-management) with a public vote attached.

## Is coin voting the wrong model altogether?

The strongest objection to everything above is that token voting may be broken beyond patching. Buterin argues in the same essay that "we need to move beyond coin voting as it exists in its present form," and suggests limiting what coin votes can decide, mixing in non-financial signals such as proof of participation, and changing voting rules so voters carry more skin in the game.

That critique is persuasive for high-stakes protocol decisions. It is less decisive for a product team that needs a working process this quarter. The practical takeaway is to limit what token votes control: let holders set direction and parameters within bounds, and keep contract-level changes behind review, timelocks and a security process.

## How does Builders Camp approach DAO governance?

Builders Camp's [Web3 Product Management bootcamp](https://builderscamp.com/bootcamps/web3-pm) runs for 2 weeks with 4 live sessions and 8 self-paced microlessons, directed by Andre Albuquerque, and lists incentives and token mechanics and ecosystem strategy among its published topics. Its practical challenge puts you in the middle of a governance vote that passed with low participation; the [web3 governance case study exercise](https://builderscamp.com/guides/challenges/web3-pm-governance-crisis-response) describes it in full. For the wider role, read [what a web3 product manager does](https://builderscamp.com/guides/path/web3-product-manager), and for how governance choices show up on screen, see [web3 UX challenges](https://builderscamp.com/guides/other/web3-ux-challenges).

## Frequently asked questions

### What are the main DAO governance models?

Token-weighted voting, where voting power follows token holdings; delegated token voting, where holders lend their votes to representatives; share-based membership, where shares carry votes and ownership; reputation-based membership, where power is earned through contribution and cannot be bought; and multisig control, where a small set of signers executes decisions.

### Which DAO governance model is the most decentralised?

None of them by default. A 2025 review in ACM Distributed Ledger Technologies found that reputation and share-based models can reduce the concentration seen in token-based systems, and that all the models it examined suffer from low member engagement. A model is only as decentralised as the people who actually vote.

### What is a whale in DAO governance?

A holder, or a delegate, with enough tokens to decide votes on their own or with a few allies. In token-weighted voting, power follows holdings, so a handful of large wallets can outvote thousands of small ones, especially when turnout is low.

### What is a quorum in a DAO vote?

The minimum number of votes a proposal needs to pass. Compound's governance documentation, for example, requires a majority and at least 400,000 votes in favour. A high quorum protects against capture by a small group, and it also makes urgent fixes harder to pass when holders are not paying attention.

### Is a multisig a DAO?

A multisig is a control mechanism that many DAOs use, not a governance model on its own. ethereum.org describes funds living in a wallet shared by 5 to 20 trusted community members who execute the result of a community vote. It adds speed and safety, and it concentrates power in the signers.

### How do you fix low turnout in DAO governance?

Lower the cost of participating: allow delegation so holders can hand their votes to someone active, make voting cheap or free for small holders, notify holders when a vote affects them, and set quorum against the supply that realistically votes. Each fix has a cost, so pick the one that addresses your actual failure mode.

### Does Builders Camp teach DAO governance?

Incentives and token mechanics and ecosystem strategy are among the published topics of Builders Camp's Web3 Product Management bootcamp, and its practical challenge asks you to diagnose a governance vote that passed with low participation and write the recovery proposal.

## Sources

- [Jungnickel et al., DAO Governance: Voting Power, Participation, and Controversy (ACM Distributed Ledger Technologies, 2025)](https://dl.acm.org/doi/10.1145/3777416)
- [Vitalik Buterin: Moving beyond coin voting governance](https://vitalik.eth.limo/general/2021/08/16/voting3.html)
- [ethereum.org: Decentralized autonomous organizations (DAOs)](https://ethereum.org/en/dao/)
- [Compound docs: Governance](https://docs.compound.finance/v2/governance/)
- [ethereum.org: Introduction to smart contracts](https://ethereum.org/en/developers/docs/smart-contracts/)
- [The Register: Smart contract bug gives away $90m in COMP](https://www.theregister.com/2021/10/01/compound_crypto_bug/)
- [Builders Camp: Web3 Product Management bootcamp](https://builderscamp.com/bootcamps/web3-pm)

## How this guide was made

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.