Layer 1 tokens are securities. The Howey Test's 'common enterprise' factor is satisfied when a token's value is tied to the core development team's efforts, a reality for chains like Solana and Avalanche where the foundation drives protocol upgrades and ecosystem growth.
Why the 'Common Enterprise' Factor Dooms Most Layer 1 Tokens
A technical analysis of why the SEC's 'common enterprise' prong is an existential legal threat to centralized Layer 1s, and how only protocols with credible, provable decentralization can survive.
Introduction
The 'common enterprise' legal doctrine renders most Layer 1 token models inherently flawed and legally vulnerable.
Decentralization is a legal shield. The SEC's cases against Ripple and Telegram establish that a sufficiently decentralized network, where no single party controls development, breaks the common enterprise. Ethereum's post-merge governance is the primary benchmark.
Token utility is not a defense. A token facilitating gas payments, like on Polygon, does not negate the security classification if investors profit from the foundational team's managerial work. The SEC's case against Coinbase highlights this distinction.
Evidence: The SEC's 2023 lawsuits explicitly named Solana (SOL), Cardano (ADA), and Polygon (MATIC) as unregistered securities, citing the foundational teams' ongoing essential managerial efforts as the core of the common enterprise.
The Core Argument
Most Layer 1 tokens are unregistered securities because their value is inextricably linked to the core development team's efforts, creating a 'Common Enterprise'.
The Howey Test's 'Common Enterprise' defines a security as an investment in a venture where profits derive from others' efforts. In a decentralized network, token value must be independent of a central promoter's work.
Protocols like Ethereum and Solana fail this test. The Ethereum Foundation and Solana Labs remain the de facto technical and promotional core. Their roadmaps and developer activity directly drive ETH and SOL price action.
Contrast with Bitcoin and Monero. Their development is credibly neutral and diffuse. No single entity's roadmap or marketing materially impacts the network's utility or the asset's value, creating a stronger non-security argument.
Evidence: The SEC's lawsuits. The regulator's actions against Coinbase and Binance explicitly name SOL, ADA, and MATIC as securities, citing the promotional and managerial roles of their founding entities as proof of a common enterprise.
The Legal On-Chain Reality
The SEC's 'common enterprise' framework is a legal sledgehammer poised to shatter the utility narrative of most Layer 1 tokens.
The Problem: Decentralization Theater
Most L1s are run by a centralized core team and foundation controlling >20% of tokens and dictating protocol upgrades. This creates a clear 'common enterprise' where token value is tied to managerial efforts, not user utility.
- Legal Precedent: SEC vs. LBRY, Telegram GRAM.
- Reality: Ethereum escaped only after The Merge's proof-of-work sunset; newer chains lack this historical ambiguity.
The Solution: Protocol-Controlled Value
Shift token value accrual from speculative team promises to automated, on-chain treasury mechanics. See Frax Finance (frax.finance) and its sfrxETH yield or Olympus DAO (olympusdao.finance) with protocol-owned liquidity.
- Mechanism: Revenue is programmatically used for buybacks, staking yield, or burning.
- Legal Shield: Value derives from code, not a promoter's roadmap, attacking the 'expectation of profit' prong.
The Problem: The Staking Yield Trap
Native staking rewards are a prima facie security under Howey. They represent an 'investment contract' where profit comes from the work of validators (a common enterprise). Solana (sol), Cardano (ada), and Avalanche (avax) are directly in the crosshairs.
- SEC Position: Explicitly stated in multiple enforcement actions.
- Metric: ~5-10% APY is a red flag, not a feature, for regulators.
The Solution: Pure Utility & Fee Tokens
Tokens must be consumptive assets, not investment vehicles. Ethereum's ETH post-Merge is the archetype: a gas token and staking deposit with yield from user-paid fees, not issuer promises. Arbitrum's ARB for governance or Filecoin's FIL for storage are stronger models.
- Key: No native, protocol-issued inflation reward.
- Defense: Value is a function of network usage, not promotion.
The Problem: Centralized Roadmap Dependency
If a token's future utility (e.g., scaling, new VMs) depends on a core team's execution, it's a security. This dooms most VC-backed L1s like Sui (sui) and Aptos (apt) whose ~3-5 year unlock schedules align investor profits with development milestones.
- Evidence: Foundation-controlled grant programs and ecosystem funds.
- Result: Token = a share in the foundation's business success.
The Solution: Credibly Neutral Infrastructure
The only durable path is Bitcoin and Ethereum's model: a finished core protocol governed by rough consensus. Layer 2s like Starknet (starkware.io) or zkSync (zksync.io), where the token is purely for staking/proving on a live network, present a narrower target.
- Blueprint: Launch feature-complete. Governance becomes a coordination tool, not a development vehicle.
- Outcome: The 'enterprise' is the open-source software, not an organization.
Layer 1 Legal Risk Matrix: Centralization vs. Defense
Evaluates how key Layer 1 architectural and governance traits influence the 'Common Enterprise' factor under the Howey Test, which is the primary legal threat to token classification.
| Critical Factor | High Risk (e.g., ETH Pre-Merge, SOL) | Medium Risk (e.g., Post-Merge ETH, AVAX) | Low Risk (e.g., BTC, Monero) |
|---|---|---|---|
Foundation/Team Token Allocation |
| 10-20% held by foundation/team | <5% or provably fair launch |
Protocol Upgrade Control | Single client dominance (>66%) or foundation multisig | Formalized, time-locked governance (e.g., 2-week delay) | User-activated soft forks; no central upgrade key |
Validator/Node Centralization | Top 10 entities control >50% of stake/hash | Top 10 entities control 30-50% of stake | Top 10 entities control <20% of hash/stake |
Treasury/Subsidy Control | Central entity funds core devs & grants | Decentralized, on-chain treasury with broad governance | No treasury; funding via voluntary donations (e.g., mempool fees) |
Explicit Profit Promise | Staking yields promoted as 'rewards' or 'dividends' | Yield framed as 'security incentive' or 'block reward' | No yield; pure PoW block reward or fee market only |
Development Centralization |
| Multiple competing core dev teams (e.g., >5 client teams) | Permissionless client development; no reference implementation |
Deconstructing the 'Managerial Efforts' Prong
The SEC's 'common enterprise' test requires active managerial efforts, which most L1 governance tokens fail to demonstrate.
Active managerial efforts are required. The Howey Test's 'common enterprise' prong demands a promoter's managerial efforts drive profits for token holders. Most L1 foundations lack the centralized, ongoing operational control the SEC expects.
Decentralized governance is insufficient. Delegated voting via Snapshot or Tally creates a governance facade, not managerial control. The core protocol development by Ethereum Foundation or Solana Foundation is legally distinct from token-holder profit generation.
The precedent is clear. The SEC's case against Ripple's XRP established that a decentralized network's utility does not negate an initial common enterprise. Tokens like ADA and ALGO face identical structural vulnerabilities despite their technical merits.
The Flawed Rebuttal: 'It's Just Code'
The 'common enterprise' legal framework renders the 'sufficient decentralization' defense for most L1 tokens a functional fiction.
The Howey Test's 'Common Enterprise' is the fatal flaw. A token's classification as a security hinges on investment in a common enterprise with an expectation of profits from others' efforts. Protocol governance tokens like Uniswap's UNI or Aave's AAVE directly fail this, as their value is explicitly tied to the development efforts of their core teams and grant-funded ecosystem projects.
'Sufficient Decentralization' is a moving target with no legal precedent. The SEC's cases against Ripple and Coinbase establish that promotional and developmental efforts by a core team create a common enterprise, regardless of the code's public availability. An L1 like Solana, despite its validator set, was marketed and developed by Solana Labs, creating a clear central promoter.
The 'Code is Law' defense ignores economic reality. Investors buy ETH, SOL, or AVAX expecting the core development teams (EF, Solana Labs, Ava Labs) to improve the protocol and drive adoption. This reliance on managerial efforts is the textbook definition of an investment contract, as seen in the SEC's ongoing case against Binance regarding BNB and BUSD.
Evidence: The SEC's enforcement trajectory is the proof. The agency did not sue the Ethereum Foundation after the Merge because it judged ETH's decentralization, but because of strategic priorities. Its lawsuits explicitly target tokens where a centralized development entity is identifiable, making 'it's just code' a narrative, not a legal shield.
Case Studies in Common Enterprise
Most Layer 1 tokens are unregistered securities because their value is derived from the managerial efforts of a centralized core team, not from a decentralized network.
The Solana Foundation as Central Manager
The SEC's case hinges on the Foundation's active, ongoing role in directing the network's development and marketing. The token's value is explicitly tied to this managerial effort, not just network usage.
- Key Control: Foundation controls ~$1.2B+ treasury, funds core devs, and runs validator incentive programs.
- Key Effort: Centralized roadmap execution (Firedancer, token extensions) drives speculative value.
- Key Risk: Token is an investment contract in a common enterprise managed by the Foundation.
Avalanche & The A-Team Dependency
Ava Labs' contractual obligations and dominant development role create a clear common enterprise. The SEC alleges AVAX value is premised on Ava Labs' technical and promotional work.
- Key Control: Ava Labs holds the core IP, employs the primary dev team, and orchestrates subnet deployments.
- Key Effort: Enterprise subnet strategy and partnerships (JPMorgan, Citi) are centrally brokered efforts.
- Key Risk: Network growth is not organic; it's a product of a specific company's business development.
The Algorand Foundation's Profit Promise
Explicit promises of future performance and ecosystem funding directly link ALGO's value to the Foundation's managerial success. This is a textbook common enterprise.
- Key Control: Foundation controls governance, doles out ~$300M+ in development grants, and manages staking rewards.
- Key Effort: Active "accelerator" programs and partnership announcements are central drivers of adoption narratives.
- Key Risk: Tokenomics are centrally adjusted (e.g., staking changes) to influence price, confirming investment contract nature.
Contrast: Ethereum's Post-Merge Decentralization
ETH survives scrutiny because the Ethereum Foundation's role has diminished post-Merge. Client diversity, consensus, and execution are now managed by disparate, independent teams.
- Key Decentralization: No single entity controls protocol development; multiple client teams (Prysm, Lighthouse, Geth, Nethermind) are independent.
- Key Effort: Value derives from global, permissionless use as gas and collateral, not a promoter's efforts.
- Key Precedent: The SEC's tacit acceptance sets a benchmark: true decentralization negates the "common enterprise" factor.
The "Protocol-As-A-Service" Trap
Newer L1s like Aptos and Sui are launched by for-profit entities (ex-Meta/Diem teams) that sell enterprise blockchain solutions. The token is the funding vehicle for this service business.
- Key Control: Founding entities own core technology, run initial validators, and sign enterprise deals.
- Key Effort: Token value is explicitly marketed alongside the parent company's technical services and partnership announcements.
- Key Risk: This is a quintessential common enterprise; investors profit from the company's business success, not a decentralized network effect.
The Regulatory Escape Hatch: True Utility Tokens
The only viable path is a token with immediate, non-speculative utility at launch, divorced from a promoter's efforts. Think Filecoin for storage or Helium for connectivity.
- Key Design: Token is a required work credential or unit of resource, not a passive investment. Value accrual is from utility consumption, not ecosystem fund performance.
- Key Effort: Network growth must be permissionless and organic; core devs can fade into the background.
- Key Example: A token that is purely gas for a VM, with no foundation treasury or promised roadmap, mirrors a commodity, not a security.
The Path Forward: Engineering Legal Defense
The 'Common Enterprise' legal doctrine renders most Layer 1 tokens as unregistered securities by design.
The Common Enterprise Test is the SEC's primary weapon. It asks if token value depends on the managerial efforts of a core team. For monolithic L1s like Solana or Avalanche, the answer is always yes. The foundation's development roadmap, grant programs, and core protocol upgrades are the sole drivers of network utility and token price.
Decentralization is a Legal Shield, not a marketing term. The Howey Test's common enterprise factor fails if no single entity controls the network's essential functions. This requires credible, irreversible exit of the founding team, a state no major L1 has achieved. Ethereum's transition to Proof-of-Stake, managed by the Ethereum Foundation, ironically strengthened this argument against it.
Modular Blockchains like Celestia structurally avoid this pitfall. By decoupling execution from consensus and data availability, they create a minimal viable coordination layer. The core protocol provides a pure public good (data ordering) with no ongoing 'managerial effort' required for application success, mirroring the legal defensibility of TCP/IP.
Evidence: The SEC's lawsuits against Coinbase and Binance explicitly allege Solana (SOL), Cardano (ADA), and Polygon (MATIC) are securities due to their respective foundations' promotional activities and development control. This establishes a clear enforcement pattern targeting foundation-driven L1s.
TL;DR for Builders and Investors
The 'Common Enterprise' legal test is the single greatest existential threat to most Layer 1 token models, turning protocol governance into a liability.
The Howey Test Trap
The SEC's primary weapon. A token is a security if it involves an investment of money in a common enterprise with an expectation of profits from the efforts of others. Decentralization is the only defense.
- Key Risk: Active foundation development or core team roadmaps create a 'common enterprise'.
- Key Metric: >90% of top 20 L1s likely fail this test under current SEC interpretation.
Protocol vs. Enterprise
The critical distinction for survival. A true protocol is neutral infrastructure; an enterprise is a managed project. Token value must derive from utility, not promotion.
- Solution: Minimize foundation control. Ethereum's post-merge evolution is the benchmark.
- Avoid: Centralized roadmaps, treasury-controlled grants with strings, marketing that promises appreciation.
The Fat Protocol Thesis is Dead
The old model of capturing all value at the L1 token layer is a regulatory bullseye. Future value accrual shifts to application-layer tokens and restaking derivatives.
- New Model: L1 as minimal, credibly neutral settlement. Value flows to EigenLayer, Lido, Aave.
- Implication: Investing in L1 tokens for 'ecosystem growth' is investing in a security. Invest in the apps built on top.
Build & Invest Checklist
Actionable steps to mitigate 'Common Enterprise' risk. This is a compliance roadmap, not just good practice.
- For Builders: Sunset foundation governance within 3-5 years. Token utility = gas, staking, governance only.
- For Investors: Demand legal memos on decentralization. Prefer tokens with >60% circulating supply and no 'ecosystem funds'.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.