Yes, DAO participants can face personal legal liability, and several federal courts have already said so. If you vote on proposals, hold governance tokens tied to profit, or help run treasury operations, you may be treated as a general partner exposed to joint-and-several liability. The single most urgent step is to stop and get counsel before your next governance vote, then evaluate a legal wrapper and insurance before litigation or a regulator finds you first.
TL;DR:
- Courts have treated DAOs as general partnerships based on participation in management, profit sharing, and contributions, exposing members to joint liability.
- Federal regulators like the SEC, CFTC, and FinCEN already pursue DAOs for securities violations, commodities enforcement, and AML breaches, regardless of their legal structure.
- Forming a DAO LLC or similar legal wrapper offers limited liability protection but requires strict compliance and matching actual governance practices to the formal structure.
- Active governance roles, such as chairing committees or holding keys, increase personal fiduciary and liability risks, especially if associated with ongoing compensation.
- Immediate preservation of records and engagement of experienced legal counsel are crucial to mitigate risks once a dispute or enforcement inquiry appears likely.
Table of Contents
- What Court Cases Define DAO Legal Liability?
- How Do Courts Decide If a DAO Is a Partnership?
- Which Regulators Pursue DAOs, and Why?
- Legal Wrappers: How Much Protection Do They Actually Give?
- Cutting DAO Liability Risk: A Practical Action Plan
- What Happens If a DAO Loses in Court?
- Does the DAO or the Member Face Liability?
- Are DAO Developers and Core Contributors at Risk?
- Do DAO Governance Participants Owe Fiduciary Duties?
- How Does DAO Liability Change Across Borders?
- What Other DAO Liability Outcomes Have Occurred?
- The Gap Between DAO Mythology and DAO Reality
- Get Legal Help Before a DAO Dispute Becomes a Judgment
- Sources
- FAQ
What Court Cases Define DAO Legal Liability?
Three matters now anchor almost every DAO legal liability discussion in the United States, and each one answers a different question about exposure.
Samuels v. Lido DAO put the partnership theory on the map. Plaintiffs alleged that Lido DAO operated as a general partnership, pointing to token-holder voting rights, a shared profit motive tied to staking rewards, and the influence wielded by large token holders over protocol decisions. The court’s willingness to let that theory proceed signaled that a DAO’s decentralized branding does not, by itself, defeat a partnership claim.
Sarcuni v. bZx DAO pushed the analysis further into negligence and duty. Plaintiffs argued that bZx DAO owed a duty of care around protocol security after a hack drained user funds, and that governance participants who profited from the protocol shared responsibility for the security failures that caused the loss. Federal courts have applied partnership tests here and pointed to management participation, profit sharing, and capital contributions as the factors that support treating members as general partners.
Ooki DAO and the CFTC default judgment took a different route entirely. The CFTC sued the DAO directly as an unincorporated association, then served process through its online help chat box and forum when no natural person came forward to accept service. The agency won a default judgment, which practitioners now flag as the clearest warning yet that decentralization does not defeat service of process or associational liability.
- Samuels v. Lido DAO: partnership allegations tied to governance control and profit motive
- Sarcuni v. bZx DAO: negligence and duty-of-care claims tied to security failures
- Ooki DAO / CFTC: unincorporated association theory, default judgment, unconventional service
Later courts increasingly cite agency findings and prior enforcement orders when reasoning through DAO conduct, treating an administrative record as evidence that a decentralized structure was still capable of coordinated action.
How Do Courts Decide If a DAO Is a Partnership?
Courts do not ask whether a DAO calls itself decentralized. They ask whether the fact pattern matches the traditional indicia of a general partnership under state law, and those indicia translate directly into risk factors you can audit right now.
Judges typically weigh three things: whether members participated in management or decision-making, whether they shared in profits generated by the protocol, and whether they made contributions of capital, labor, or code. Courts look for indicia of profit motive, managerial control, and direct influence by founders or large token holders when deciding whether to apply partnership law. A retail holder who never votes looks very different from a delegate who chairs a governance committee.
Agency and representative liability raises a separate problem: who gets named as a defendant, and how do you serve them? Courts have shown they will name individual signers, multisig key holders, and even vocal forum participants when a plaintiff cannot identify a corporate entity to sue instead.
Securities exposure runs on its own track. If a token functions as an investment contract, offering or selling it can trigger Section 12 liability or registration requirements regardless of how the sale was structured, an issue worth understanding through a full investment contract analysis.
- General partnership indicia: management participation, profit sharing, capital or labor contributions
- Agency exposure: multisig signers, delegates, and vocal governance participants can be named individually
- Securities exposure: token structure and sale conduct can trigger Section 12 or registration liability
- Tort and contract exposure: governance votes tied to security failures can support negligence claims
Pro Tip: Before you cast your next governance vote, ask whether the proposal creates a paper trail suggesting managerial control over treasury funds. That paper trail is exactly what plaintiffs’ lawyers request first in discovery.
Which Regulators Pursue DAOs, and Why?
Federal exposure runs on a separate track from private litigation, and DAOs face at least three regulators with distinct legal theories.
The SEC treats certain governance tokens as securities when they meet the Howey investment-contract test, focusing on how a token was offered, sold, and marketed rather than its technical label. The CFTC claims authority over commodity and derivatives activity and has already secured a real enforcement win: its Ooki DAO case ended in a default judgment establishing that an unincorporated association can be sued and held liable under the Commodity Exchange Act. FinCEN enters the picture whenever a DAO’s treasury functions like a money-transmission business, triggering AML and reporting obligations that most governance token holders never anticipate signing up for.
- SEC: securities registration and offer/sale theories tied to token economics
- CFTC: commodities and derivatives enforcement, backed by a successful default judgment against Ooki DAO
- FinCEN/AML: reporting duties triggered when a DAO treasury moves funds like a money-services business
State DAO statutes do not neutralize any of this. Wyoming, Tennessee, Utah, and Vermont each created frameworks meant to give DAOs a recognizable legal form, but state-level recognition does not shield a DAO from federal regulators or from a judge who looks past the entity structure when partnership indicia are present, according to the Harvard Law School Forum on Corporate Governance. A Wyoming filing helps with predictability. It does not make the SEC or CFTC disappear.
Legal Wrappers: How Much Protection Do They Actually Give?
State DAO statutes offer a real starting point, but the protection they provide is narrower than most founders assume, and the gap between “filed” and “protected” is where most disputes end up.
Wyoming’s DAO LLC statute and comparable frameworks in Tennessee, Utah, and Vermont extend LLC-style limited liability to DAO members who organize under them, provided the DAO actually follows the statute’s formalities. Academic reviews of these frameworks recommend careful attention to formal organization precisely because predictability and reduced individual exposure come at the cost of some decentralization that many communities value. Utah and Wyoming in particular offer clearer statutory pathways, but the scope of that protection still depends on careful drafting and ongoing compliance, not just the initial filing.
An LLC or foundation wrapper can insulate individual members from personal liability, but courts retain the power to “look through” any entity when the underlying conduct shows the entity was a formality rather than a genuine operating structure. That look-through risk is exactly why relying on a state statute alone, without matching internal practice to its formalities, does not eliminate federal or judicial risk.
- Match your operating agreement’s actual governance practice to the statute you filed under. Gaps between paper and practice are the first thing opposing counsel will find.
- Separate governance rights from profit rights in your token design wherever feasible, since combining both is what most invites partnership claims.
- Draft token-holder agreements that clearly disclaim partnership intent and define the scope of member authority.
- Address cross-border members explicitly. A US wrapper does not resolve whether a foreign regulator treats your token holders as partners under their own law.
Cutting DAO Liability Risk: A Practical Action Plan
Reducing exposure means combining legal form with operational discipline. Skipping any one leg of that stool leaves a gap that plaintiffs’ counsel will find.
Start with the legal wrapper itself: form an LLC, foundation, or DAO LLC under a statute suited to your governance model, register it properly, and keep the formalities current every year, not just at launch. From there, narrow governance powers where you can, separate profit rights from voting rights, and document every material decision so there is a clean record of who decided what and why.
- Form and maintain a legal wrapper, then actually operate consistently with its formalities
- Narrow governance scope and document decision-making in writing, every time
- Implement multisig custody, independent security audits, and an active bug-bounty program
- Carry Directors & Officers and technology errors-and-omissions insurance, and revisit coverage annually
- Preserve communications, treasury records, and on-chain snapshots the moment a dispute looks possible
Technical controls matter as much as paperwork. Multisig custody, regular smart contract audits, and a live bug-bounty program reduce the odds that a security failure ever becomes a negligence claim in the first place. Insurance closes the gap that no amount of drafting can close on its own: D&O coverage and technology errors-and-omissions policies exist specifically for the moment governance decisions or code failures turn into lawsuits. Practical mitigation mixes legal form, technical controls, and insurance, and skipping any one of the three leaves an exploitable gap.
Pro Tip: The moment a dispute looks even possible, stop certain governance votes, snapshot the on-chain state, and preserve chat logs and treasury records before anything gets deleted or overwritten. Counsel typically recommends exactly these steps at first contact, and waiting even a few days can destroy evidence a defense depends on. Review your token launch practices against a full compliance checklist well before a regulator asks you to.
What Happens If a DAO Loses in Court?
Losing a DAO liability case rarely means a clean, capped judgment against a single entity. It usually means something messier.
Joint-and-several liability is the headline risk. When a court treats a DAO as a general partnership, every partner can be held responsible for the full judgment, not just their proportional share, which means a plaintiff can collect the entire award from whichever member has the deepest pockets or the most identifiable assets. That exposure extends to personal assets: wallets, staked tokens, and even off-chain property can become targets once a judgment attaches to an individual rather than an entity shell.
Service of process creates its own headaches. Ooki DAO showed that a plaintiff or regulator does not need to find a named officer; serving a forum post or help-chat box can satisfy due process when no natural person steps forward. That means members who assumed anonymity offered protection have been proven wrong in a real, precedent-setting case.
Tax and reporting consequences follow close behind. A DAO treated as an unincorporated association or partnership for liability purposes may also face partnership-style tax treatment, meaning members could owe pass-through tax liability on protocol income they never personally received, plus penalties for unfiled returns. Combine that with potential FinCEN reporting failures on treasury movements, and a single adverse ruling can trigger liability on three fronts simultaneously: civil judgment, tax exposure, and regulatory penalty.
Does the DAO or the Member Face Liability?
This distinction confuses even sophisticated founders, and it matters enormously once a lawsuit is actually filed.
When a DAO exists inside a proper legal wrapper, an LLC, foundation, or cooperative, the entity itself is generally the party that can be sued and that bears liability, with member exposure limited to their investment much like a traditional LLC member. The entity’s assets, not the members’ personal wallets, are the first target.
When a DAO has no wrapper, courts increasingly treat the DAO itself as an unincorporated association or general partnership, which collapses the distinction entirely. There is no separate “entity” shielding anyone; the members are the liable parties, and the DAO’s treasury is simply a pool of jointly held partnership assets. Federal courts have allowed plaintiffs to allege exactly this structure, exposing unincorporated DAO participants to joint and several liability rather than protecting them behind an entity veil.
The practical lesson: the wrapper is what creates the distinction in the first place. Without it, “the DAO” and “the members” are legally the same target, and every governance participant inherits exposure proportional to their involvement, whether they ever intended to accept that risk or not.
Are DAO Developers and Core Contributors at Risk?
Developers and core contributors face a liability profile distinct from ordinary token holders, and it is often more acute because their conduct is easier to document.
Writing and deploying smart contracts creates a direct causal link between a developer’s work and any resulting harm, which makes negligence and product-liability theories easier to plead against contributors than against passive holders. Sarcuni v. bZx DAO leaned on exactly this logic, tying a security failure back to decisions made by those responsible for the protocol’s technical operation and governance.
Core contributors who continue drawing compensation, whether in tokens, stablecoins, or fiat, after a project transitions to “decentralized” governance face particular scrutiny. Courts and plaintiffs alike treat continued paid involvement as evidence that decentralization was more branding than reality, undermining any argument that the contributor had stepped back from managerial control.
Public-facing roles compound the risk. Developers who post roadmaps, respond to community concerns, or make representations about security audits create a documentary record that plaintiffs can use to argue duty of care, actual knowledge of risk, or managerial authority, regardless of what the organization’s formal structure claims. Reviewing personal exposure specific to your role, especially if you hold keys or sit on a security council, deserves a look at how executive liability risks actually attach in practice.
Do DAO Governance Participants Owe Fiduciary Duties?
Fiduciary duty analysis in DAOs remains unsettled, but the trend line points toward greater exposure for anyone exercising real control.
Traditional corporate law imposes duties of care and loyalty on directors and officers who control corporate assets on behalf of others. DAOs complicate this because governance authority is often diffuse, held by thousands of anonymous token holders rather than a defined board. Courts have started filling that gap by importing partnership-law duties instead: when a participant looks and acts like a managing partner, controlling treasury decisions or influencing protocol direction, courts have been willing to impose duties analogous to those a general partner owes co-partners.
Large token holders and delegates face the sharpest version of this problem. When an institutional investor actively participates in governance, courts are more willing to treat that investor as a partner bearing fiduciary-style obligations, creating a meaningfully different risk profile than the one facing a retail holder who never votes. That asymmetry means the DAO members with the most influence over outcomes also carry the most exposure if those outcomes go wrong.
The practical upshot: any participant who chairs a committee, controls a multisig key, or votes a large delegated stake should assume fiduciary-style duties apply to them, even absent a formal appointment. Acting as though those duties do not exist because no one signed a director agreement is not a defense a court is likely to accept.
How Does DAO Liability Change Across Borders?
DAOs by design ignore borders, but courts and regulators do not, which creates a genuinely difficult compliance puzzle for any project with a global token-holder base.
A US-based legal wrapper resolves domestic liability questions but says nothing about how a French, Singaporean, or UAE regulator treats the same token holders under their own securities, tax, or partnership law. A token holder physically located outside the United States may still face liability exposure under their home jurisdiction’s rules, even while the DAO itself operates under a Wyoming DAO LLC filing that fully satisfies US requirements.
Enforcement coordination adds another layer. US regulators increasingly share findings with foreign counterparts, and a CFTC or SEC action against a DAO can prompt parallel scrutiny abroad, particularly where treasury funds moved through exchanges or custodians subject to multiple regulatory regimes. Multinational contributor teams also face a patchwork of local labor, tax, and corporate law that a single US entity wrapper cannot paper over.
The realistic approach for any DAO with meaningfully international participation is layered compliance: a primary US wrapper for domestic liability protection, supplemented by jurisdiction-specific legal review wherever a significant concentration of token holders, contributors, or treasury activity exists. Treating US compliance as sufficient for a genuinely global membership is one of the more common and costly assumptions founders make.
What Other DAO Liability Outcomes Have Occurred?
Beyond the three headline cases, a broader pattern of smaller disputes shows how varied DAO liability outcomes actually are in practice.
Several DeFi protocols facing exploits have seen governance participants named alongside the protocol itself in demand letters, even when litigation never proceeded to a filed complaint, because plaintiffs’ counsel routinely name every plausible defendant before narrowing the field during discovery. That pattern alone should worry any contributor who assumes anonymity or a pseudonymous handle offers real protection.
Regulatory settlements outside the CFTC’s Ooki action have followed a consistent script: an agency identifies a treasury-controlling wallet or a small group of founding contributors, issues a subpoena or civil investigative demand, and negotiates a resolution before the matter ever reaches a courtroom. These outcomes rarely make headlines because they resolve quietly, but they represent the most common real-world liability event a DAO actually faces, far more often than a headline federal court ruling.
Insurance-backed resolutions have also emerged as a quieter category of outcome. Projects that carried D&O or technology errors-and-omissions coverage before a security incident or governance dispute have, in several instances, resolved claims through negotiated settlements funded by that coverage rather than personal assets, underscoring why insurance sits alongside legal form and technical controls as a core mitigation layer rather than an afterthought.
The Gap Between DAO Mythology and DAO Reality
Founders keep treating “decentralized” as a legal shield, and the courts keep proving them wrong. That gap between mythology and reality is where most of the exposure in this space actually lives.
The pattern we see most often is a community that talks like a company long before it gets sued like one. Roadmaps, security audit announcements, and governance forum posts promising future returns read to a plaintiff’s lawyer exactly like evidence of profit motive and managerial control, the two ingredients partnership law cares about most. In litigation, courts and plaintiffs lean heavily on public governance records and promotional statements to establish exactly that kind of control and intent, which means the marketing team’s enthusiasm can become the litigation team’s worst exhibit.
Procedural traps do the rest of the damage. Ooki DAO proved that service on a forum or help-chat box works, and default judgments follow fast when no one shows up to defend the organization. By the time most contributors realize a case is real, the window for a coordinated defense has already closed, and the resolution is often FinCEN reporting obligations or an entire discovery database subpoenaed before counsel is engaged. Timely engagement is not a formality. It is frequently the difference between a negotiated outcome and an unopposed default.
— Mark
Get Legal Help Before a DAO Dispute Becomes a Judgment
You can get litigation and compliance help beyond generic “DAO legal help” forums and DIY wrapper templates by working with a licensed firm experienced in crypto disputes, rather than relying on generic documents filed without specific review of your governance structure.
An engagement typically starts with an assessment of your governance history, treasury controls, and any public statements that could be read as evidence of partnership intent, followed immediately by preservation steps for communications and on-chain records if a dispute already looks likely. From there, the firm handles crypto fraud recovery litigation for DAOs and members targeted by bad actors, regulatory defense for enforcement inquiries, and compliance program development for DAOs that want their treasury and AML practices, including KYC review, in order before a regulator asks first. If your DAO faces an active dispute, a subpoena, or you simply want your governance structure reviewed before your next vote, request an assessment through Murphy’s Law’s crypto fraud recovery litigation page to start the conversation now.
Sources
- A primer on DAOs (Harvard Law School Forum on Corporate Governance)
- How to resolve a dispute involving a DAO (Duke FinReg Blog)
FAQ
What Is a DAO in Legal Terms?
Courts have not settled on one uniform legal category. Depending on the facts, a DAO can be treated as a general partnership, an unincorporated association, or, if properly formed, a limited liability entity under a state DAO statute.
Does XRP Have a DAO?
XRP and Ripple do not operate through a decentralized autonomous organization structure. XRP is issued and largely managed by Ripple Labs, a traditional corporate entity, which is a fundamentally different governance and liability model than a DAO.
What Is an Example of a DAO?
Lido DAO and bZx DAO are two of the most litigated examples, both now central to how US courts analyze DAO legal liability. Both faced lawsuits alleging their governance structures functioned as general partnerships.
What Does Federal Law Say About DAOs?
No single federal statute defines DAOs, but the CFTC has already won a default judgment treating Ooki DAO as an unincorporated association liable under the Commodity Exchange Act, and the SEC continues applying securities law to governance tokens that meet the investment-contract test.
Can DAO Members Avoid Personal Liability Entirely?
No approach eliminates risk completely, but forming a proper legal wrapper, such as a Wyoming or Utah DAO LLC, limiting governance control, and maintaining insurance meaningfully reduces the odds of personal exposure compared with operating with no entity at all.