How long does it take for a proposal to take effect?
A decentralized autonomous organization (DAO) lets token holders vote on a protocol's rules or how its treasury is spent. Announcements usually report only that a vote passed, but a proposal typically moves through discussion, an informal poll, a formal vote, and a waiting period before anything happens.
This guide explains what a DAO can decide and walks a hypothetical proposal through each stage. It also covers proposal thresholds and voting periods, timelocks and execution powers, and how to check documents against contracts.
What a DAO decides
What a DAO controls varies widely. Some vote on parameters such as fee rates, treasury spending, new features, and even contract upgrades; others vote on a few items and leave the rest to a core team.
Ethereum.org's governance page explains that changes to Ethereum itself go through coordination among developers, node operators, and users rather than a token vote. Many DeFi protocols do use token voting, and the BIS has noted that decision-making power can still end up concentrated in a few hands. So it is worth checking what "the DAO decides" actually covers.
A hypothetical proposal timeline
The table follows a hypothetical proposal to fund a development grant from the treasury, with typical durations for each stage.
| Stage | Duration (assumed) | What happens | What to check |
|---|---|---|---|
| 1. Forum discussion | About 7 days | Proposal published, feedback gathered | Objections and revisions |
| 2. Off-chain poll | 3–5 days | Gas-free signaling vote | Turnout and split |
| 3. On-chain submission | 1 day | Proposer must meet threshold (e.g., 1% of supply) | Who submitted it |
| 4. On-chain vote | About 7 days | Quorum and passing threshold | Share held by top voters |
| 5. Timelock | About 2 days | Waiting period before execution | Time for users to react |
| 6. Execution | Immediate | Contract moves funds | Whether execution matches the proposal |
From discussion to execution takes about three weeks. Every protocol sets its own stages, and some allow shortened procedures for emergencies.
Voting power and proposal thresholds
OpenZeppelin's governance documentation explains that on-chain governance requires decisions on how voting power is counted, the quorum, voting options, and what is executed when a proposal passes. Many protocols also require a minimum amount of voting power before an address can submit a proposal on-chain.
A high proposal threshold filters out spam but means only large holders can put proposals forward directly. Smaller holders often work through delegates or community members who hold enough voting power.
Delegation and turnout
In some protocols, holding tokens is not enough to vote; holders must first delegate their voting power, to themselves or someone else. Many holders never take that step, so the voting power actually in use is often a small fraction of supply.
Consider a hypothetical case: if only 15 million of 100 million votes are delegated, a quorum of 4 million represents about 27% of the votes that can actually be cast. If that delegated power is concentrated among a few delegates, their judgment determines outcomes.
Execution powers and timelocks
When an on-chain vote passes, the result often goes through a timelock contract and executes automatically after a delay. The timelock gives users time to review the change and withdraw if they disagree.
If voting is off-chain and a multisig carries out results, whether the vote is honored depends on those signers. Check who holds any emergency pause power and what it can do.
Execution details matter as much as the vote. A proposal's text and the transaction actually executed should match, and some DAOs publish the exact call data in advance so anyone can verify it before the timelock expires.
Checking documents against contracts
When reviewing a DAO's governance, compare its documentation with what is on-chain.
- Find the stages, durations, proposal threshold, quorum, and passing threshold in the official documentation.
- Locate the governor and timelock contract addresses and check in a block explorer that their settings match the documents.
- Look at turnout, total delegated voting power, and the share held by top delegates in recent proposals.
- Check that passed proposals were actually executed and that the executed transaction matches the proposal.
- If a multisig or emergency pause exists, find out what it can do and who controls it.
Limits of DAO governance
DAOs make decision-making public and recorded, but low turnout and concentrated voting power can let a few holders' choices be presented as the community's will. Legal responsibility is often unclear as well.
The timeline and figures here are hypothetical. When looking at a real DAO, use its latest governance documentation and voting records with their dates, and look at how a result is carried out, and by whom, before taking the vote count at face value.