How DAO Governance Actually Works: From Forum Post to On-Chain Execution

“Decentralised governance” sounds like a single mechanism, but in practice it is a pipeline. An idea passes through several stages, each with its own gatekeepers, costs and failure modes. Understanding that pipeline is the fastest way to read any DAO's decisions critically.

1. The forum: where most decisions are really made

Nearly every serious DAO starts proposals on a discussion forum. Authors publish a draft, delegates and contributors challenge it, and the text is revised. By the time something reaches a vote, the outcome is often already clear. That makes forum participation disproportionately influential — and worth watching even if you never post.

2. The temperature check

Next comes a non-binding poll, commonly run on Snapshot. Because Snapshot votes are signed messages rather than transactions, they cost nothing, which encourages wide participation. A temperature check filters out ideas that clearly lack support before anyone spends gas or political capital.

3. The formal proposal

A formal proposal must usually clear a proposal threshold — a minimum amount of voting power held or delegated by the proposer. This protects the DAO from spam, but it also means small holders typically need a delegate to sponsor their idea.

In fully on-chain systems, the proposal contains the exact transactions to execute: contract addresses, function calls and parameters. Reading these “calldata” actions is the most reliable way to know what a proposal really does, regardless of its title.

4. The vote

Voting power is measured at a fixed snapshot block, so tokens bought after the proposal was created don't count. A proposal generally passes when:

• participation reaches quorum, and
• “For” votes exceed “Against” votes (or a higher supermajority, for sensitive actions).

5. The timelock

Passed on-chain proposals are queued in a timelock contract for a fixed delay — often one to several days. The delay is a safety valve: if a harmful proposal slips through, users can exit and guardians (where they exist) can cancel it.

6. Execution

After the delay, anyone can trigger execution. For Snapshot-based DAOs, execution is instead performed by a multisig or by a module (such as UMA's oSnap or the Zodiac Reality module) that relays the off-chain result on-chain.

Where power concentrates

Formal voting is the last step, not the first. Agenda-setting, proposal thresholds and execution rights shape outcomes as much as the vote itself.

When you evaluate a DAO, ask: who can propose, who can execute, who can veto, and how long users have to react. Those four answers tell you more about its decentralisation than any marketing page.