---
title: "Voting and delegation in DAOs"
url: "https://caper.network/wiki/dao-governance/concepts/voting/voting-and-delegation"
updated: 2026-08-31
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# Voting and delegation in DAOs

|  |  |
| --- | --- |
| **Topic** | Handing your voting power to a representative |
| **Solves** | Voter apathy — most token holders never vote |
| **Forms** | Direct delegation · self-delegation · liquid (transitive) democracy |
| **Chief risk** | Delegate cartels — power re-concentrating in a few addresses |
| **Related** | [Token-weighted voting](/wiki/dao-governance/concepts/voting/token-weighted-voting), [Governance models](/wiki/dao-governance/concepts/fundamentals/dao-governance-models), [Sybil resistance](/wiki/dao-governance/concepts/membership/sybil-resistance-in-daos) |

**Delegation** is the mechanism that lets a token holder assign their voting power to another address — a _delegate_ — who then votes on their behalf. What that delegate owes in return, and what happens when they stop voting without returning the weight, is covered in [delegate accountability and dormant delegates](/wiki/dao-governance/concepts/voting/delegate-accountability). It is the single most common answer to the defining problem of [token-weighted governance](/wiki/dao-governance/concepts/voting/token-weighted-voting): most holders never vote, so without delegation a handful of active whales decide everything and quorums fail. By concentrating dispersed, apathetic weight onto engaged representatives, delegation is what lets large [DAOs](/wiki/dao-governance/concepts/fundamentals/what-is-a-dao) reach quorum at all.

## Why delegation exists

Voter turnout in major DAOs is chronically low — most governance tokens sit in wallets that never cast a vote, whether from apathy, gas costs, or the sheer effort of evaluating every proposal. Delegation lets those holders stay passive without their weight going to waste: they hand it to someone who _will_ read the forum, follow the technical debate, and show up for every vote. Some frameworks make this mandatory — under [Compound's Governor](https://docs.compound.finance/governance/), COMP confers no voting power until it is delegated, so even holders who want to vote themselves must first **self-delegate** (see [voting power activation and delegation thresholds](/wiki/dao-governance/concepts/voting/voting-power-activation) for what that step does to the size of the electorate). ([a16z crypto: DAO governance FAQ](https://a16zcrypto.com/posts/article/governance-faq/))

## How delegation works

A holder picks a delegate and signs a delegation; from then on their weight counts toward whatever that delegate votes, at the balance they hold when each proposal snapshots. Crucially, delegation is **non-custodial and revocable** — the delegate never touches the tokens, and the holder can re-delegate to someone else or take their weight back at any time, overriding the delegate on a specific vote if they disagree.

Around this primitive an entire layer has grown up: delegates publish **delegate statements** — platforms and voting histories — and holders browse and compare them on tools like [Tally](https://www.tally.xyz/) and [Boardroom](https://boardroom.io/). [ENS](https://docs.ens.domains/dao/) built its DAO delegation-first, encouraging every token holder to pick a delegate at claim time.

Cosmos SDK chains invert the default entirely. On the [Cosmos Hub](/wiki/daos/networks/cosmos-hub) and every chain running its `x/gov` module, a delegator who does not vote **automatically inherits their validator's vote**; voting yourself simply overrides it. Delegation there is not something a holder opts into for governance, it is a side effect of staking for yield, and it means an inactive balance is counted as a vote rather than as an abstention. That single default is why Cosmos turnout figures are not comparable to the ones quoted for opt-in delegation DAOs. The pattern is not confined to Cosmos: [Orbs](/wiki/daos/networks/orbs-network) runs the same inversion off-chain, where a Guardian votes its entire delegated stake unless the delegator opts out for that proposal – which is how one of its ballots passed on seven signatures carrying 151.1m ORBS.

[SafeDAO](/wiki/daos/infrastructure/safe-dao) runs a comparable delegate system and pushes further on the incentive side: its ongoing [Outcomes-Based Resource Allocation (OBRA)](https://forum.safe.global/t/sep-32-obra-continuation-of-governance-accessibility-and-participation-enhancement-at-safedao-stablelab/5381) track pays active delegates and working groups against measurable results — an explicit attempt to keep representatives engaged rather than absentee, since an unpaid delegate is as prone to apathy as the holders who delegated to them.

## Liquid democracy and its cartels

When delegates can themselves re-delegate, delegation becomes **transitive** — a chain of trust that ends at whoever is actually voting. This is _liquid democracy_: a fluid middle ground between direct democracy (everyone votes) and representative democracy (fixed officials), where any holder can be a passive voter, an active voter, or a delegate, and can switch roles at will.

The flexibility has a cost. Delegation re-concentrates power: in practice a handful of large delegates end up controlling a majority of the active vote, so a low-turnout DAO can be captured by a **delegate cartel** coordinating across proposals — the pattern behind on-market governance raids like [the Compound 'Golden Boys' incident](/wiki/dao-governance/concepts/analysis/dao-security-and-governance-attacks). Delegation fixes apathy but does not, by itself, fix [plutocracy](/wiki/dao-governance/concepts/voting/token-weighted-voting); it can sharpen it. ([Fritsch et al., 'Analyzing Voting Power in Decentralized Governance'](https://arxiv.org/abs/2505.04136))

## How Caper approaches this

A [caper](/wiki/foundations/what-is-a-caper) has **no member-to-delegate system**: every member [votes their own ranked ballot directly](/wiki/governance/voting), and voting weight is the product of a member's stake _and_ their earned participation, not a balance that can be assigned away. That deliberately trades the expertise and higher turnout delegation buys for immunity to delegate cartels — there is no aggregated voting bloc to capture, because there are no delegates. The one delegation-like primitive a caper ever had was the [VOTE proposal](/wiki/governance/proposals) — a caper deciding as a body how to vote, then casting that pre-committed ballot inside another caper. It belonged to the pre-August 2026 escrow system and did not return with the ballots: kind 2 is retired, the contract rejects it by name, and `vote()` takes a `Global` voter it checks against the caller, so a treasury holding another caper's token has no path to cast it. Organization-to-organization delegation is therefore not something a caper can do today in either direction.

## References

- a16z crypto, [Lightspeed Democracy: what web3 organizations can learn from the history of governance](https://a16zcrypto.com/posts/article/governance-faq/).
- Compound, [Governance documentation](https://docs.compound.finance/governance/) (delegation-to-vote requirement).
- ENS, [ENS DAO documentation](https://docs.ens.domains/dao/).
- Tally, [delegate directory and voting platform](https://www.tally.xyz/).
- Fritsch, Müller & Wattenhofer, [Analyzing Voting Power in Decentralized Governance](https://arxiv.org/abs/2505.04136) (arXiv, 2025).