PROPELOO

DAO GOVERNANCE DEVELOPMENT

Build DAO governance that makes decisions, not just proposals.

PROPELOO engineers DAO governance systems — token-weighted and quadratic voting contracts, proposal lifecycle management, timelock execution, treasury multi-sig integration, delegation mechanics, and the off-chain signalling layer (Snapshot) that enables cheap governance before on-chain execution. A governance system that has proposals but no execution path is a suggestion box, not governance.

Most DAOs fail at governance because they confuse voting activity with decision-making. High proposal volume with low voter participation and no execution path is worse than no governance at all.

DAO governance has a fundamental challenge: on-chain voting is expensive (gas), so most token holders do not vote; proposals that do pass need to actually execute something on-chain (treasury transfers, parameter changes, contract upgrades); and governance power concentrated in large token holders creates plutocracy that undermines the decentralisation promise. PROPELOO designs governance systems that address these problems explicitly: Snapshot for off-chain signalling with gasless voting, on-chain voting for binding decisions, timelock for security (delayed execution gives holders time to exit if they disagree), delegation for voter representation, and quadratic voting for more equitable power distribution. The treasury module is the part governance needs to be useful — the ability to propose and execute treasury transfers is what makes DAO governance real.

What a production DAO governance system contains.

Signalling, voting, execution and treasury management are distinct components.

System Layers

  • Signalling Layer: Snapshot space, gasless off-chain voting, community temperature check, forum integration
  • Proposal Layer: On-chain proposal submission, quorum requirements, voting period, proposal types (text, treasury, contract call)
  • Voting Engine: Token-weighted voting, quadratic voting, delegation, vote counting, snapshot block
  • Execution Layer: Timelock contract, proposal queue, execution after timelock delay, veto mechanism
  • Treasury Module: Multi-sig treasury, proposal-driven spending, streaming payments, budget allocation, treasury reporting

Core Technical Capabilities

  • Snapshot Integration

    Snapshot space configuration with custom voting strategy (token balance, staked balance, delegation). Proposal templates. Community temperature check before on-chain vote. Results not directly executable but inform on-chain decisions.

  • On-Chain Governance

    OpenZeppelin Governor contract (Governor Bravo pattern). Proposal submission, discussion period, voting period, execution queue. Proposal types: simple text, treasury transfer, arbitrary contract call, parameter change.

  • Voting Mechanics

    Token-weighted: 1 token = 1 vote. Quadratic: voting power = sqrt(tokens). Conviction voting: vote weight increases with time held. Delegation: delegate voting power to a representative. Vote snapshot at proposal block to prevent flash loan manipulation.

  • Timelock Execution

    Passed proposals queue in a timelock contract with a delay (typically 48-72 hours). During the delay, token holders can review the execution and exit if they disagree. Timelock delay is configurable by governance itself.

  • Treasury Management

    Gnosis Safe multi-sig as treasury. Governance module connected to safe as a signer. Proposal-triggered treasury transfers. Streaming payments (Superfluid/Sablier) for contributor compensation. Budget period allocation.

  • Vote Delegation

    On-chain delegation: token holders delegate voting power to any address without transferring tokens. Delegatees vote on behalf of delegators. Delegators can revoke delegation at any time. Delegation chain tracking.

How we approach DAO governance architecture.

Governance is only as valuable as what it can decide. A governance system that cannot execute on-chain actions is advisory, not binding.

  • Execution path must be defined before governance is deployed

    The hardest question in DAO governance is not how to vote — it is what the vote controls. Before building the voting contract, define what actions governance can trigger: treasury transfers, contract parameter changes, contract upgrades, team compensation. Governance without a defined execution scope is a discussion forum.

    Axiom: DEFINE SCOPE BEFORE BUILDING CONTRACTS

  • Timelock delay is a security guarantee, not a bug

    A passed governance proposal that executes immediately with no delay is a security risk — a governance attack can drain the treasury in one transaction. The timelock delay gives the community time to respond. The delay length is a security parameter: long enough to be meaningful (48-72h), short enough not to paralyse operations.

    Axiom: TIMELOCK IS SECURITY, NOT FRICTION

  • Voter apathy must be designed around

    Token-weighted governance with high quorum requirements fails when token holders do not vote. Design for the participation rate you will actually achieve, not the rate you want. Delegation reduces the effective quorum needed by allowing active participants to accumulate delegated voting power. Lower quorum thresholds with time-delayed execution achieve better operational governance than high quorum with paralysis.

    Axiom: DESIGN FOR ACTUAL PARTICIPATION

Key decisions in DAO governance architecture.

These choices define governance power distribution, security and operational effectiveness.

  • Token-weighted vs quadratic voting?

    Impact: Token-weighted for on-chain binding votes (simpler to implement, standard expectation). Quadratic for signalling votes where broad community input is valued. Full quadratic voting requires Sybil resistance that is difficult to guarantee on-chain.

    • Token-weighted — simple, standard, plutocratic (large holders dominate)
    • Quadratic — more equitable distribution, requires Sybil resistance (one person = one vote identity)
    • Conviction voting — vote weight increases with time held, favours long-term holders
    • Hybrid — token-weighted for binding on-chain votes, quadratic for signalling
  • OpenZeppelin Governor vs custom governance?

    Impact: OpenZeppelin Governor is the correct default. It is audited, supports all standard voting patterns, and is easily extended.

    • OpenZeppelin Governor — audited, battle-tested, Governor Bravo pattern, widely understood
    • Compound Bravo — original implementation, same pattern as OZ Governor
    • Custom — full flexibility, requires full audit, justified only for very specific requirements
  • Snapshot + on-chain vs on-chain only?

    Impact: Snapshot for routine signalling and community feedback. On-chain governance for binding decisions with treasury or contract execution. The two-step process reduces on-chain governance attack surface by limiting what proposals reach on-chain voting.

    • On-chain only — all votes on-chain, highest trust, high gas cost per vote
    • Snapshot + on-chain — gasless signalling on Snapshot, binding votes on-chain, common hybrid
    • Snapshot only — no on-chain execution, advisory only
  • Timelock delay: how long?

    Impact: 48-72 hours standard timelock. Variable timelock by proposal category is worth the added complexity for protocols managing large treasuries.

    • 24 hours — fast execution, low security buffer
    • 48-72 hours — industry standard, sufficient response time for most communities
    • 7 days — maximum security, slow for time-sensitive decisions
    • Variable per proposal type — higher delay for treasury, lower for parameter changes

What PROPELOO builds.

  • Protocol DAO Governance

    Full governance system for a DeFi protocol — token-weighted voting, timelock, treasury management, Snapshot integration.

  • Investment DAO

    Investment DAO infrastructure — deal proposal workflow, member voting on investments, capital deployment execution, portfolio reporting.

  • Community DAO

    Community governance for a token-gated community — proposal creation, gasless voting, treasury allocation for community initiatives.

  • Grants DAO

    Grants programme governance — project applications, committee review, token holder ratification, milestone-based payment execution.

  • Sub-DAO Structure

    Multi-level governance with parent DAO and working group sub-DAOs — delegated authority, budget allocation, escalation paths.

The DAO governance stack.

Proven contracts and community tooling.

  • Smart Contracts

    Stack: OpenZeppelin Governor, TimelockController, Gnosis Safe (treasury), ERC-20 voting token, Foundry testing

  • Signalling

    Stack: Snapshot (off-chain voting), Custom voting strategies, Tally / Boardroom UI, Forum (Commonwealth/Discourse), Discord integration

  • Streaming

    Stack: Superfluid (streaming payments), Sablier (vesting streams), Budget allocation contracts, Contributor compensation, Treasury diversification

  • Analytics

    Stack: Tally governance analytics, Voter participation tracking, Delegation flow visualisation, Treasury reporting, Proposal success rate

DAO governance security: the attack surface is the treasury and the contract upgrade path.

A governance attack that passes a malicious proposal can drain the treasury or upgrade contracts to an attacker-controlled version.

  • Governance attack via flash loan

    An attacker borrows governance tokens, submits and passes a proposal in one transaction. Snapshot-at-proposal-block prevents this — voting power is fixed at the block when the proposal was created, before the flash loan.

  • Proposal spam and griefing

    Minimum proposal threshold (tokens required to submit a proposal) prevents spam. Proposal deposit that is slashed for failed proposals prevents griefing. These parameters must be calibrated to the token distribution.

  • Timelock bypass

    The timelock contract is the final security gate. Its own governance permissions (who can cancel proposals, what delay can be reduced to) must be carefully configured. The timelock admin should itself be the DAO, not an EOA.

  • Quorum manipulation

    If quorum is low and token distribution is concentrated, a small number of colluding holders can pass proposals. Quorum should be set relative to the active voter population, not total supply. Delegation increases effective participation and makes quorum manipulation harder.

From governance design to live DAO operations.

  1. 01. Governance Design

    What does governance control? Proposal types, voting model, quorum, timelock parameters.

  2. 02. Smart Contracts

    Governor, timelock, treasury integration, token deployment or integration.

  3. 03. Snapshot Space

    Snapshot space setup, voting strategy, proposal templates, forum integration.

  4. 04. Treasury Setup

    Gnosis Safe deployment, governance module, initial funding, streaming payment setup.

  5. 05. Delegation Launch

    Delegation infrastructure, delegation campaign, voter onboarding.

  6. 06. First Proposals

    Governance process documentation, first proposal cycle, participation monitoring.

  7. 07. Iteration

    Governance parameter tuning based on actual participation data.

Frequently Asked Questions

What can DAO governance actually control?

It depends on what you connect to the governor. Common controllable actions: treasury transfers, protocol fee parameter changes, contract upgrades (via proxy), whitelisting addresses, minting tokens, changing governance parameters themselves. Define the scope before deploying the contracts.

How do you prevent governance attacks?

Three main defences: proposal snapshot at creation block (prevents flash loan voting), minimum proposal threshold (prevents spam), and timelock delay (gives community time to respond to malicious proposals). Additional: guardian multisig that can veto proposals during the timelock period for a specified initial phase.

Do all votes need to be on-chain?

No — and for routine community decisions, they should not be. Snapshot enables gasless off-chain voting for temperature checks and non-binding decisions. Only binding decisions (treasury transfers, contract changes) need on-chain voting and execution. This keeps on-chain governance load manageable.

How do you handle low voter participation?

Delegation is the primary mechanism — allow active community members to accumulate delegated voting power from passive holders. Lower quorum thresholds with time-delayed execution is more effective than high quorum that paralyses governance. Gasless voting on Snapshot also increases participation for signalling decisions.

Which governance token standards do you implement?

We implement ERC-20Votes and ERC-721Votes (OpenZeppelin standard) with checkpointed historical balance tracking. This records account voting power at specific block checkpoints, allowing proposal snapshots to calculate voting weights deterministically and preventing double-voting through token transfers during active ballots.

How do optimistic governance models save gas costs?

Optimistic governance (such as Snapshot combined with Safe Zodiac Reality or Kleros) enables community members to vote completely off-chain for zero gas. Once approved, the proposal outcome is posted optimistically to a multi-sig or timelock contract on-chain. Anyone can challenge fraudulent execution within a challenge window.

Can DAOs enforce sub-DAO budgets and streamed milestone payouts?

Yes. We architect modular governance topologies using sub-DAO smart vaults and token streaming protocols (such as Sablier or Superfluid). Working groups receive continuous streaming grants that the main DAO governor or multisig council can pause or claw back if milestone deliverables are unmet.

How is legal entity wrapper integration supported technically?

We design governance systems compatible with real-world DAO legal wrappers (Swiss Verein, Cayman Foundation Company, Marshall Islands MIDAO). Smart contract timelocks and multi-sig signers are mapped directly to legal board resolutions and authorized signatory quorums to ensure binding legal enforceability.