DAO Governance

Details

Author: Daniel Larimer (term coined 2014, Bitshares); Vitalik Buterin (extended the term 2014, Ethereum); first major implementation The DAO 2016
Category: Frameworks
Published: 2014
Source: Ethereum Foundation
Source URL: https://ethereum.org/en/dao/
Access: public

Description

Governance through on-chain voting, weighted by token holdings, often layered with off-chain deliberation. Documented in the ToGather archive at Traditional Dream Factory in Portugal.

Annotation

A DAO is a Decentralized Autonomous Organization. Strip away the marketing layer and the operational definition is simple. A group makes decisions through votes recorded on a public blockchain, the votes are weighted by tokens held (or by some weighted formula combining tokens, presence, and contribution), and the rules of the voting are themselves enforced by code. The first major experiment was The DAO in 2016, a venture-fund DAO that raised 12.7 million Ether before being drained by an attacker through a code exploit. Most DAOs in operation in 2026 inherit lessons from that incident: code can be wrong, on-chain voting alone is not enough, and a working DAO is almost always a hybrid of on-chain mechanisms and off-chain deliberation.

The pattern's intentional-community application is more recent and quieter than its venture-capital application. A handful of regenerative villages, co-living networks, and stewardship projects have adopted DAO mechanics not as a way to maximize token returns but as a way to keep land out of speculative dynamics across multiple human generations. The clearest example in the ToGather archive is [Traditional Dream Factory](/community/traditional-dream-factory), a regenerative village in Alentejo, Portugal, founded 2021-2022. TDF has roughly 280 token holders, has raised €1.2 million in capital, holds 25 hectares of former industrial chicken farm now under agroforestry, and uses a DAO with weighted voting based on tokens, presence, and contribution.

The DAO at TDF is not an autonomous treasury. It is a governance layer above a Swiss nonprofit that legally holds the land. The token is non-speculative by design. One token equals one night's stay. The token is a one-way entry into the commons. The project will never buy the token back. If a holder leaves, they can sell the token to someone else; the project itself does not hold a buyback obligation. If the association fails, the land does not return to private ownership; it must be donated to another nonprofit with a similar purpose. These constraints are encoded into the legal and governance scaffolding, not just the smart contract. The pattern only works because the on-chain layer and the off-chain legal layer are designed together.

Sam, one of TDF's founders, names the three weights that determine governance influence in his archive interview: financial capital ("how much money you put in"), presence capital ("how much time you spend in the year"), and work capital ("how much work you put into the project"). Citizens, who are vetted through a one-month minimum stay and a vouching process, can create proposals. Anyone with tokens can vote. The categories that go through the DAO are explicit: changes to the master plan, changes to the village from a building perspective, changes to the game rules, and election of a new executive team. The conflict resolution layer, the relational practice, and the weekly transparency circles run alongside the DAO, not through it.

This entry covers what DAO Governance is, where it came from, how it actually runs at TDF and across the broader DAO field, where it gets confused with adjacent patterns, who is using it now, how a group can begin practicing it, where the door is for community builders considering DAO mechanics, and where it gets hard. The companion entries are [Sociocracy 3.0](/library/sociocracy-3-0) (the consent-based deliberation pattern that often runs alongside on-chain voting), [Doocracy](/library/doocracy) (the off-chain initiative pattern that handles the operational layer most DAOs cannot reach), and the forthcoming Plurality entry by Audrey Tang and Glen Weyl, which extends the conceptual frame to digital-democracy mechanisms beyond token-weighted voting.

A working DAO is almost never the whole governance system. It is the formal layer that handles a specific bounded set of decisions, layered onto a legal scaffold and an off-chain deliberation culture. Communities that adopt DAO mechanics expecting them to replace governance entirely tend to discover, somewhere between month six and year three, that the off-chain layer they did not build is the layer that determines whether the on-chain layer holds. The DAO does not replace conflict resolution. The DAO does not replace cultural memory. The DAO does not replace the question of who gets to be in the room. What the DAO does is record the formal decisions in a way that survives the loss of the people who made them, and tie those decisions to a treasury that cannot be unilaterally raided.

For an intentional community, that is sometimes exactly the right tool. Sometimes it is the wrong tool. The entry below tries to make the difference legible.

Full text

# DAO Governance

## Description (one-sentence card text)

Governance through on-chain voting, weighted by token holdings, often layered with off-chain deliberation. Documented in the ToGather archive at Traditional Dream Factory in Portugal.

## Long annotation (italic block under the hero)

For an intentional community, that is sometimes exactly the right tool. Sometimes it is the wrong tool. The entry below tries to make the difference legible.

## Full content

## What it is, and what it is for

A DAO is a Decentralized Autonomous Organization. The operational definition is one sentence. A group of people makes formal decisions through votes recorded on a public blockchain, the votes are weighted by some combination of tokens held, time in the project, and work contributed, and the rules of the voting are enforced by code rather than by a chairperson.

The canonical short definition comes from the Ethereum Foundation: "A DAO is an organization owned and managed by its members, with rules written in code on a blockchain, where decisions are made through community-wide voting." The Ethereum.org primer adds the political claim: "DAOs allow us to work with like-minded folks around the globe without trusting a benevolent leader to manage the funds or operations."

The pattern fits a particular kind of group. Distributed across geographies, with members who may not meet in person every year. Holding shared resources (land, treasury, code, stewardship rights) that need to survive turnover in the original founding cohort. Willing to invest in the technical and legal scaffolding that makes on-chain governance work. Comfortable with the trade-off that on-chain voting privileges those who can navigate digital tools and absorb the cognitive load of reading proposals.

DAO governance is a layer, not a complete system. Most DAOs in operation in 2026 are hybrid: on-chain voting for the formal decisions (treasury allocations, role elections, master plan changes, rule amendments) layered on off-chain deliberation (Discord conversations, monthly forum calls, working groups, in-person citizens' gatherings) and a legal entity (a Swiss nonprofit, a Cayman foundation, a Delaware LLC, a Wyoming DAO LLC). The DAO is the formal record. The off-chain layer is where the deliberation happens. The legal layer is where the assets sit.

> **FROM THE FIELD.** The clearest archive example is [Traditional Dream Factory](/community/traditional-dream-factory), a regenerative village in Alentejo, Portugal. The Base44 community card names the governance model directly: "DAO with weighted voting based on tokens, presence, and contribution." Sam, a founder, walks through the procedural layer in his archive interview. The TDF entry draws on three published interviews on Base44 ([Tias](/interview/6967b061bcc53fba406b8bf9), [Julia](/interview/6967af25ea360ea6bc027a20), [Tonya Gorman](/interview/6967a192a0662d4d189b6cce)) plus draft interviews with Sam and Luna pending publication.

<figure>
<svg viewBox="0 0 700 460" xmlns="http://www.w3.org/2000/svg" style="max-width:660px; display:block; margin:24px auto; background:#fcfaf5;">
<text x="350" y="26" text-anchor="middle" font-family="Georgia, serif" font-size="13" fill="#857e72" font-style="italic">Three layers running together. None of them works alone.</text>
<text x="350" y="58" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#5d4f3a" font-weight="600">ON-CHAIN: the formal record</text>
<rect x="48" y="72" width="145" height="110" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="120" y="96" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#c97e4f" font-weight="600">1. TOKEN</text>
<text x="120" y="122" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Tokens, presence,</text>
<text x="120" y="136" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">contribution weight</text>
<text x="120" y="162" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">membership and</text>
<text x="120" y="174" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">governance weight</text>
<text x="199" y="132" text-anchor="middle" font-family="Georgia, serif" font-size="22" fill="#c97e4f">→</text>
<rect x="209" y="72" width="145" height="110" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="281" y="96" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#c97e4f" font-weight="600">2. PROPOSAL</text>
<text x="281" y="122" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Vetted member writes,</text>
<text x="281" y="136" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">posts to forum</text>
<text x="281" y="162" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">bounded categories</text>
<text x="281" y="174" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">only</text>
<text x="360" y="132" text-anchor="middle" font-family="Georgia, serif" font-size="22" fill="#c97e4f">→</text>
<rect x="370" y="72" width="145" height="110" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="442" y="96" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#c97e4f" font-weight="600">3. VOTE</text>
<text x="442" y="122" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Recorded on-chain,</text>
<text x="442" y="136" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">verified cryptographically</text>
<text x="442" y="162" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">quorum + threshold</text>
<text x="442" y="174" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">in smart contract</text>
<text x="521" y="132" text-anchor="middle" font-family="Georgia, serif" font-size="22" fill="#c97e4f">→</text>
<rect x="531" y="72" width="145" height="110" rx="6" fill="#ffffff" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="603" y="96" text-anchor="middle" font-family="Georgia, serif" font-size="11" fill="#c97e4f" font-weight="600">4. EXECUTION</text>
<text x="603" y="122" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Time-locked, then</text>
<text x="603" y="136" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">executed by legal entity</text>
<text x="603" y="162" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">ragequit available</text>
<text x="603" y="174" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">to minority voters</text>
<text x="350" y="216" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#5d4f3a" font-weight="600">OFF-CHAIN: where deliberation happens</text>
<rect x="48" y="228" width="628" height="70" rx="6" fill="#f7f1e3" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="362" y="254" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Forum threads, Discord, working groups, weekly citizens' sharings,</text>
<text x="362" y="270" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">conflict resolution, vetting process, relational practice</text>
<text x="362" y="288" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">Most DAO failures are off-chain failures dressed up as technical ones.</text>
<text x="350" y="326" text-anchor="middle" font-family="Georgia, serif" font-size="12" fill="#5d4f3a" font-weight="600">LEGAL ENTITY: where the assets sit</text>
<rect x="48" y="338" width="628" height="70" rx="6" fill="#f3ede1" stroke="#5d4f3a" stroke-width="1.5"/>
<text x="362" y="364" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">Swiss nonprofit, Cayman foundation, Wyoming DAO LLC, Delaware LLC,</text>
<text x="362" y="380" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72">French community-interest association, French SCIC, Perpetual Purpose Trust</text>
<text x="362" y="398" text-anchor="middle" font-family="Georgia, serif" font-size="9" fill="#857e72" font-style="italic">Without the legal layer, the DAO carries unresolved liability.</text>
<text x="350" y="438" text-anchor="middle" font-family="Georgia, serif" font-size="10" fill="#857e72" font-style="italic">TDF model: token bundles financial + presence + contribution. Swiss nonprofit holds the land.</text>
</svg>
<figcaption style="text-align:center; font-style:italic; color:#857e72; font-size:13px; margin-top:8px;">The hybrid DAO governance stack: on-chain cycle (top), off-chain deliberation (middle), legal entity (bottom). All three layers running together, as at Traditional Dream Factory.</figcaption>
</figure>

## Where it came from

DAO governance is new as a label and old as an idea.

The label was coined by Daniel Larimer in 2014 in the context of Bitshares, an early blockchain protocol. Vitalik Buterin extended the term in his 2014 essay "DAOs, DACs, DAs and More: An Incomplete Terminology Guide," distinguishing decentralized autonomous organizations from corporations, applications, and societies. The Ethereum white paper, also 2014, framed smart contracts as the technical substrate that would make DAOs operational. The first major implementation was The DAO, launched in April 2016, which raised 12.7 million Ether (worth roughly 150 million dollars at the time) in a token sale before being drained of approximately 3.6 million Ether in June 2016 through a recursive call exploit in its withdrawal function.

The Ethereum community responded by hard-forking the chain to reverse the exploit, creating the split between Ethereum (the forked chain) and Ethereum Classic (the unforked chain). The episode taught the DAO community three lessons that shaped every subsequent generation:
1. Code is not a complete substitute for governance. Rules enforced by code can be exploited by anyone who reads the code more carefully than the people who wrote it.
2. On-chain governance produces real social conflicts that have to be resolved off-chain. The hard fork was a political decision made by the human community of Ethereum developers, not an output of a smart contract.
3. A DAO without a legal entity around it carries enormous unresolved liability. The DAO's investors had no clear legal recourse against the attacker, and the people who organized the response had no clear legal authority to do so.

Subsequent DAOs have layered governance more carefully. MakerDAO, launched 2017, separated executive contracts from governance votes and produced one of the longer-running and most-tested DAO governance systems. MolochDAO, launched 2019, introduced "ragequit" (the right to exit with your share of the treasury) as a structural protection against governance attacks. Gitcoin, launched 2020, layered DAO governance on top of quadratic funding for public goods. Nouns DAO, launched 2021, ran continuous on-chain auctions to fund creative work.

The intentional-community application emerged later and quieter. Communities holding land for stewardship across multiple human generations have a different optimization function from venture-capital DAOs trying to maximize treasury returns. Patagonia's 2022 conversion to a Perpetual Purpose Trust and the Steward-Ownership tradition (Bosch since 1937, Carl Zeiss since 1889) provided one model for taking ownership out of speculation. The DAO model provided another, with the trade-off that the legal mechanism was less battle-tested but the governance mechanism was more transparent.

[Traditional Dream Factory](/community/traditional-dream-factory) launched in 2021-2022 explicitly inside this lineage. The legal layer is a Swiss nonprofit holding the land in commons. The governance layer is a DAO. Sam describes the design choice in his archive interview: "We wanted to take land out of these speculative dynamics and make sure that two, three, five generations from now, the land will continue to be regenerated, and we can keep building up the resources rather than depleting them." The DAO is the formal record-keeping mechanism for a thousand-year project; the Swiss nonprofit is the legal hand that holds the title.

## How it actually runs

The TDF system is the cleanest archive example. The pattern below draws on Sam's interview, the TDF community card, and the broader DAO governance literature.

### The token

At TDF, one token equals one night's stay at the village. Tokens are sold publicly on the project's website and through subsequent token issuance rounds. As of 2025, the project has raised approximately 1.2 million euros from roughly 280 token holders. The token is non-speculative by design: it is a one-way entry into the commons. The project will never buy a token back. If a holder leaves, they can resell the token to another buyer. The token grants access rights, not equity in a legal entity that could be liquidated.

The TDF token bundles three things that are usually unbundled in venture DAOs: financial capital (the euros put in), presence capital (the time spent at the village), and work capital (the labor contributed to the project). Each of these contributes to the holder's governance weight. Sam in his interview: "How much time you spend in the year also gives you more governance weight. How much work you put into the project gives you more governance weight."

### The proposal

Citizens, who are vetted through a minimum one-month stay plus a vouching process, can create proposals. Anyone with tokens can vote on a proposal once it is submitted. Proposals are written in plain language, posted to the governance forum, and recorded on-chain when they reach the formal vote stage.

The categories that flow through the DAO at TDF are bounded and named. Changes to the master plan. Changes to the village's physical buildings. Changes to the game guide (the document that defines values, conflict resolution processes, substance use, sexuality, and other cultural norms). Election of a new executive team or replacement of the current one.

The categories that do not flow through the DAO are equally important. Daily operational decisions (who cooks Tuesday dinner, where to put the new compost bin, which workshop to host this weekend). Conflict resolution between specific individuals. The vibe-check call before someone is approved to come for a one-month stay. These run through the off-chain layer: the team, the citizens' weekly sharings, the vetting process, the relational practice.

### The vote

Votes are recorded on-chain and verified cryptographically. Sam: "Everything is verified cryptographically, so we can actually trust that the votes being cast are accurate." The voting tool is a digital interface designed to make the on-chain layer legible to non-technical participants. Most DAOs use one of a small number of standard tools (Snapshot for off-chain signaling, Aragon for full on-chain execution, Tally for delegation interfaces) layered with custom UI.

Quorum, threshold, and weighting rules are written into the smart contract. At TDF the weighting combines token holdings, presence, and contribution. At MakerDAO, the weighting is purely token-based. At Nouns DAO, each Noun NFT carries one vote regardless of secondary-market price. The choice of weighting is the most consequential governance design decision and is the place where most DAO failures originate.

### The execution

When a vote passes, the execution mechanism varies. In a fully on-chain DAO, the smart contract automatically executes the decision (transfers funds, deploys a new contract, changes a parameter). In a hybrid DAO like TDF, the on-chain vote is a binding mandate that is then executed by the legal entity (the Swiss nonprofit) through ordinary off-chain means (signing a contract, hiring a contractor, registering a change with the relevant authorities).

The hybrid model is the dominant pattern in 2026 because pure on-chain execution requires every action the organization takes to be representable as a smart contract call, which excludes most interactions with the physical world. A DAO that holds land in Portugal cannot replace its village manager through a smart contract. It can only record the decision to do so on-chain and then execute the decision through the legal entity.

### The exit

The exit pattern is one of the most consequential design choices a DAO makes. MolochDAO popularized "ragequit": the right of any minority voter to exit at any time with their proportional share of the treasury, before a contested decision executes. This protects against governance attacks where a majority votes to drain the treasury at the expense of a minority.

At TDF, the exit pattern is different. Tokens are non-refundable. The project will never buy a token back. A token holder who leaves can resell the token to another buyer at whatever price the market sets, but the project itself does not hold a buyback obligation. The land cannot be liquidated under any circumstance. If the project association fails, the land must be donated to another nonprofit with a similar purpose. These constraints are encoded in the legal scaffolding, not the smart contract. A person who joins TDF accepts that the financial commitment is illiquid in exchange for the community commitment being permanent.

### A real moment

From Sam's archive interview, on the moment two years into the project when the founder stepped out for several months. "I was burned out. That was a moment when we launched the token, and I was like, okay, good time to decentralize it and hand it over to someone to run it. I stepped out for a few months and I went to travel and I replenished my energies. And then the project, things didn't go so well. Kind of had to come back and pick up the pieces."

The story is told because it names a structural feature of DAO governance that the literature often misses. A DAO does not, by itself, distribute the operational load that a founder carries. The DAO distributes formal decision-making authority. It does not automatically distribute the on-the-ground work of running the project. The transition from founder-led to DAO-led is a separate and harder transition than the technical setup of the smart contract.

## What it is and what it is not

Five common confusions worth naming directly.

**DAO governance is not the same as cryptocurrency speculation.** A community DAO that uses a token to encode access rights and governance weight is doing something different from a token launched on Uniswap to be traded for profit. The TDF token is non-speculative by design. The project will never buy it back. The token grants access to a place, not a claim on a future cash flow. Conflating the two is the most common public misunderstanding of community DAOs.

**DAO governance is not autonomous in the everyday sense.** The "A" in DAO is misleading. A working DAO requires constant human attention: proposal authors, voters, working group members, dispute resolvers, the people who maintain the off-chain forum, the people who keep the legal entity in good standing, the people who write the smart contract upgrades. A DAO automates the formal record of decisions. It does not automate the decisions themselves.

**DAO governance differs from [Sociocracy 3.0](/library/sociocracy-3-0)**. Sociocracy 3.0 is a deliberation framework grounded in consent decision-making. Most DAOs do not use consent decision-making; they use majority or supermajority voting, often with weighted voting tied to token holdings. The two patterns can pair: a community can run S3 in its working groups for proposal development, then run a DAO vote for formal ratification. TDF's working groups operate this way in practice.

**DAO governance differs from [Doocracy](/library/doocracy)**. Doocracy is the off-chain initiative pattern that handles the operational layer most DAOs cannot reach. A DAO records who voted what; doocracy describes who built what. Most working DAOs run doocracy in parallel for the daily operational work and run the DAO for the bounded categories that need formal record. TDF explicitly runs both layers.

**DAO governance differs from steward-ownership and perpetual purpose trusts.** Steward-ownership uses traditional legal mechanisms (foundation ownership, voting rights tied to roles rather than capital, golden shares) to hold ownership out of speculation. The Patagonia 2022 conversion is the most prominent recent example. DAO governance can sit on top of a steward-ownership-like legal structure (TDF does this with its Swiss nonprofit) but the two patterns are not the same. Steward-ownership is a legal arrangement. DAO governance is a decision-making system.

## Communities practicing it

Three communities or movements with archive grounding or substantive documentation, plus three external networks that name DAO governance in their own self-description.

### Traditional Dream Factory, Portugal (founded 2021-2022)

Located in Alentejo, southern Portugal. Approximately 280 token holders. €1.2 million raised in capital. 25 hectares of former industrial chicken farm now under agroforestry restoration. Hybrid governance: a Swiss nonprofit holds the land legally; a DAO holds governance authority over master plan, building changes, game guide changes, and executive team elections. The Base44 community card names the model: "DAO (Decentralized Autonomous Organization) with weighted voting based on tokens, presence, and contribution."

The TDF archive includes published interviews with [Tias](/interview/6967b061bcc53fba406b8bf9) (renovating the chicken farm with strangers, on collective building), [Julia](/interview/6967af25ea360ea6bc027a20) (people see you all the time, even in bad conditions), and [Tonya Gorman](/interview/6967a192a0662d4d189b6cce) (on choosing to stay), plus draft interviews with Sam (founder, the most detailed governance walk-through) and Luna (interior architect, leadership and somatic space-holding). Sam's interview is the procedural backbone for this entry. The published Tias and Julia interviews give the lived-experience layer of what it feels like to live inside the DAO-governed village. When the Sam and Luna interviews move from draft to published, this section will link to them directly.

### Cabin DAO, distributed (founded 2021)

A network of co-living houses (called "neighborhoods") tied together by a DAO that issues a stake-based membership token. Cabin's governance model is one of the more careful articulations of DAO governance for a residential network. The network publishes its governance documentation openly at cabin.city. Each neighborhood maintains its own local governance; the DAO handles network-level decisions about onboarding new neighborhoods, treasury allocations to public goods, and the network's strategic direction.

### MakerDAO, distributed (founded 2017)

The most-tested DAO governance system in operation as of 2026. MakerDAO governs the DAI stablecoin, with treasury holdings in the billions of dollars and a governance system that has weathered multiple crises (the March 2020 crash, the 2022 USDC depeg, the ongoing tension between RWA-backed and crypto-backed collateral). MakerDAO is not an intentional community in the residential sense, but its governance experiments are the closest thing the DAO world has to long-running primary research on what works for a DAO with billions of dollars in its treasury and tens of thousands of token holders. The community DAO movement borrows from MakerDAO without often saying so: the executive contract pattern, the delegation system, the constitutional voting framework, the multi-tier governance with different quorum thresholds for different decision types.

> **FROM THE FIELD.** The pattern that holds across these three communities is the layering. None of them runs governance through the DAO alone. TDF layers the DAO over a Swiss nonprofit and an off-chain citizens' culture. Cabin layers network DAO governance over local-neighborhood governance. MakerDAO layers DAO governance over an executive contract system, a delegation layer, and an extensive off-chain forum culture. The DAOs that have tried to run on the on-chain layer alone, without a legal scaffold and an off-chain deliberation culture, are mostly the ones that failed at the year-three mark or got drained by an exploit.

## How to begin practicing this in your own group

Six steps. Verb-first.

**1. Confirm a DAO is the right tool for your decisions.** A DAO is the right tool when the group is distributed across geographies, when shared resources need to survive turnover, when transparency of formal decisions matters more than speed, and when at least a meaningful subset of the membership can engage with on-chain tools. A DAO is the wrong tool when the group is small enough to meet in person regularly, when most decisions are operational rather than strategic, when participation requires forms of legibility (digital fluency, time, attention) that exclude the people who matter most, or when the assets at stake are mostly relational rather than financial. Many groups that adopt DAO mechanics would have been better served by a simple co-op or a Sociocracy 3.0 structure.

**2. Build the legal scaffolding before the smart contract.** A DAO without a legal entity carries enormous unresolved liability. The Swiss nonprofit that holds TDF's land is the layer that makes the DAO survivable. Other working community DAOs use Cayman foundations, Wyoming DAO LLCs, Delaware LLCs with custom operating agreements, or French community-interest associations. The legal layer determines what assets the DAO can hold, what jurisdictions its members are exposed to, and what happens if the smart contract is exploited. Build it first.

**3. Decide your weighting formula before the token launches.** The choice between one-token-one-vote, one-person-one-vote, weighted voting (tokens plus presence plus contribution, as at TDF), and quadratic voting determines who has power in the DAO. This is the single most consequential design decision. A token-weighted DAO will produce plutocratic outcomes. A presence-weighted DAO will produce locally rooted outcomes. A contribution-weighted DAO will produce founder-led outcomes for the first three years. Each has trade-offs. Pick consciously and document the reasoning.

**4. Develop the supporting skill of off-chain deliberation.** Most DAOs that fail, fail at the off-chain layer, not the on-chain layer. The forum culture, the working group meetings, the citizens' gatherings, the relational practice. These are the layer where proposals become viable before they reach the formal vote. A DAO whose members do not develop fluency in off-chain deliberation produces a thin formal layer over an operational vacuum. Pair with [Sociocracy 3.0](/library/sociocracy-3-0) for proposal development and a relational practice (council, sharing circles, regular weekly transparency meetings as TDF runs) for the cultural-memory layer.

**5. Pair with [Doocracy](/library/doocracy) for the operational tier.** A DAO records who voted what. Doocracy describes who built what. The two layers serve different functions and need different time horizons. Most working community DAOs run doocracy for the operational work that fills the days and run the DAO for the bounded categories that need formal record. Trying to run operational decisions through the DAO is a recipe for governance fatigue, voter apathy, and proposals that nobody bothers to read.

**6. Plan the governance attack and the founder transition.** Two crises hit DAOs predictably. The first is a governance attack: someone accumulates enough tokens to push through a self-serving proposal, or finds an exploit in the smart contract. Design rage-quit, time-locked execution, and minimum quorum thresholds before you need them. The second is the founder transition: the original founder steps back and the project discovers the operational load was carried by them, not by the DAO. Sam's two-year burnout at TDF is one archive example. The transition needs to be planned years in advance, not improvised when the founder hits the wall.

## Living examples and entry points for community builders

Where DAO governance is alive in 2026, and how to engage with it without falling into the patterns that have produced the field's recurring failures.

### Living examples

[**Traditional Dream Factory**](/community/traditional-dream-factory) (Alentejo, Portugal). The clearest community-DAO example documented in the ToGather archive. Token-based commons, Swiss nonprofit legal scaffold, weighted voting, hybrid on-chain and off-chain governance. The 25-hectare land regeneration is visible and tangible; the DAO is one tool among several. Visit through their one-month or three-month stewardship programs.

**Cabin DAO** (cabin.city, distributed). A network of co-living neighborhoods governed at the network level by a DAO. Neighborhoods are listed publicly and accept short-term visits. The Cabin governance documentation is one of the cleaner published examples for a residential application.

**Nouns DAO** (nouns.wtf). Not an intentional community in the residential sense, but the most architecturally interesting DAO experiment of the 2021-2026 era. Continuous on-chain auctions, treasury that funds creative public goods, governance through NFT ownership. Worth studying for the auction-mechanism innovation even if the use case is different.

**MakerDAO** (makerdao.com). The most-tested DAO governance system in the world. Read the constitutional voting framework documentation; it is the most carefully thought-through document in the DAO field as of 2026.

**Gitcoin** (gitcoin.co). Quadratic funding for public goods, governed by a DAO. The matching-funds mechanism is the most-discussed alternative to token-weighted voting and has been adopted in multiple research-funded experiments at the city level.

### Adjacent and inspired applications

**Mietshäuser Syndikat** ([Library entry](/library/mietshauser-syndikat)). The German housing federation that takes property out of the market through a different legal mechanism. Useful as a non-blockchain comparison for what land-out-of-speculation looks like across over 200 buildings in Germany.

**Embassy Network design patterns** ([Library entry](/library/embassy-network-design-patterns)). The co-living network that named "Do-ocracy" alongside other organizational design patterns. Pre-DAO but conceptually adjacent.

**Patagonia's Perpetual Purpose Trust** (2022 conversion). A non-blockchain mechanism to take a billion-dollar company out of speculation in service of a stated purpose. Read alongside DAO experiments for context on what other tools exist.

**Audrey Tang's Plurality work** (Variant C Library entry, forthcoming). Extends the conceptual frame beyond token-weighted voting to digital-democracy mechanisms (quadratic voting, Polis, vTaiwan) that have been deployed at the national-government level.

### Entry points

**Read the Ethereum.org DAO primer** (ethereum.org/en/dao). Forty minutes. The cleanest neutral introduction. Then read MakerDAO's constitutional voting framework alongside (forum.makerdao.com).

**Visit TDF for a one-month stay or stewardship program** (oasa.co or traditionaldreamfactory.com). The most direct way to see a community DAO in operation. €600 to €1,200 per month range as of 2026 depending on program; check current pricing.

**Join an existing DAO at low commitment.** The Gitcoin Passport program lets you build a verifiable contributor identity across multiple DAOs without large financial commitment. The Bankless DAO offers a low-floor entry point for governance learning. Most regional Cabin neighborhoods accept short visitors.

**Experiment with off-chain governance tools first.** Snapshot (snapshot.org) lets a group run weighted votes without smart contracts, treasury, or token issuance. Loomio offers similar functionality with no blockchain layer at all. Many groups discover their actual governance needs through Snapshot before investing in a full DAO setup.

**Sit with the legibility question.** A DAO's governance is only as legitimate as the participation of its members. If half your community cannot read a proposal, your DAO will be governed by the half that can. Before adopting DAO mechanics, ask whether the technical floor matches your community's actual participation patterns. If it does not, the DAO will encode an exclusion you did not name.

### One caution

A DAO is not a replacement for governance. It is a formal layer that records decisions and enforces some of them through code. The off-chain layer (deliberation, conflict resolution, cultural memory, relational practice) is what determines whether the on-chain layer holds. Most DAO failures are off-chain failures dressed up as technical ones. Communities that adopt DAO mechanics expecting them to solve governance discover, somewhere between month six and year three, that the work they avoided is the work that mattered most. Build the off-chain layer first. Build the legal scaffold second. Build the smart contract third. The order matters.

## Where it gets hard

Five tensions, each grounded in archive material, published critique, or documented incident.

### The legibility tension

A DAO requires every participant to read, understand, and vote on formal proposals. The cognitive load is real. At TDF, Sam describes the design challenge: "It's all very transparent, and you have a digital tool so everyone is able to contribute to the decision making." The digital tool is necessary because raw on-chain interfaces are largely illegible to non-technical participants. Even with the digital tool, voter participation in most DAOs runs at 5 to 30 percent of token holders. The unread proposals get decided by the small group that does read them, which produces the same hidden hierarchy that doocracy produces, dressed up as transparent governance. Naming this honestly is part of running a DAO well.

### The plutocracy tension

Token-weighted voting privileges those with the most tokens. Even at TDF, where the weighting combines tokens with presence and contribution, the financial-capital component remains significant. In purely token-weighted DAOs (most venture and protocol DAOs), the plutocracy problem is structural and acknowledged. Designs that combine multiple weights (presence, contribution, reputation, quadratic) reduce but do not eliminate the problem. A DAO that does not surface the plutocracy critique reproduces the problem invisibly. A DAO that does surface it can design around it.

### The legal-blockchain mismatch tension

A DAO's smart contract operates at the speed of code. The legal entity that holds the DAO's assets operates at the speed of law. The mismatch is structural. A DAO can vote in fifteen minutes to fire its executive director; the Swiss nonprofit that legally employs the executive director may need three months to execute the firing. The 2016 DAO hack response (the Ethereum hard fork) was, structurally, a community deciding to rewrite history through off-chain coordination because the on-chain mechanism could not respond fast enough. Most working DAOs accept the mismatch and run hybrid governance with the legal layer as the binding execution mechanism. Communities that try to eliminate the legal layer rediscover why it exists.

### The governance-attack tension

A sufficiently determined attacker can sometimes accumulate enough tokens to push through a self-serving proposal. The Build Finance hack of February 2022 (where an attacker took over the DAO through a low-turnout vote and drained 470,000 dollars) is the canonical recent example. Defenses include time-locked execution (the vote passes but execution is delayed long enough for the community to respond), minimum quorum thresholds, ragequit rights, and constitutional layers (some decisions require a higher threshold or are impossible to make at all). At TDF, the constitutional layer includes the rule that the land cannot be liquidated under any circumstance, regardless of any vote.

### The founder transition tension

The DAO does not, by itself, distribute the operational load that a founder carries. Sam at TDF stepped out for several months at the two-year mark and described what happened in the archive interview: "I stepped out for a few months and I went to travel and I replenished my energies. And then the project, things didn't go so well. Kind of had to come back and pick up the pieces." The DAO recorded the formal decisions during his absence; it did not run the project. Most community DAOs hit this transition somewhere between year two and year five. The honest planning move is to assume the founder will need to step back or step out and to design the operational distribution accordingly, before the founder hits the wall, not after.

## More resources

### Canonical primary sources

- **Ethereum.org DAO primer** (ethereum.org/en/dao). The cleanest neutral introduction.
- **MakerDAO Constitutional Voting Framework** (forum.makerdao.com). The most carefully thought-through governance documentation in the DAO field as of 2026.
- **Vitalik Buterin, "DAOs, DACs, DAs and More: An Incomplete Terminology Guide"** (May 2014, blog.ethereum.org). The 2014 essay that named the field.
- **Sam Hart, Toby Shorin, Laura Lotti, "Headless Brands"** (2020, Other Internet). The argument that DAO-style governance is a new form of brand stewardship; useful theoretical companion.

### Trainings and residencies

- **TDF stewardship program** (traditionaldreamfactory.com). Three-month residential program in Alentejo. The deepest available immersion in a community-DAO context.
- **Cabin DAO neighborhoods** (cabin.city). Short visits available across the Cabin network.
- **Bankless DAO** (banklessdao.com). The lowest-floor entry point for DAO governance learning, fully online.

### Theoretical lineage

- **Plurality** by Audrey Tang and Glen Weyl (2024, Variant C Library entry, forthcoming). The book-length argument for digital democracy as bridging social capital. Extends the conceptual frame beyond token-weighted voting.
- **Governing the Commons** by Elinor Ostrom (1990, Variant C Library entry, forthcoming). The foundational text on collective resource governance. The DAO field has rediscovered Ostrom's design principles repeatedly without often saying so.
- **The Sovereign Individual** by James Dale Davidson and Lord William Rees-Mogg (1997). The libertarian political theory that influenced the early DAO movement. Read as historical context, not as endorsement; the book's class politics are part of why DAO governance is contested in community settings.

### Companion frameworks

- [Doocracy](/library/doocracy). The off-chain initiative pattern that handles the operational layer most DAOs cannot reach.
- [Sociocracy 3.0](/library/sociocracy-3-0). The deliberation framework that pairs well with on-chain voting for proposal development.
- [Embassy Network: Design Patterns and Do-ocracy](/library/embassy-network-design-patterns). The co-living network that documented organizational design patterns including doocracy. Pre-DAO but conceptually adjacent.
- [Mietshäuser Syndikat](/library/mietshauser-syndikat). The non-blockchain mechanism to hold property out of the market across hundreds of buildings; useful comparison.
- Plurality (Variant C Library entry, forthcoming). Audrey Tang and Glen Weyl, 2024.
- Steward-Ownership (Variant A Library entry, forthcoming). The Patagonia, Bosch, Carl Zeiss tradition.

### From the ToGather archive

- [Tias on Collective Building](/interview/6967b061bcc53fba406b8bf9). Renovating a chicken farm with strangers at TDF. The ground-level lived experience.
- [Julia at TDF](/interview/6967af25ea360ea6bc027a20). People see you all the time, even in bad conditions. The community-life layer underneath the governance layer.
- [Tonya Gorman: Maybe Searching Is Not the Answer](/interview/6967a192a0662d4d189b6cce). On choosing to stay at TDF. The relational and personal commitment side of community DAO membership.
- Sam (TDF, draft on Base44). Founder. The procedural walk-through of TDF's DAO. Local file: `Substack/Communities/TDF/interview_sam_luna_tdf.md` and `interview_sam_new_land_tdf.md`. When the interview moves from draft to published, this section will link directly.
- Luna (TDF, draft on Base44). Interior architect, leadership and somatic space-holding. Local file: `Substack/Communities/TDF/interview_sam_luna_tdf.md`.

When the Sam and Luna interviews are published on Base44, this section will be revised to link to them directly.

## Short summary (preview text)

DAO Governance is a system where formal decisions are recorded as votes on a public blockchain, weighted by some combination of tokens, presence, and contribution. Documented in the ToGather archive at Traditional Dream Factory, alongside Cabin DAO, MakerDAO, Nouns, and Gitcoin.