The Common Enterprise Doctrine is the SEC's new legal weapon. It argues that token value is derived from a promoter's managerial efforts, not just a specific contract, allowing them to target the protocol's foundational code and governance.
Why 'Common Enterprise' Is the SEC's Next Legal Battleground
An analysis of how the SEC is shifting its legal strategy to use the 'common enterprise' prong of the Howey Test to assert jurisdiction over crypto projects by tying token value to core developer activities, even in seemingly decentralized ecosystems.
Introduction: The Pivot from 'Investment Contract' to 'Common Enterprise'
The SEC's enforcement strategy is shifting from the Howey Test's 'investment contract' analysis to the 'common enterprise' doctrine, targeting the underlying protocol layer itself.
This is a structural attack on decentralized finance. Unlike the contract-based Howey Test, this doctrine implicates the entire protocol architecture, from Uniswap's fee switch to Lido's staking module, as potential securities.
The SEC's target is coordination. By focusing on the collective efforts of core developers and DAOs like Arbitrum or Optimism, they aim to prove a centralized 'enterprise' exists, regardless of user intent.
Evidence: The SEC's case against Terraform Labs established that algorithmic stablecoins like UST can constitute a common enterprise, setting a precedent for attacking protocol-level economics.
The SEC's New Playbook: Three Key Trends
The SEC is moving beyond the Howey Test's 'investment of money' prong to attack the 'common enterprise' and 'expectation of profits' elements in crypto.
The Problem: Fragmented 'Common Enterprise' Arguments
The SEC is no longer relying solely on token sales. It's now arguing that protocol governance, staking rewards, and treasury management create a de facto common enterprise. This turns decentralized coordination into a legal liability.
- Target: DAOs and staking-as-a-service providers.
- Precedent: The LBRY and Terraform Labs cases expanded this definition.
- Risk: Successful prosecution here could classify most active Layer 1s and DeFi protocols as securities.
The Solution: Protocol Neutrality & Passive Infrastructure
Projects must architect to disprove 'common enterprise.' This means minimizing centralized development promises and building credibly neutral infrastructure.
- Model: Emulate Bitcoin and Ethereum's post-merge stance—no entity promises profits.
- Tactic: Decouple foundation from protocol; use trustless multi-sigs like Safe{Wallet} for treasury.
- Execution: Document all governance decisions as user-driven, not management-driven.
The Problem: 'Expectation of Profits' From Staking
The SEC's case against Coinbase and Kraken staking services sets a dangerous precedent. It argues that staking rewards constitute a security because they are derived from the managerial efforts of the protocol.
- Target: Centralized exchanges and liquid staking tokens (Lido's stETH, Rocket Pool's rETH).
- Mechanism: Rewards are framed as dividends from a common enterprise.
- Exposure: $50B+ in total value locked in liquid staking derivatives is now in the crosshairs.
The Solution: Non-Custodial, Permissionless Staking Pools
Mitigate risk by architecting staking where users retain sole control and rewards are algorithmic, not discretionary.
- Blueprint: Rocket Pool's decentralized node operator network.
- Requirement: No central entity controlling funds or setting reward rates.
- Verification: Use EigenLayer's cryptoeconomic security or similar trust-minimized designs.
The Problem: The 'Ecosystem Fund' as a Securities Pool
Large foundation-controlled treasuries used for grants and incentives are being framed as a pool of capital from which investors expect profits. The SEC views developer grants and liquidity mining as promotional efforts that fuel the common enterprise.
- Target: Major Layer 1 foundations like Solana, Avalanche, and Polygon.
- Evidence: Public roadmap updates and grant announcements become exhibits.
- Scale: Billions in ecosystem funds are now potential evidence of managerial control.
The Solution: Transparent, Exhausted Treasuries & Trustless Grants
Convert the foundation from an active manager to a spent force. Use retroactive public goods funding models and on-chain voting for all allocations.
- Model: Adopt Optimism's RetroPGF or Gitcoin Grants framework.
- Action: Burn or permanently lock a majority of the treasury after initial decentralization.
- Proof: Maintain a public ledger showing zero discretionary spend post-launch.
Deconstructing 'Common Enterprise': From Legal Theory to On-Chain Reality
The SEC's 'common enterprise' test is the critical, unresolved legal framework that will determine the regulatory fate of decentralized protocols.
The Howey Test's Core is the 'common enterprise' requirement, where investor profits are tied to the efforts of a promoter or third party. In crypto, this maps directly to the relationship between token holders and core developers or DAOs.
Protocols are legal chameleons. A protocol like Uniswap or Compound can morph from a decentralized utility to a regulated security if a court finds its DAO's governance constitutes a controlling 'third party' managing a common enterprise.
On-chain activity creates evidence. Every governance vote, treasury allocation, and grant from a MolochDAO or Optimism Collective is a public record the SEC uses to argue for centralized managerial efforts benefiting token value.
The precedent is LBRY. The SEC successfully argued LBRY's token issuance and development roadmap created a common enterprise where investor fortunes rose and fell with the company's managerial efforts, setting a dangerous template.
Case Study Matrix: How 'Common Enterprise' Applies to Major Protocols
A comparative analysis of major crypto protocols against the three-pronged 'Howey Test' for a common enterprise, focusing on the critical element of profit expectation from the efforts of others.
| Legal Prong / Operational Feature | Ethereum (ETH) | Uniswap (UNI) | Lido DAO (LDO) | MakerDAO (MKR) |
|---|---|---|---|---|
Investment of Money | ||||
Common Enterprise: Horizontal | Proof-of-Stake Validator Pool | Liquidity Provider Pools | Staked ETH Pool (stETH) | DAI Savings Rate (DSR) Pool |
Common Enterprise: Vertical | Core Devs (EF) + Client Teams | Uniswap Labs + Governance | Lido DAO + Node Operators | Maker Foundation + Core Units |
Profit Expectation: Primary Source | Protocol Security Fee Burn (EIP-1559) | Trading Fee Revenue (0.01%-1%) | Staking Rewards (3-4% APY) | Stability Fee Revenue (Variable) |
Profit Relies on Managerial Efforts | High (Roadmap, EIPs, Client Updates) | Medium-High (V4, UniChain, Treasury Mgmt) | High (Node Operator Slashing, Oracle Mgmt) | High (Collateral Onboarding, Risk Parameters) |
Decentralization Defense (Active Devs) | ~200 (Across 5+ Clients) | ~50 Core (Uniswap Labs) | ~30 Core (Lido Contributors) | ~100 (Across Core Units) |
SEC Lawsuit/ Wells Notice Status | No (Commodity Designation) | Yes (2020, Closed) | No (Under Scrutiny) | No |
The Counter-Argument: When Is a Protocol Truly Decentralized?
The SEC's 'common enterprise' test is the existential legal threat to protocols that rely on centralized development and governance.
The Howey Test's 'Common Enterprise' is the SEC's primary weapon. It defines an investment contract based on profits derived from the efforts of others. For protocols like Uniswap or Aave, the SEC argues the core development team and foundation constitute that central, profit-driving 'enterprise'.
Decentralization is a spectrum, not a binary. The SEC targets points of centralization: foundation-controlled treasuries, multi-sigs for upgrades, and reliance on centralized oracles like Chainlink. A protocol's legal status depends on its weakest centralized component.
Protocols must pass the 'sufficient decentralization' threshold to escape securities law. This requires irreversible smart contracts and community-led governance without founder influence. Many 'DeFi blue chips' fail this test due to their upgradeable proxies and foundation veto powers.
Evidence: The SEC's case against Coinbase explicitly argued that staking services constitute a common enterprise. This precedent directly implicates Lido's stETH and other liquid staking tokens, where a core entity manages validator operations.
Builder's Risk Assessment: Who Is Most Exposed?
The 'common enterprise' doctrine is the SEC's primary weapon to classify tokens as securities. This is a first-principles breakdown of which protocols are most vulnerable.
The Foundation & Treasury Problem
Protocols with a centralized foundation controlling a $100M+ treasury and funding development are painting a target on their back. The SEC argues this creates a single, dependent enterprise where token value is tied to the foundation's managerial efforts.
- Key Risk: Direct funding of core devs from treasury.
- Key Risk: Foundation-led roadmap and governance proposals.
- Mitigation: Move to fully permissionless, grant-based funding like Optimism's RetroPGF.
The Staking-as-Security Trap
Centralized staking services and protocol-native staking with promised yields are low-hanging fruit. The SEC's case against Kraken established that offering returns from a pool of assets can be an investment contract.
- Key Risk: Marketing token staking as an income-generating product.
- Key Risk: Lido (LDO) and similar pooled staking derivatives.
- Mitigation: Pure Delegated Proof-of-Stake (DPoS) where rewards are protocol inflation, not a profit share.
The 'Essential Function' Token
Tokens whose sole utility is governance over a profitable, centralized service are exposed. If the token doesn't enable the core protocol function (e.g., Filecoin for storage, Helium for coverage), it's just a speculative bet on the team's success.
- Key Risk: Token is not technically required for network operation.
- Key Risk: Uniswap (UNI) as the canonical example of a 'non-essential' governance token.
- Mitigation: Fee switch activation that directly ties token value to protocol cash flows.
The VC-Backed Launch
Projects that conducted a private sale to VCs with promises of future exchange listings and ecosystem development have already created a common enterprise. Public token distribution is often just a liquidity event for insiders.
- Key Risk: SAFTs (Simple Agreements for Future Tokens) are explicit investment contracts.
- Key Risk: VC vesting schedules that align token success with managerial efforts.
- Mitigation: Fair launches, liquid bonding curves, or worker token models like Threshold Network.
Why 'Common Enterprise' Is the SEC's Next Legal Battleground
The SEC's 'common enterprise' doctrine is the primary legal weapon for classifying crypto assets as securities, focusing on the network's managerial dependency.
The Howey Test's Core: The SEC's enforcement hinges on the third prong of the Howey Test: a 'common enterprise' where investor profits depend on the managerial efforts of others. This is the legal linchpin for labeling tokens as securities, not the technology itself.
Protocol vs. Promoter: The critical distinction is between a decentralized protocol like Ethereum or Uniswap and a token sale where a central team's roadmap drives value. The SEC argues that pre-launch tokens and those with active foundation development constitute a managerial common enterprise.
The Decentralization Defense: Projects like Filecoin or The Graph aim to pass this test by ceding protocol upgrades to community governance. The legal battle centers on whether this transition is substantive or a cosmetic decentralization that masks ongoing promoter control.
Evidence: The SEC's case against Ripple Labs explicitly argued XRP represented an investment in a common enterprise managed by Ripple, a precedent now applied to dozens of subsequent lawsuits against centralized token issuers.
TL;DR for Protocol Architects
The 'Common Enterprise' test is the SEC's primary weapon to classify tokens as securities; your protocol's design determines its legal fate.
The Problem: Howey's 'Common Enterprise'
The SEC argues token value depends on a centralized managerial effort, not just code. This makes staking rewards, treasury management, and core dev roadmaps into evidence of a security. The legal risk is binary: fail this test, face multi-year lawsuits like Ripple and Coinbase.
The Solution: Protocol Neutrality & Forkability
Architect for credible exit and irrelevance. Design where the core dev team can vanish and the protocol persists. Key levers:\n- Fully on-chain, immutable governance (e.g., early Uniswap)\n- Permissionless forking with no penalty\n- Treasury controlled by broad, decentralized DAO
The Precedent: Ripple's Partial Victory
Ripple's XRP ruling created a critical distinction: institutional sales were securities, but programmatic sales on exchanges were not. This sets a template. For architects, it means:\n- Avoid direct, negotiated token sales to funds\n- Ensure liquid, impersonal secondary markets exist at launch\n- Decouple token utility from funding promises
The Counter-Strategy: The 'Consumption Asset' Argument
Frame your token as a pure utility good, like cloud computing credits or gas. This requires deliberate design choices:\n- Token is required for core protocol function (e.g., ETH for gas, FIL for storage)\n- No profit-sharing or dividend-like mechanisms\n- Value accrual is from utility demand, not promotional efforts
The Red Flag: Centralized 'Ecosystem Funds'
A centralized foundation deploying capital to bootstrap projects is a prime SEC target. It's seen as managerial effort driving token value. Mitigate by:\n- Using community-run grants programs (e.g., Optimism's Citizen House)\n- Making investments from a DAO treasury with broad participation\n- Avoiding token-based VC raises with explicit ROI expectations
The Litmus Test: The 'Venture Capital' Question
Ask: Would a traditional VC invest in this token expecting profits from our work? If yes, you've likely created a security. Architect to make the answer 'no'. This means:\n- Launch with sufficient decentralization from Day 1\n- Token has inherent, non-speculative utility\n- Team's future involvement is not critical to value
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.