Ten named governance frameworks — from quadratic and conviction voting to futarchy — with the tradeoffs of each and how DAOs combine them without deadlocking.
The "move fast and break things" era of DAOgovernance is over. Early experiments showed what's possible—and what's dangerous. To survive the next decade, DAOs need frameworks that balance speed, security, and decentralization. Here are 10 governance frameworks that top-tier DAOs are using to ensure resilience.
The Governance Trilemma
Every DAO faces a fundamental tradeoff:
Priority
Benefit
Cost
Speed
Quick decisions
Centralization risk
Security
Protected from attacks
Slow, bureaucratic
Decentralization
Broad participation
Coordination overhead
No framework optimizes all three perfectly. The goal is conscious tradeoffs that match your DAO's needs.
The "best" governance framework doesn't exist. The right framework depends on your DAO's size, treasury, member composition, and mission. What works for a 10-person collective won't work for a billion-dollar protocol.
The cost of each additional vote increases quadratically. One vote costs 1 credit, two votes cost 4 credits, three votes cost 9 credits. This prevents wealthy holders from dominating.
Implementation
Votes
Credits Required
1
1
2
4
3
9
5
25
10
100
Benefits
Democratic expression: Smaller holders have meaningful voice
Intensity signaling: Shows how strongly you feel
Whale resistance: Diminishing returns on large positions
Nuanced decisions: Not just yes/no
Tradeoffs
Sybil attacks (creating many wallets)
Complex for voters to understand
Requires identity verification for fairness
Used by: Gitcoin Grants, Optimism Retro Funding
Framework 4: Conviction Voting
How It Works
Voters "charge up" their preference over time. The longer you hold your vote on a proposal, the more weight it gains. Removing your vote resets conviction.
Implementation
Element
Description
Continuous voting
No discrete voting periods
Conviction growth
Weight increases over time
Threshold
Proposals pass when conviction exceeds threshold
Decay
Removing votes loses accumulated weight
Benefits
Long-term thinking: Rewards sustained commitment
Reduced hype: Can't rush decisions
Stakeholder alignment: Those who stay engaged have more say
Reputation token: Non-transferable, earned through contribution
Implementation
Token
Properties
Purpose
Governance
Transferable, tradeable
Economic alignment
Reputation
Soulbound, non-transferable
Merit-based authority
Benefits
Decoupling: Financial power ≠ decision power
Meritocracy: Contributors earn influence
Plutocracy resistance: Can't buy reputation
Flexibility: Different weights for different decisions
Tradeoffs
Complexity in token design
Reputation gaming possible
Two systems to maintain
Used by: Hats Protocol, various DAOs experimenting with soulbound tokens
Dual-token systems work best when reputation is earned through verifiable contributions, not social relationships. Design clear criteria for reputation allocation.
Framework 6: Futarchy (Decision Markets)
How It Works
"Vote on values, bet on beliefs." Governance uses prediction markets to determine which proposals will increase a specific metric (like TVL, user growth, or token price).
Implementation
Step
Action
1
Define target metric (e.g., TVL increase)
2
Create prediction markets for each option
3
Traders bet on outcomes
4
Implement option with highest predicted value
5
Settle markets based on actual results
Benefits
Incentive alignment: Bettors have skin in the game
Information aggregation: Markets surface hidden knowledge
Responsiveness: Change delegates if they disappoint
Participation: Lower barrier than voting on everything
Tradeoffs
Complex to implement and explain
Delegation cascades can create unexpected power concentrations
Requires active engagement to work well
Used by: Snapshot delegations, various DAOs experimenting
Framework 10: Multi-Sig Guardians
How It Works
A small group of elected "Guardians" holds a veto over proposals that could harm the treasury or protocol. Provides a safety layer without daily control.
Used by: Safe multisigs as fallbacks, various protocol DAOs
Guardians should be time-limited, publicly known, and removable. Concentrated power without accountability is dangerous.
The attack surface: how governance actually fails
Frameworks are chosen in calm rooms and tested in ugly ones, and the failures repeat across every DAO large enough to matter. The first is flash-loan voting: borrowing voting power for a single block, passing or blocking a proposal, returning the loan. Snapshot-based voting mostly kills this by sampling balances off-chain at a past block, but anything that reads voting weight within the same transaction remains exposed — the checklist question is not "are we snapshot voting?" but "at what block, and can anyone influence that block's balances?"
The second is vote buying. Bribe markets pay holders for voting a specific way, and their effect is worse than raw plutocracy: they make apathy profitable and concentration liquid. A holder who would never research a proposal will still sell a vote on it. The mitigations are structural rather than moral — longer lockups make borrowed power expensive, hidden-until-execution voting raises the buyer's uncertainty, and issue-specific delegations dilute the value of any single bought block.
The third failure is the quiet one: apathy, usually expressing itself through quorum. A quorum threshold meant as protection becomes an attack surface when participation drops — a small coordinated minority can pass proposals at hours nobody watches, technically, legally by the rules as written. The DAOs that survive this treat participation itself as infrastructure: delegation systems, clear summaries, predictable schedules. The last is proposal spam under optimistic designs: when challenge is the only filter, the challenge bond prices the defense, and a well-funded attacker can make disputing every malicious action more expensive than enduring them. Optimistic frameworks need a watcher economy, not just a watcher assumption.
Governance health is measurable, and the numbers that matter are mostly trends rather than levels. Participation rate — distinct voters or delegators per proposal — matters as a direction: falling participation with stable treasury size is the early warning that precedes every governance crisis. Delegate concentration answers one question: what share of voting power the top ten accounts control, and whether that share is growing. Above roughly half, your "decentralized" DAO is a committee with extra steps, whatever the token distribution says.
Time-to-decision measures the cost of your framework choices: median days from proposal to execution, split by proposal type. It is the number members feel first and complain about second. Quorum margin — how far past the threshold proposals actually land — tells you how much headroom the system has before a quiet Tuesday attack passes; margins shrinking quarter over quarter deserve a response before they reach zero. And treasury velocity ties governance to solvency: committed spend versus runway, because a treasury governed generously without a runway model is a commons waiting for enclosure. Five numbers, reviewed quarterly, catch most failures a constitution will not.
A realistic year-one rollout
The composition advice below is easier to trust with a sequence attached. Quarter one: direct voting plus a multisig for treasury operations, nothing else — the goal is a working habit, not a system. Quarter two: add delegation for routine decisions and name the delegation criteria explicitly, because implicit delegate power is how informal hierarchies get formalized. Quarter three: add the second framework your proposal volume now justifies — quadratic or conviction for funding, optimistic execution for operations — and write down what it replaced. Quarter four: a constitutional review, which is a scheduled meeting with one agenda item — what broke, what the metrics said, what changes next year.
The rollout matters because frameworks adopted reactively, mid-crisis, tend to encode the panic: a treasury scare produces permanent guardians, an angry thread produces quadratic voting. Sequencing the adoption turns governance from a reaction into a practice, and the year-one document — what was tried, what the numbers were — becomes the onboarding material that makes year two cheaper.
Choosing and Combining Frameworks
Assessment Criteria
Criterion
Questions to Ask
DAO size
How many active participants?
Treasury size
What's at risk?
Technical capability
Can members use complex systems?
Decision frequency
How many proposals per week?
Member expertise
Do you have domain specialists?
Risk tolerance
What's the cost of a bad decision?
Recommended Combinations
Small DAO (<50 active members):
Direct democracy for major decisions
Multi-sig for treasury operations
On-chain courts for disputes
Medium DAO (50-500 members):
Quadratic voting for funding decisions
Liquid democracy for general governance
Delegation to pods for operations
Large DAO (500+ members):
Holographic consensus for attention scaling
Conviction voting for funding
Guardian multisig for safety
Resilient DAO governance isn't about choosing one framework—it's about composing multiple approaches into a system that fits your specific context. The frameworks above represent building blocks, not finished solutions. Start simple, observe what breaks, and add complexity only when needed. The DAOs that survive will be those that treat governance as an evolving system, not a one-time design.