How to start a DAO: an 8-step founder's guide (legal wrapper, governance, treasu

Short answer: To start a DAO you need eight things:

a written mandate;
a legal wrapper;
an explicit governance design (membership, voting, quorum, delegation);
a treasury held in a multisig with spending rules;
a decision on token vs. non-token membership;
tooling for discussion, voting and execution;
a launch checklist;
a plan for the failure modes that kill most DAOs.

Deploying a token comes last. Designing the institution comes first.

Most "how to start a DAO" guides are tool tutorials. The tools are the easy part. The hard part, and the part that decides whether your DAO survives its first crisis, is institutional design. Treat a DAO as an institution with a constitution and test it against failure before you launch. A minimum viable constitution covers: purpose, membership, voting and quorum, delegation, treasury policy, upgrade process, amendment process and dispute resolution.

Step 1: Define the purpose and mandate
Write down, in one paragraph, what the DAO is for and what it is not allowed to do. A DAO without a narrow mandate becomes a treasury looking for a reason to spend. Answer three questions honestly:
[list=1]

What shared asset or rule set will members govern? A protocol, a treasury, a grants program, a standard, a collectively owned resource.
Why can't a normal company do this? Good answers: credible neutrality, community ownership of a shared resource, resistance to a single operator changing the rules. "Tokens are trendy" is not an answer.
Which decisions must stay fast or private? Security response, hiring and legal matters rarely suit open voting.

Step 2: Choose a legal wrapper
Pick a legal entity before you take members or money, because without one, members may carry personal liability. In the CFTC's case against Ooki DAO, a US federal court accepted that the DAO could be treated as an unincorporated association, which exposed its token-holding participants. Common options:

Wyoming DAO LLC (USA). DAO supplement to the LLC Act, effective July 2021; member-managed or algorithmically managed. The name must include "DAO", "LAO" or "DAO LLC", and the articles must reference the smart contracts used to manage it.
Marshall Islands DAO LLC. Decentralized Autonomous Organization Act (2022); for-profit or non-profit LLCs.
Cayman Islands foundation company. Foundation Companies Act (2017); can operate ownerless, widely used by protocols to hold IP, sign contracts and act on token-holder decisions.
Other routes. Swiss associations or foundations, Utah's DAO legislation (2024), unincorporated nonprofit associations in some US states. Each has trade-offs on tax, governance flexibility and member disclosure.

The wrapper is the interface between on-chain governance and off-chain law. Pick it for liability, tax and enforceability, not marketing. This is not legal advice; hire a lawyer in the relevant jurisdiction.

Step 3: Design governance (voting, quorum, delegation)
Decide who can propose, who can vote, how votes are counted, what quorum applies and how delegation works, and write it all down before launch.

Proposal rights: who can submit, and is there a threshold to prevent spam?
Voting method: one-token-one-vote, one-member-one-vote, quadratic voting, conviction voting. Each shifts power to different groups.
Quorum: too high and nothing passes; too low and a small group decides everything.
Timing: a discussion period, a voting period and an execution delay (timelock) between approval and effect.
Delegation: delegates should publish voting rationale and disclose conflicts; holders need an easy way to revoke.
Separation of powers: don't let one vote control spending, upgrades and emergencies. Use different paths and thresholds.

Why it matters: in 2022 an attacker used a flash loan to acquire temporary voting power in Beanstalk and passed a proposal that sent protocol funds to themselves. Every rule was followed. The design was the vulnerability.

Step 4: Set up the treasury and multisig
Hold funds in a multisig smart-contract wallet with independent signers, written spending rules and a timelock on large movements.

Use a multisig such as Safe, with a threshold like 3-of-5 or 4-of-7. Signers must be truly independent: different organizations, devices and jurisdictions.
Split the funds: an operating wallet with low limits and a reserve with high thresholds and long delays.
Write a treasury policy: budget, approval levels, signer rotation, what happens if a signer disappears.
Limit emergency powers: a guardian should be able to pause, never move, funds.
Publish everything: addresses, signers and policy.

The 2022 Ronin bridge breach is the reference case for signer independence: attackers obtained enough validator keys to authorize withdrawals. The blunt question: who can move the money, and who can change who can move the money?

Step 5: Decide token or non-token membership
Tokens reward capital; non-token membership can reward contribution, identity or reputation.

Fungible governance token: liquid and easy to distribute, but voting power can be bought, borrowed or concentrated; may raise securities questions.
Non-transferable membership: soulbound NFTs or registry-based membership resist vote buying but need a credible admission process.
Hybrid: tokens for economic participation, a separate body holds specific powers. Optimism's Token House plus Citizens' House is one example.
No token at first: launch with a small, known membership and decentralize progressively.

Define who is a member, how they join, and how they leave or are removed. If you can't answer the exit question, the design is incomplete.

Step 6: Pick the tooling

Discourse / forums: long-form proposal discussion before any vote.
Snapshot: off-chain, gasless voting with signed messages and balances at a block snapshot. Results are not automatically executed on-chain; usually a multisig carries them out.
Safe (formerly Gnosis Safe): the most widely used smart-contract multisig for DAO treasuries.
Tally: interface for on-chain governance on Governor-style contracts; passed proposals can execute on-chain, usually via a timelock.
Aragon: framework (Aragon OSx) and app for deploying DAOs with on-chain voting and permission plugins.
OpenZeppelin Governor: audited, open-source contracts for on-chain governance with timelocks.

Common pattern: forum discussion, then a Snapshot signal, then Safe or Governor execution, with a timelock in front of anything touching the treasury or upgrades. If your tool decides your governance, you outsourced your constitution to a UI default.

Step 7: Run the launch checklist

Mandate published (Step 1)
Legal wrapper registered and members' liability addressed (Step 2)
Proposal, voting, quorum and delegation rules published (Step 3)
Treasury multisig live, signers independent, policy published (Step 4)
Membership rules, including entry and exit, published (Step 5)
Tooling configured: forum, voting, execution, timelocks (Step 6)
Upgrade process: who can change contracts, with what delay
Amendment process: how the constitution itself changes
Dispute resolution: how contested decisions are challenged
Governance stress test run, every item green or with a documented plan

Upgrade, amendment and dispute resolution are the three elements founders most often skip, and the three that matter most in a crisis.

Step 8: Plan for the common failure modes
Assume each of these will happen, and design a response before launch.
[list=1]

Plutocracy / whale capture. Mitigation: delegation with accountability, non-token checks, separated powers.
Governance attacks. Flash-loaned or borrowed votes, as with Beanstalk. Mitigation: pre-proposal snapshots, delays, timelocks.
Voter apathy. Mitigation: realistic quorums, delegates with duties, fewer and better proposals.
Key concentration. One team or laptop controls the multisig or upgrades. Mitigation: independent signers, rotation, pause-only guardians.
No error correction. A bad proposal passes and can't be reversed quickly (Compound's 2021 Proposal 62 bug). Mitigation: bounded emergency powers and a defined amendment path.
Legal exposure. No wrapper, so members may be liable. Mitigation: Step 2.

Written by Jarvis Nelson Osorio, author of Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design. Full guide with FAQ: https://jarvis-osorio-books.surge.sh/dao/how-to-start-a-dao/