Table of Contents
- 1. What Makes a Token a DAO Token?
- 2. Governance Models: Token-Weighted vs Conviction vs Quadratic
- 3. Voting Weight and Supply Design
- 4. Quorum and Approval Thresholds
- 5. Delegation: Letting Others Vote for You
- 6. DAO Token Distribution
- 7. Solana DAO Tools and Infrastructure
- 8. Common DAO Token Design Mistakes
What Makes a Token a DAO Token?
A DAO (Decentralized Autonomous Organization) token is a token whose primary function is to confer governance rights — the ability to propose and vote on decisions that control a protocol, treasury, or community. Unlike a memecoin or utility token, the DAO token's value is fundamentally tied to the voting power it represents.
DAO tokens can also carry other rights — staking rewards, fee revenue share, access to services — but governance is the core purpose that distinguishes them from other token types.
Governance Models: Token-Weighted vs Conviction vs Quadratic
Token-weighted voting (most common)
One token = one vote. Simple to implement, easy to understand, but subject to plutocracy — large holders can dominate all decisions. This is the dominant model in crypto today and the right starting point for most DAOs.
Conviction voting
Voting power accumulates over time as you commit tokens to a proposal. The longer you hold your position, the more conviction (voting weight) you accumulate. Prevents flash governance attacks and rewards long-term stakeholders. More complex to implement but produces better quality decisions.
Quadratic voting
Voting power scales as the square root of tokens held. A holder with 100 tokens has 10 votes; one with 10,000 tokens has 100 votes rather than 10,000. Reduces plutocracy but requires sybil resistance (preventing one person from splitting tokens across many wallets). Very hard to implement securely in a permissionless crypto environment.
Recommendation for most Solana DAOs: Start with token-weighted voting. It's simple, understood, and compatible with all governance tools. Add time-locking (staking your tokens to vote) to reduce short-term manipulation. Graduate to more complex models only if you have a concrete problem to solve.
Voting Weight and Supply Design
DAO token supply design has different constraints than memecoin supply design. The key question is: who should have meaningful governance power?
Smaller supply, higher concentration of power
If you have 1,000,000 total tokens and 1,000 active community members, each member on average holds 1,000 tokens. Governance votes are legible — you can track who voted and what their stake was. This works well for smaller, focused DAOs.
Larger supply, more distributed power
Higher supply makes it easier to distribute to a larger number of holders without fractional token amounts being awkward. But it also means governance proposals need higher absolute token counts to reach quorum, which can cause voter apathy.
Small DAO (<500 members)
- Supply: 1M–10M tokens
- Higher per-token price signals
- Each holder's vote is meaningful
- Quorum is easier to reach
- Governance is more personal
Large DAO (>5,000 members)
- Supply: 100M–1B tokens
- Broader distribution possible
- Delegation becomes essential
- Voter apathy is a real risk
- Quorum thresholds need tuning
Quorum and Approval Thresholds
Two governance parameters shape whether your DAO can actually function:
Quorum
The minimum percentage of total voting power that must participate for a vote to be valid. Set it too high (e.g., 30% of all tokens) and you'll have proposals that can never pass due to voter apathy. Set it too low (e.g., 1%) and a small coordinated group can pass anything.
Most functioning DAOs use 5–15% quorum for routine proposals and 20–30% for major protocol changes. Start lower and raise it as your community matures.
Approval threshold
The percentage of voting tokens that must vote "yes" for a proposal to pass. Simple majority (51%) is standard for most decisions. Constitutional changes or treasury spending above a threshold often require supermajority (67% or 75%).
Delegation: Letting Others Vote for You
Most DAO token holders don't vote on every proposal — they're busy, uninterested in certain decisions, or not qualified to evaluate technical proposals. Delegation solves this: token holders delegate their voting power to a trusted party who votes on their behalf.
Delegation is essential for any DAO with more than a few hundred active members. Without it, quorum becomes nearly impossible to reach and a small group of highly motivated voters dominates all decisions.
How to implement delegation on Solana
Most Solana governance frameworks (Realms, SPL Governance) support token delegation natively. Token holders can delegate to any wallet address — including specialized "delegates" who publish their voting philosophy publicly.
DAO Token Distribution
DAO token distribution should reflect the principle that governance power belongs to those who are most engaged with and knowledgeable about the protocol. This means:
- Large community allocation — Distributed to active users, early supporters, contributors. 30–50% is common.
- Smaller team allocation with long vesting — Team tokens should vest for 2–4 years minimum. Founders shouldn't have outsized control at launch.
- Investor allocation with vesting — Investors who rushed to buy governance tokens at a low price shouldn't dominate governance on day one.
- Treasury / DAO-controlled reserve — A portion locked in the DAO's own treasury, disbursed only by governance vote. This gives the DAO real resources to fund initiatives without depending on founders.
Solana DAO Tools and Infrastructure
SPL Governance / Realms
The native Solana governance framework. Open-source, on-chain, and widely used. Supports token-weighted voting, multi-sig councils, proposal creation, and treasury management. The starting point for most Solana DAOs. Accessible at realms.today.
Squads Protocol
Multi-sig wallet infrastructure for Solana DAOs. Often used for DAO treasury management alongside Realms for governance. Provides programmable spending controls with on-chain enforcement.
Streamflow
For vesting team and investor tokens — essential to ensure governance power isn't concentrated at launch.
Common DAO Token Design Mistakes
- Governance theater — Putting everything to a vote but ignoring results or having the team veto decisions anyway. Destroys community trust quickly.
- Voter apathy trap — Setting quorum too high for the actual active voter base. The DAO becomes ungovernable and the team ends up making all decisions anyway.
- No delegation — Without delegation, governance participation drops as the community grows. Passive holders never participate and active minority runs everything.
- Governance over everything — Not every decision needs a governance vote. Requiring votes for operational decisions creates paralysis. Reserve governance for major decisions and delegate operational authority to the core team or council.
- Token = votes without token = utility — If holding the governance token provides no benefit beyond voting rights, demand is low. Consider adding staking rewards, fee revenue, or product access to governance token holders.
Next Steps
Understand how a DAO token compares to other token types: Community Token vs Investor Token →
For the complete context guide: Complete Guide to DAO Governance Token Creation →
Or return to the hub: Tokenomics Guide for Non-Technical Founders →