BLK 368.5M·XRD $0.0008·Σ TVL √ 11.1K
LAUNCHGOVERN
Wiki homeEssays
  1. Home
  2. /
  3. Wiki
  4. /
  5. DAOs
  6. /
  7. Tooling
  8. /
  9. The DAO tooling stack

MANIFESTO · CAPER / OWN THE GAME
The launchpad that raises and deploys capital. Guaranteed entry / exit liquidity. Governance that can't be captured.

Running a DAO is not one product but a stack: a set of specialised tools, mostly independent of each other, that a community assembles to make decisions, hold money, pay people, control who takes part and stay legible. There is no “DAO operating system” that does all of it — instead a typical DAO layers a voting venue over a treasury wallet, bolts on funding and payroll modules, and points analytics and legal wrappers at the result. This page maps that stack by function and links to the deep page for each tool, so you can see how the pieces fit before diving into any one of them.

Voting & signaling

The layer that turns members into decisions. Snapshot is the near-universal off-chain venue — gasless, wallet-signed votes stored on IPFS — used for temperature checks and non-binding signaling. Tally (now Cactus) covers the on-chain side, providing the interface for OpenZeppelin Governor contracts where a passed vote executes a transaction directly. Agora is the other major on-chain interface, running binding votes for Optimism, Uniswap and ENS. Most large DAOs run both layers: cheap Snapshot signaling first, binding on-chain execution second. (Snapshot docs, Tally docs)

Access & identity

Deciding who is in the room before any vote is cast. Guild is the widely-used authorization layer: it turns an on-chain fact — hold this token or NFT, complete this action — into an off-chain permission, automatically granting and revoking Discord roles, Telegram access, and GitHub or Google permissions as wallets meet or fall out of a role's requirements. It is the plumbing behind most token-gated communities, including social DAOs like Friends With Benefits, and pairs with proof-of-personhood signals such as Gitcoin Passport to keep one person from entering as many. This layer governs access, not vote weight — it decides who may participate, while the voting and framework layers decide what that participation does.

Frameworks

The scaffolding that defines what a DAO is on-chain — its permissions, membership and upgrade rules. Aragon OSx models a DAO as a lean permission manager with swappable governance plugins. The Moloch framework — minimal, audited contracts whose defining feature is rage-quit — underpins a generation of grants DAOs and lives on today through DAOhaus. Colony adds reputation-weighted, task-based structure — influence is earned reputation that decays, not tokens held. Frameworks trade flexibility for safety: you inherit battle-tested contracts instead of writing your own. Hats Protocol narrows this layer to roles and permissions alone: revocable, non-transferable ERC-1155 "hats" arranged in an admin tree, read by tools like Safe and Snapshot to gate who may act (Hats Protocol). (Aragon docs, Moloch contracts)

Treasury & custody

Where the money actually sits. Safe (formerly Gnosis Safe) is the default: an m-of-n multisig smart-contract wallet that holds the treasury for most of the DAO world, extended by modules and guards — most commonly the Zodiac standard — so a passed Snapshot vote can execute against it without a trusted signer. Custody is the highest-stakes layer — a treasury is a DAO’s most valuable and most attacked asset — which is why the ecosystem standardised hard on one well-audited account model. (Safe docs)

Funding & contributor comp

Getting money in and back out to the people doing the work. Juicebox is the programmable treasury/fundraising layer that powered ConstitutionDAO and thousands of crowdfunds. Gitcoin runs quadratic-funding rounds for public goods. Coordinape pioneered peer-allocated compensation — contributors reward each other’s work directly — though its app wound down in 2025. This layer is where governance meets payroll, and it is historically the least standardised part of the stack.

Analytics & discovery

The instruments that make a DAO legible to its members and to outsiders. DeepDAO is the canonical directory and analytics dashboard — treasury sizes, membership, voter turnout across thousands of DAOs. Boardroom — acquired by Agora in 2025 — and Messari Governor track live proposals across ecosystems. These are the sources that answer “how healthy is this DAO?” — the metrics covered on treasury management. (DeepDAO)

Legal wrappers

The off-chain shell that gives an on-chain organisation legal personhood and limited liability. MIDAO forms Marshall Islands DAO LLCs; Wyoming’s DAO LLC statute offers a US equivalent. Without a wrapper, members of an unincorporated DAO can face unlimited personal liability — a risk the legal-structures page covers in depth. This layer is optional but increasingly standard for any DAO holding real assets or signing contracts.

Choosing a stack

The right stack follows the DAO’s type and size. A small grants collective may need only a Safe plus Snapshot and a Moloch-style rage-quit. A large protocol DAO governing a live contract needs on-chain Governor execution (Tally/Cactus), a formal legal wrapper, and analytics for accountability. The rule of thumb: start minimal — a treasury and a way to vote — and add layers only when a concrete failure (a captured multisig, an unclear payout, a liability scare) demands one. Over-tooling an early DAO adds coordination cost without adding safety.

How Caper approaches this

Caper collapses most of this stack into a single protocol. Custody, voting, execution and exit are not separate tools bolted together but one contract-governed flow: a proposal is voted and executed on-chain in one binding step, the treasury is a protocol-controlled vault rather than a separate Safe, and members can exit for their pro-rata share under the same rules. The trade-off is deliberate: a caper gives up the pick-your-own-tools flexibility of the assembled stack in exchange for having no seams — no multisig to capture, no off-chain vote to later ratify, no gap between deciding and doing. For teams that want the modular approach, the tools above remain the reference.

References

  • Aragon, OSx documentation.
  • Snapshot, Documentation; Tally, Documentation.
  • Safe, Documentation.
  • DeepDAO, DAO analytics directory.
  • a16z crypto, DAO governance FAQ (Andrew Hall, 2023).
What this isA map of the DAO operating stack — the software categories a DAO wires together to run
Core layersVoting · frameworks · treasury custody · funding · contributor comp · analytics · legal wrappers
Design realityNo single app runs a DAO; most assemble best-of-breed tools around a Safe treasury and a Snapshot vote
RelatedWhat is a DAO?, Governance models, Treasury management