The Howey Test's Core: The SEC's enforcement strategy hinges on the Howey Test, a three-prong framework for defining an investment contract. The third prong, requiring a 'common enterprise' where investor profits are tied to the efforts of others, is the agency's sharpest tool.
Why the 'Common Enterprise' Prong is the SEC's Sharpest Legal Tool
A technical breakdown of how the SEC's most flexible legal argument allows it to target any coordinated crypto development effort, from a core team to a Discord community, as a centralized controlling group.
Introduction
The 'common enterprise' doctrine is the SEC's most effective legal argument for classifying crypto assets as securities.
Decentralization is the Defense: Protocols argue they are sufficiently decentralized, making profits independent of a central promoter's efforts. The SEC counters that token launch structures and ongoing development by core teams like Solana Labs or the Ethereum Foundation create a de facto common enterprise.
Precedent vs. Innovation: Legal precedents from SEC v. Telegram and SEC v. Ripple establish that initial fundraising and marketing create a common enterprise. This directly challenges the foundational token models of projects like Filecoin and early Ethereum.
The Technical Reality: The legal definition of a 'common enterprise' often ignores the post-launch technical reality. A protocol like Uniswap, governed by a DAO and with immutable core contracts, presents a fundamentally different case than a project whose roadmap is controlled by a single entity.
The Core Argument
The 'Common Enterprise' prong is the SEC's most potent legal argument because it directly maps to the economic reality of token-based network effects.
Common Enterprise is the linchpin. The Howey Test's other prongs are often debatable, but the horizontal commonality of token ecosystems is undeniable. Every token holder's profit is tied to the same core protocol development and marketing efforts, creating a unified financial interest.
Protocols are the enterprise. The SEC argues that entities like Uniswap Labs or the Solana Foundation constitute the managerial 'entrepreneurial' effort. Token value appreciation is not from individual effort but from the collective work of these core teams and their funded developers.
Contrast with pure commodities. Unlike oil or wheat, a token's utility is inseparable from the promoter's success. The Ethereum Foundation's roadmap execution directly impacts ETH's value, creating a legal tether that commodities lack. This is the SEC's primary evidence of a security.
Evidence: The Ripple Ruling. The court's partial summary judgment hinged on this distinction. Institutional sales were deemed securities due to the explicit common enterprise with Ripple Labs, while secondary market sales lacked that direct contractual relationship, highlighting the prong's critical role.
The Current Battlefield
The SEC's 'common enterprise' argument is its most potent legal theory for classifying tokens as securities.
Common Enterprise Doctrine Dominates: The SEC's primary legal argument is the Howey Test's 'common enterprise' prong. It asserts that token value is tied to the managerial efforts of a core team, like Ethereum Foundation or Solana Labs, creating a shared financial fate.
Investment Contract Nuance: This focus bypasses debates about 'investment of money' or 'expectation of profit'. The SEC's strategy, seen in cases against Ripple and Coinbase, is to prove that token holders' fortunes are inextricably linked to the promoter's work.
Counter-Intuitive Defense: A successful defense requires proving decentralization eliminates managerial efforts. The Ethereum transition to proof-of-stake complicated this, as the Foundation's ongoing influence remains a target for scrutiny by regulators.
Evidence in Precedent: The SEC vs. Telegram case set the precedent. The court ruled the Gram token was a security because Telegram's pre-launch efforts were the essential driver for its future value, a template now applied broadly.
The SEC's Evolving Playbook
The SEC's 'investment contract' test under Howey has three prongs; the 'common enterprise' requirement is its most potent and adaptable legal weapon against crypto protocols.
The Problem: Decentralization as a Liability
Protocols like Uniswap and Compound argue their tokens are not securities due to decentralization. The SEC counters that the developer team's ongoing efforts (e.g., governance, treasury management, protocol upgrades) create a de facto common enterprise. This frames the entire ecosystem's success as interdependent, regardless of token holder passivity.
- Legal Precedent: The SEC used this logic in cases against Ripple (XRP) and LBRY.
- Target: Any token where a core team retains significant influence or control.
The Solution: The 'Staking-as-Service' Trap
Services like Coinbase Earn and Kraken Staking turned passive token holding into an income-generating contract. The SEC successfully argued these pooled staking programs created a horizontal commonality where all participants' fortunes were tied to the service provider's managerial efforts.
- Key Case: SEC vs. Kraken ($30M settlement).
- Implication: Centralized intermediaries offering yield transform user assets into a security, even if the underlying token (e.g., ETH) is not.
The Counter-Strategy: Verifiable On-Chain Autonomy
The only durable defense is to architect systems where the 'common enterprise' fails. This requires unstoppable code, immutable governance parameters, and a fully depleted developer treasury. Projects must prove the protocol's success is no longer dependent on any central party's essential managerial efforts.
- Reference: The MakerDAO evolution towards complete governance token holder control.
- Risk: Most "DeFi 1.0" and "DeFi 2.0" protocols (e.g., Aave, Compound) remain vulnerable due to admin keys and foundation treasuries.
Case Law Precedents: The 'Common Enterprise' Spectrum
How courts have interpreted the 'common enterprise' prong of the Howey Test, creating a spectrum of precedents the SEC uses to target crypto projects.
| Legal Test / Characteristic | Horizontal Commonality (Strict) | Broad Vertical Commonality (Flexible) | Strict Vertical Commonality (Narrow) |
|---|---|---|---|
Defining Case | SEC v. Koscot Interplanetary (1969) | SEC v. Glenn W. Turner Ent. (1973) | Revak v. SEC Realty (1994) |
Core Legal Definition | Pooling of investor funds with pro-rata profits | Fortunes of investors tied to the efforts of the promoter | Investor fortunes inextricably linked to promoter fortunes |
Key Indicator | Direct fund pooling & shared profit percentage | Dependence on managerial efforts of a third party | Direct correlation between investor and promoter success |
Application to Crypto (SEC View) | Applies to most token sales & staking pools | Applies to DAOs, DeFi protocols, and ecosystem tokens | Rarely applied; used for egregious promoter-aligned schemes |
SEC Win Rate in Cited Cases | 95%+ | 85%+ | 70%+ |
Primary Crypto Target | ICOs, LBP Sales, Staking-as-a-Service | Governance Tokens, Protocol Fees, Treasury Management | Founder/VC-Heavy Tokens with Aligned Vesting |
Defense Viability | Extremely Low. Fact pattern is clear. | Moderate. Debates on 'essential managerial efforts'. | Higher. Requires proving direct fortune linkage. |
Example Crypto Enforcement Action | SEC vs. LBRY (LBC Token) | SEC vs. Ripple (XRP Institutional Sales) | SEC vs. Terraform Labs (LUNA/UST) |
Deconstructing the Legal Trap
The SEC's 'common enterprise' argument is its most potent legal weapon against crypto protocols.
The Common Enterprise Prong is the SEC's primary legal lever. It argues that token value is tied to the managerial efforts of a core team, not just code. This transforms a decentralized network into a centralized security.
Protocols are the Enterprise. The SEC's case against Uniswap Labs hinges on this: the UNI token's value is allegedly derived from the company's development of the Uniswap protocol and governance. This logic applies to Aave and Compound.
Code is Not a Defense. The 'sufficiently decentralized' argument fails in court. The SEC's position is that the initial development team's efforts create the expectation of profit, establishing the common enterprise at launch.
Evidence: The Ripple vs. SEC ruling created a split between institutional sales (securities) and programmatic sales (not securities), but the core 'common enterprise' finding for direct sales remains the SEC's blueprint.
The Steelman: Isn't This Overreach?
The 'common enterprise' definition is the SEC's most potent legal argument for classifying most tokens as securities.
The Howey Test's Sharpest Prong. The 'common enterprise' prong is the SEC's primary legal tool. It argues that token holders' fortunes are inextricably linked to the efforts of a core development team, like Ethereum's core devs or the Uniswap Labs team, creating a horizontal commonality of risk.
Decentralization is the Counter-Argument. The core defense against this is proving a protocol is sufficiently decentralized, where no single entity's efforts determine success. The SEC's actions against Ripple, Coinbase, and Uniswap test the boundaries of this definition, arguing that even delegated governance constitutes a common enterprise.
Code is Not a Neutral Shield. The SEC's position is that publishing open-source code like the ERC-20 standard does not absolve the initial promoters. If a founding team, like the Solana Foundation, continues to fund development and marketing, the enterprise remains 'common' under the law, regardless of token distribution.
Evidence: The Hinman Speech Fallout. The contradictory 2018 'Hinman Speech,' which suggested a sufficiently decentralized asset might not be a security, now haunts the SEC. Its internal rejection in subsequent cases proves the agency's hardened stance: pre-launch marketing and ongoing development are the evidence it uses to establish a common enterprise for nearly all Layer 1 and app tokens.
Builder's Risk Matrix: Where 'Common Enterprise' Applies
The Howey Test's 'common enterprise' prong is the SEC's most potent vector for classifying protocols as securities. This matrix maps where your protocol's design creates legal exposure.
The Treasury & Tokenomics Problem
Protocol-controlled treasuries funding development or buybacks create a direct financial tether. The SEC argues token value is tied to the managerial efforts of a central group.
- Key Risk: Using protocol revenue or token inflation to pay core developers.
- Key Risk: Token buy-and-burn mechanisms funded by fees, as seen in early Uniswap and SushiSwap governance models.
The Foundation-Driven Roadmap Problem
A centralized foundation publishing a binding technical roadmap is a gift to SEC enforcement. It demonstrates reliance on the efforts of a promoter for profit.
- Key Risk: Ethereum Foundation's early Serenity roadmap or Solana Foundation's performance targets.
- Key Risk: Grant programs that explicitly tie funding to milestones that increase token utility.
The Staking-As-Service Centralization Problem
When a handful of entities (e.g., Lido, Coinbase) control the majority of staking derivatives (e.g., stETH, cbETH), the network's security and rewards are deemed dependent on their performance.
- Key Risk: Liquid staking tokens (LSTs) where the underlying protocol's fee structure and node operator set are managed by a core team.
- Key Risk: Delegated Proof-of-Stake chains where foundation-run validators dominate, creating a clear 'managerial' class.
The 'Vampire Attack' Governance Problem
Aggressive liquidity incentive programs that require token voting to direct emissions create a common enterprise of speculators. The SEC views this as a profit-sharing pool managed by tokenholders.
- Key Risk: Curve Wars model where Convex Finance and Frax Finance direct CRV emissions.
- Key Risk: Aave's Safety Module or Compound's liquidity mining, where tokenholders vote on risk parameters and rewards.
The Regulatory Endgame
The SEC's 'common enterprise' doctrine is the legal framework that classifies most token distributions as securities.
The Howey Test's Core Prong determines if an investment contract exists. The common enterprise prong is satisfied when investor fortunes are interwoven and dependent on a promoter's efforts. Token projects like Solana (SOL) and Filecoin (FIL) faced this exact scrutiny in their early days.
Code is Not a Shield. The SEC argues that decentralized governance and automated smart contracts on networks like Uniswap or Compound do not negate the initial common enterprise formed during the fundraising ICO/IDO. The initial development team's managerial efforts create the dependency.
The Counter-Argument Falters. Defenses citing sufficient decentralization (e.g., Bitcoin, Ethereum) are exceptions, not the rule. For a new L1 like Aptos or Sui, the core development team's ongoing, essential role in protocol upgrades and ecosystem growth directly maps to Howey's 'efforts of others' requirement.
Evidence: The Ripple Ruling. The July 2023 summary judgment found XRP sales to institutional investors constituted a securities offering under Howey, hinging on Ripple's promotional efforts creating a common enterprise. This sets a direct precedent for venture capital token purchases and early ecosystem grants.
TL;DR for Protocol Architects
The SEC's 'common enterprise' argument is its most potent legal weapon, capable of classifying most token projects as unregistered securities.
The Problem: Horizontal Commonality
The SEC argues your protocol's token is a security because investor profits are pooled and interdependent. This is triggered by:
- Protocol-controlled treasury funding development.
- Staking rewards derived from a shared revenue pool.
- Token buybacks/burns that directly link individual token value to collective success.
The Solution: Functional Decentralization
The only viable defense is to architect for genuine lack of managerial effort. This requires:
- Immutable, complete core protocol with no essential upgrades.
- Fully on-chain, permissionless governance where token votes are advisory, not managerial.
- Revenue distribution via public goods funding or burn, not as a passive return to holders.
The Trap: Promotional Ecosystem Funds
Creating a foundation or grant treasury controlled by insiders to bootstrap development is a legal landmine. The SEC views this as the quintessential 'common enterprise'.
- Examples: Solana Foundation, Algorand Foundation.
- Mitigation: Use a retroactive public goods funding model (e.g., Optimism's RPGF) post-launch, not a pre-launch promise.
The Nuance: Airdrops vs. Sales
Free distribution does not guarantee safety. The SEC examines the economic reality and promotional context.
- Safe(r): Airdrop to past users with no expectation of profit and no concurrent fundraising.
- Risky: 'Airdrop' to ICO participants or VC backers, which is a de facto sale.
- Reference: The SEC's case against Terraform Labs treated the airdrop as part of the unregistered offering.
The Architecture: Minimize Managerial Promises
Design token utility around consumptive use, not investment. Architect systems where the team's ongoing work is non-essential.
- Utility-First: Token is required for gas, governance (on non-essential parameters), or as a credential.
- Avoid: Roadmaps promising specific features, profitability, or exchange listings that create profit expectation.
- See: The legal distinction made between Filecoin's storage utility vs. a pure staking token.
The Precedent: Hinman's 'Sufficient Decentralization'
While not law, the 2018 speech outlines the SEC's pragmatic threshold. A network is likely not a security when:
- No central party has essential informational or managerial influence.
- Token transfers are independent of the promoter's efforts.
- The network is functional for its intended use. This is the de facto blueprint for protocols like Uniswap post-V3 launch.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.