The Howey Test Fails on the core premise of a common enterprise. Liquid staking protocols are non-custodial, automated smart contracts. The staker retains full control of their assets, delegating only validation rights. This breaks the vertical commonality required for an investment contract.
Why the SEC's Investment Contract Framework Fails for Liquid Staking
Applying the Howey Test to Liquid Staking Tokens (LSTs) is a category error. It ignores their primary function as network access instruments and misdiagnoses the actual systemic risks, like smart contract failure and validator centralization.
The Regulatory Blind Spot
The SEC's investment contract framework is structurally incapable of assessing liquid staking protocols like Lido and Rocket Pool.
Staking is a Service, not a security. Protocols like Lido and Rocket Pool provide a utility: pooled validation infrastructure. Users pay a fee for this service, receiving a yield derived from network consensus rewards, not from the managerial efforts of a central promoter.
The SEC conflates the derivative (stETH, rETH) with the underlying service. These tokens are receipt tokens representing a claim on a staked asset, similar to a warehouse receipt for a commodity. Regulating them as securities creates a category error that stifles infrastructure innovation.
Evidence: The SEC's case against Kraken's staking service settled on a central, custodial model. This precedent does not apply to decentralized, non-custodial protocols where the user, not the protocol, bears the slashing risk.
Executive Summary: The Three Fatal Flaws
The SEC's rigid application of the 1946 Howey test to modern liquid staking protocols reveals fundamental legal and technological incompatibilities.
The Problem: Misapplied Expectation of Profit
The SEC fixates on staking rewards as the sole 'profit' driver, ignoring the protocol's core utility. This mischaracterizes a network security service as a passive investment.
- Key Flaw: Ignores that ~90% of staked ETH is used as productive collateral in DeFi (e.g., Aave, MakerDAO).
- Reality: The primary 'profit' for most users is utility yield from leveraged DeFi strategies, not the base staking APR.
- Precedent: By this logic, cloud computing credits or AWS Reserved Instances would be securities.
The Problem: No Common Enterprise with a Central Promoter
Liquid staking protocols like Lido (via DAO governance) and Rocket Pool (decentralized node operators) are not centrally managed 'enterprises' in the Howey sense.
- Key Flaw: Token holders govern the protocol; profits are not derived from a promoter's efforts but from automated, permissionless smart contracts.
- Reality: The 'managerial efforts' are codified and immutable. Profits flow from the Ethereum protocol itself.
- Analogy: Classifying this as a common enterprise is like calling Uniswap v3 a security because LPs earn fees.
The Solution: The Functional Approach (Hinman Doctrine)
The correct framework is the 2018 Hinman Doctrine, which focuses on a token's consumptive use and decentralization. This aligns with first principles of blockchain utility.
- Key Shift: Evaluate if the asset is used primarily for its intended function (e.g., staking, governance, gas) versus pure speculation.
- Precedent: Applied correctly, it exempted ETH and BTC. Mature LSTs like stETH or rETH are clearly consumption assets for DeFi.
- Outcome: Provides a technology-neutral standard that protects investors without stifling protocol innovation.
Core Thesis: Utility Precludes Howey
The SEC's Howey test fails for liquid staking because the primary purpose is utility, not passive profit from a common enterprise.
Liquid staking tokens (LSTs) are not investment contracts. Their primary function is utility as a collateral asset within DeFi protocols like Aave and Compound, not passive income generation from a promoter's efforts.
The Howey test's common enterprise prong collapses. LST holders do not rely on a central promoter; value accrual is driven by decentralized network security and DeFi composability, not managerial efforts.
Passive income is a byproduct, not the essence. The SEC's focus on staking rewards ignores the active utility of LSTs in lending, trading on Curve/Uniswap, and serving as money legos.
Evidence: Over 70% of Lido's stETH is locked in DeFi protocols, not held for yield. This demonstrates dominant utility use over passive investment, invalidating the Howey framework's core premise.
Deconstructing the Howey Test for LSTs
The SEC's application of the Howey Test to liquid staking tokens fails to account for their non-financial utility and decentralized operational reality.
LSTs are not investment contracts because they lack a common enterprise. Holders of Lido's stETH or Rocket Pool's rETH do not pool funds expecting profits from a promoter's efforts. The staking yield is a protocol-native reward, not a return from a managerial entity.
The 'expectation of profit' is misapplied. The primary utility of an LST is programmatic DeFi composability, not passive appreciation. Users hold stETH to access lending on Aave or leverage on MakerDAO, treating it as a productive collateral asset, not a security.
Evidence: The SEC's case against Kraken's staking service targeted the centralized service, not the underlying LST tokens themselves. This distinction proves the asset's neutrality; the regulatory risk is in the custodial wrapper, not the token's inherent properties.
LSTs vs. Traditional Securities: A Functional Comparison
A functional deconstruction of Liquid Staking Tokens versus traditional securities, highlighting why applying the SEC's investment contract framework is a category error.
| Functional Feature | Liquid Staking Token (e.g., stETH, rETH) | Traditional Equity Security (e.g., Apple Stock) | Traditional Debt Security (e.g., Corporate Bond) |
|---|---|---|---|
Primary Value Source | Protocol-native staking rewards + MEV | Company profit & growth | Contractual coupon payments |
Holder's Legal Claim | None (governed by smart contract) | Residual claim on assets & earnings | Contractual claim to principal + interest |
Underlying Asset Control | Decentralized validator set (non-custodial) | Centralized corporate management | Issuer's balance sheet & covenants |
Capital Formation Purpose | Protocol security (Proof-of-Stake) | Corporate financing & operations | Corporate/Government financing |
Yield Generation Mechanism | Automated, permissionless validation | Discretionary dividends & buybacks | Pre-defined interest schedule |
Secondary Market Liquidity | On-chain DEXs (Uniswap, Curve) - 24/7 | Centralized exchanges (NYSE, Nasdaq) - Market hours | OTC & bond markets - Limited |
Regulatory Compliance Nexus | Smart contract code & decentralized governance | SEC filings (10-K, 10-Q), GAAP accounting | Trust indenture, SEC regulation |
Default/Dilution Risk | Validator slashing (capped at stake) | Bankruptcy, equity dilution | Default, credit downgrade |
Steelman: The SEC's Likely Rebuttal (And Why It's Wrong)
The SEC's Howey Test framework fundamentally mischaracterizes the economic reality of liquid staking tokens like Lido's stETH.
The SEC's Core Argument is that staking pool tokens constitute an investment contract. The agency claims users provide ETH with an expectation of profit derived from the managerial efforts of entities like Lido DAO or Rocket Pool.
The Managerial Efforts Fallacy is the SEC's weakest point. Protocol operations are automated by smart contracts, not discretionary management. The staking yield is a network-native reward, not a profit from a promoter's business acumen.
The Common Enterprise Requirement fails. Lido's stETH is a claim on a basket of validators, not a shared venture. The token's value is pegged to ETH plus accrued yield, similar to a money market fund share, not an equity security.
Evidence: The SEC's own actions reveal the flaw. It approved ETH futures ETFs, which are derivatives of an asset it now claims is part of an unregistered security. This regulatory arbitrage exposes the inconsistency of applying Howey to staking.
The Real Risks the SEC Ignores
The SEC's rigid investment contract analysis ignores the operational and systemic risks inherent in modern DeFi protocols, creating a dangerous regulatory blind spot.
The Systemic Risk of Centralized Operators
The SEC's focus on profit expectation ignores the primary risk: operator failure. A single entity controlling $30B+ in staked ETH (e.g., Lido, Coinbase) creates a systemic point of failure. The real security is in the protocol's slashing mechanisms and governance, not the token's price.
- Validator Centralization: Top 3 providers control >50% of staked ETH.
- Smart Contract Risk: Billions secured by immutable, audited code, not a promoter's efforts.
The Liquidity & Composability Black Box
Liquid staking tokens (LSTs) like stETH are not passive investments; they are productive financial primitives. The SEC framework cannot account for their utility as collateral, which dwarfs simple profit expectation. This utility creates complex, unexamined risks in lending markets like Aave and MakerDAO.
- DeFi Integration: stETH used as collateral in ~$10B of loans.
- Protocol Dependency: Failure cascades through Aave, Compound, Uniswap.
The Oracle Manipulation Attack Vector
The critical infrastructure risk is oracle failure, not token sales. LST prices are pegged via decentralized oracles (Chainlink). A manipulation causing de-pegging could trigger mass liquidations across DeFi, a risk wholly separate from the investment contract analysis.
- Attack Surface: Oracle networks securing $100B+ in value.
- Regulatory Gap: No SEC rule addresses oracle security or slashing penalties.
The Validator Client Diversity Crisis
Real risk resides in the validator set's technical health, governed by the DAO, not token holders. The SEC's framework ignores the catastrophic risk of a consensus-layer bug in a dominant client like Prysm, which could lead to correlated slashing of billions in stake.
- Client Concentration: >40% of validators ran vulnerable Prysm client in 2023.
- DAO Governance: Lido DAO votes on client allocation, not token traders.
The Withdrawal Queue as a Run Risk
LSTs derive value from a non-financial utility: bypassing Ethereum's native withdrawal queue. The SEC's profit-centric view misses the structural risk of a "bank run" if unstaking demand exceeds protocol liquidity, a scenario managed by protocol parameters, not corporate promises.
- Queue Length: Ethereum's exit queue can span weeks.
- Liquidity Pools: Protocols like Curve provide secondary market depth.
The MEV Redistribution Mechanism
LSTs like Rocket Pool's rETH are claims on a stream of MEV and staking rewards, redistributed by smart contracts. This is a utility akin to a dividend-reinvesting ETF, but the SEC ignores the technical risks in the MEV supply chain (builders, relays) that directly impact returns.
- Revenue Source: MEV contributes ~10-20% of validator rewards.
- Infrastructure Risk: Relays like Flashbots are critical, unregulated middleware.
The Path Forward: Regulatory Clarity or Chaos?
The SEC's investment contract framework is a legal anachronism that fails to capture the technical reality of decentralized liquid staking protocols like Lido and Rocket Pool.
The Howey Test Fails because liquid staking tokens (LSTs) like stETH or rETH are not securities. They are debt-like yield receipts for a performed service—validating the Ethereum network—not an investment in a common enterprise with an expectation of profits from others' efforts.
The SEC's flawed logic conflates protocol utility with financial speculation. A user's economic return is contractually fixed by the underlying consensus rewards, not managerial efforts. The staking pool's role is purely infrastructural, akin to a cloud provider, not an active manager.
Regulatory chaos ensues when the same asset is a commodity (ETH) but its staked derivative is a security. This creates an untenable bifurcation that stifles DeFi composability, breaking integrations with Aave, Uniswap, and Compound that rely on uniform asset treatment.
Evidence: The CFTC has consistently classified ETH as a commodity, creating direct conflict with the SEC's stance on staking. This jurisdictional arbitrage forces builders to choose regulators, not logic, determining if an LST is a security based solely on its marketing.
TL;DR: Key Takeaways for Builders
The SEC's Howey Test is a legal anachronism that misapplies to modern, non-custodial DeFi primitives like liquid staking.
The Problem: Misapplied 'Common Enterprise'
The SEC argues staking pools are a common enterprise. This ignores the decentralized, non-custodial reality of protocols like Lido and Rocket Pool.\n- No Managerial Effort: Node operators are permissionless and automated.\n- No Pooled Profits: Rewards are algorithmically distributed, not from a promoter's efforts.\n- User Sovereignty: stETH holders retain full control of assets, unlike a traditional security.
The Solution: Functional & Legal Disaggregation
Architect protocols where the staking derivative (e.g., stETH) is legally distinct from the underlying validation service.\n- Separate Entities: Isolate the liquid staking token issuer from the node operator set.\n- Non-Custodial Design: Use smart contracts like EigenLayer's restaking or SSV Network's DVT to eliminate central control.\n- Clear Utility: Frame the token as a utility token for DeFi composability, not an investment in the protocol's success.
The Precedent: Ethereum's Non-Security Status
The SEC's own 2018 framework and the Hinman speech deemed a sufficiently decentralized network not a security. This directly applies.\n- Decentralized Validation: Post-Merge, Ethereum relies on ~1M+ independent validators.\n- Staking as a Service: Liquid staking protocols are just interfaces to this base layer.\n- Regulatory Arbitrage: Build on Cosmos, Solana, or other chains with clearer staking narratives to pressure the SEC.
The Fallback: Fully On-Chain Legal Wrappers
If the SEC prevails, the next wave is autonomous, code-is-law staking pools with embedded legal compliance.\n- DAO-Governed Legal Trusts: See Kleros or Aragon for dispute resolution models.\n- On-Chain KYC/AML: Integrate privacy-preserving proofs via Polygon ID or zkPass.\n- Automated Tax Reporting: Build Subgraphs or APIs that output Form 1099-equivalents directly from chain data.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.