No Investment of Money: Users deposit crypto assets for a specific utility service—validation—not a capital contribution. This is a fee-for-service transaction, akin to paying AWS for compute, not buying a share of Amazon.
Why Staking-As-A-Service Fails All Four Prongs of the Howey Test
A first-principles legal and technical breakdown arguing that the SEC's classification of pooled staking as a security is a fundamental misapplication of the Howey Test, ignoring the operational reality of decentralized networks.
Introduction
Staking-as-a-Service (SaaS) is structurally distinct from an investment contract, failing all four prongs of the Howey Test.
No Common Enterprise: SaaS providers like Figment or Coinbase Cloud operate isolated node infrastructure. User rewards derive from the protocol's inflation schedule, not the pooled efforts of the service or other users.
No Expectation of Profits: The primary yield is protocol-determined staking rewards, a function of network security, not managerial effort. Any profit expectation stems from the underlying asset's appreciation, a market variable.
No Managerial Efforts: The service provider's role is purely execution and infrastructure maintenance. They lack discretionary control over the core profit-generating asset—the blockchain protocol itself, like Ethereum or Solana.
Executive Summary
Staking-As-A-Service (SaaS) providers argue their products are non-securities, but their operational reality fails all four prongs of the Howey Test, exposing them to regulatory risk.
The Problem: Investment of Money
Users deposit capital expecting returns, satisfying the first Howey prong. SaaS platforms frame this as a "service fee" model, but the economic reality is a capital contribution to a common enterprise.
- User funds are pooled into validator nodes controlled by the service.
- The primary motivation is profit from staking rewards, not a utility service.
The Problem: Common Enterprise
SaaS providers operate a centralized pool of validators. User rewards are derived from the collective performance of this pool, not individual effort, creating a textbook common enterprise.
- Horizontal commonality: Profits are pooled and distributed pro-rata.
- Managerial control: The SaaS operator makes all technical and slashing-risk decisions.
The Problem: Expectation of Profit
Marketing is explicitly ROI-focused, anchoring user expectation in financial gain, not network participation. This is the most unambiguous failure of the Howey Test.
- APY dashboards are the primary interface, not governance or utility tools.
- Promotions highlight "earn yield" and "passive income," cementing the profit motive.
The Problem: Efforts of Others
Users are entirely passive. The SaaS provider's team performs all managerial and technical work—node operation, software upgrades, slashing risk mitigation—making profits solely reliant on others' efforts.
- Zero technical requirement for the end-user.
- Full delegation of all operational and financial risk management.
The Core Argument: A Misapplied Framework
Applying the Howey Test to Staking-As-A-Service misinterprets the fundamental nature of decentralized infrastructure.
The Howey Test is misapplied because it assumes a common enterprise, but non-custodial staking services like Lido and Rocket Pool are permissionless protocols, not centralized ventures. The user retains full control of their validator keys, eliminating the managerial effort required by the test's third prong.
The expectation of profit is misattributed. The yield from Proof-of-Stake consensus is a network security subsidy, not a return from the service provider's efforts. The service merely provides the technical means to access this native protocol reward, similar to how Coinbase Wallet provides access to DeFi yields it does not generate.
The investment of money is a red herring. Users stake existing assets (e.g., ETH) to perform a network utility function. This is a capital commitment for operational security, distinct from purchasing a security where capital is pooled for a venture's success.
Evidence: The SEC's own actions against Kraken and Coinbase targeted their custodial staking programs, explicitly distinguishing them from non-custodial protocols. This legal distinction validates the technical argument that key custody defines the enterprise.
The Battlefield: SEC Actions and Market Reality
Staking-as-a-Service (SaaS) structurally fails the Howey Test, rendering the SEC's enforcement posture a legal overreach against a passive infrastructure layer.
Investment of Money is Passive: SaaS users deposit tokens, but the capital is not pooled into a common enterprise. The user retains full ownership of their specific validator keys, unlike a pooled fund like Grayscale's GBTC.
No Common Enterprise Exists: The validator's performance is siloed. A failure at Coinbase or Figment does not affect a user's specific staked ETH, negating the horizontal commonality central to Howey.
Expectation of Profit is Disconnected: Rewards derive from the protocol's consensus mechanism, not the managerial efforts of the service provider. The provider's role is purely operational, akin to AWS hosting a website.
Evidence: The SEC's own case against Ripple established that programmatic sales on secondary exchanges lack a common enterprise. Applying this logic, user-directed staking is a bilateral service contract, not an investment contract.
Howey Test Prong Analysis: SEC Claim vs. On-Chain Reality
Deconstructing the SEC's security classification of Staking-as-a-Service by evaluating its claims against the verifiable mechanics of protocols like Lido, Rocket Pool, and EigenLayer.
| Howey Test Prong | SEC Legal Claim | On-Chain Protocol Reality | Prong Fails? |
|---|---|---|---|
| User's staked ETH is a capital contribution. | User retains full, non-custodial control via liquid staking tokens (LSTs) like stETH or rETH. No transfer of funds to a common enterprise. | |
| Provider pools user assets into a single validator set, creating horizontal commonality. | Assets are technically pooled, but user's economic return is algorithmically derived from their specific staked amount and the performance of randomly assigned validators (e.g., Lido's oracle reports, Rocket Pool's minipool model). No profit-sharing from the enterprise itself. | |
| Users stake solely to earn rewards from the provider's efforts. | Rewards are a function of Ethereum's consensus protocol (4.1% APR). The service provider's effort (node operation) is a commoditized infrastructure service, not an entrepreneurial or managerial effort determining profit. User profit expectation is from the underlying protocol, not the service. | |
| Profits come solely from the managerial efforts of the service operator. | Post-deposit, rewards are generated by Ethereum's decentralized proof-of-stake mechanism. Node operator failure slashes the operator's stake, not the user's principal (protected by overcollateralization, e.g., Rocket Pool's 150% minipool collateral). User effort is required to delegate/undelegate. | |
Legal Precedent Anchor | Relies on 1946 Supreme Court case (orange groves) & 2023 Kraken settlement. | Controlled by smart contract code, decentralized oracle networks (Chainlink), and autonomous on-chain governance (e.g., Lido DAO). | |
User's On-Chain Exit Ramp | Claimed to be locked and dependent on provider. | Immediate via decentralized AMMs (Curve, Uniswap) for LSTs. Direct withdrawal queues are protocol-native (Ethereum's withdrawal credentials, EigenLayer's withdrawal delay). | |
Key On-Chain Entities | Single, centralized 'issuer'. | Decentralized Validator Networks, DAOs (Lido, Rocket Pool DAO), Oracle Networks, Liquid Staking Tokens (stETH, rETH, ezETH). |
Technical Dissection: Why 'Common Enterprise' and 'Efforts of Others' Fail
A technical breakdown of why staking-as-a-service structurally fails the two most critical prongs of the Howey Test.
The 'Common Enterprise' prong fails because the staking pool's success is not inherently tied to the validator's efforts. The protocol's native yield is a function of network consensus rules, not managerial skill. Unlike a traditional enterprise, the pool's performance is dictated by the Ethereum Beacon Chain or Solana's inflationary schedule, not coordinated business activity.
The 'Efforts of Others' prong fails because the delegator's role is not passive. The delegator actively selects the operator based on slashing history, commission rates, and infrastructure reliability. This is a discrete service contract, akin to using AWS for compute, not an investment in a promoter's managerial efforts. The operator's work is execution, not profit-generation.
Counter-intuitive evidence: The most successful operators, like Coinbase or Figment, market their technical reliability, not their profit-maximizing acumen. Their service-level agreements (SLAs) guarantee uptime, not returns. This frames the relationship as infrastructure-as-a-service, not a security. The SEC's own actions against Kraken centered on undisclosed risks, not the fundamental structure of delegation.
Steelman: The SEC's Best Case and Its Fatal Flaw
A technical deconstruction of why staking-as-a-service fails the Howey Test's definition of an investment contract.
The SEC's best case relies on a reductive analogy: a user's deposit into a service like Coinbase Staking is an investment of money in a common enterprise with profits from the efforts of others. This framing deliberately ignores the user's underlying property rights and the service's mechanical, non-discretionary function.
Fails the 'Common Enterprise' prong. The user's staked ETH is a discrete asset, not pooled into a fungible security like a stock. The validator's performance is tied to its own infrastructure, not a shared business venture. This is a critical distinction from pooled investment vehicles.
Fails the 'Profits from Others' Effort' prong. The service provider's role is execution, not management. Providers like Lido or Rocket Pool run software clients; they do not make discretionary business decisions that generate profit. The yield is a protocol-native reward for securing the network, not a dividend from corporate success.
Evidence: The Ethereum protocol's reward schedule is deterministic and public. A user delegating to a Figment or Allnodes validator receives rewards based on a transparent, algorithmic schedule, not the provider's managerial skill. The service is a utility, not an investment.
Case Study: How Leading Protocols Invalidate the Howey Test
Modern staking protocols structurally invalidate the Howey Test's four prongs by eliminating common enterprise, profit expectation, and reliance on managerial efforts.
The Problem: Centralized Staking Pools as De Facto Securities
Traditional staking services like Lido or Coinbase act as centralized intermediaries, creating a common enterprise where users pool funds and rely on managerial efforts for profit. This structure directly triggers Howey analysis.
- Centralized Operator: A single entity controls validator selection and slashing risk.
- Pooled Capital: User funds are commingled into a shared liquidity pool.
- Passive Income Expectation: Returns are marketed as an investment contract.
The Solution: Non-Custodial, Permissionless Validator Sets
Protocols like Rocket Pool and EigenLayer dissolve the common enterprise by allowing any user to run a node or delegate to a permissionless set of operators. Profit stems from protocol-enforced cryptoeconomics, not a promoter's efforts.
- No Central Promoter: The protocol's smart contracts, not a company, manage slashing and rewards.
- User-Controlled Capital: Stakers retain custody and select their operator from an open market.
- Effort From User/Protocol: Returns are a function of individual operator performance and cryptographic guarantees.
The Problem: Profit Solely from Others' Efforts
The Howey Test's third prong fails if profit is derived solely from the efforts of others. In legacy staking-as-a-service, the user delegates all technical execution, creating a clear reliance on the promoter's managerial skill.
- Full Technical Delegation: User provides capital but zero operational input.
- Active Management Required: The service must actively maintain validator uptime, handle key rotation, and avoid slashing.
- Direct Correlation: User rewards are a direct function of the service's operational competence.
The Solution: Staking Derivatives as Commodity Futures
Liquid staking tokens (LSTs) like stETH or rETH are not securities because they represent a claim on a future commodity (ether) plus yield, similar to a futures contract. The value accrual is automated and non-discretionary.
- Commodity-Backed: Each LST is a claim on a fungible underlying asset (ETH).
- Automated Yield: Rewards are programmatically distributed via rebasing or vault mechanics, requiring no managerial discretion.
- Secondary Market: LSTs trade on DEXs like Uniswap, with price discovery detached from any promoter.
The Problem: Investment of Money with Expectation of Profit
Howey's first prong examines an 'investment of money'. If staking is framed purely as a financial return play, it leans into security territory. Centralized services emphasize APY marketing, framing staking as a passive income product.
- Capital-At-Risk: User funds are locked with the primary goal of generating a return.
- Profit-Centric Marketing: Messaging focuses on comparative APYs, not network security.
- Contractual Promise: Implied or explicit promises of returns based on the service's performance.
The Solution: Staking as a Utility for Network Security
Protocols like Cosmos and Solana reframe staking as a utility service—paying for the right to participate in consensus and governance. The 'profit' is a byproduct of securing the network, akin to earning fees for providing a public good.
- Service-For-Payment: Staking is a quid pro quo for validating transactions and blocks.
- Governance Rights: Stakers earn voting power, aligning rewards with active participation.
- No Profit Guarantee: Rewards fluctuate with network usage and slashing risk, negating a fixed expectation.
FAQ: Staking, Securities, and Regulatory Overreach
Common questions about why Staking-As-A-Service (STaaS) fails the Howey Test, a key legal framework for determining what constitutes a security.
The Howey Test is a Supreme Court framework to determine if an arrangement is an 'investment contract' and thus a security. It has four prongs: (1) an investment of money, (2) in a common enterprise, (3) with an expectation of profits, (4) derived solely from the efforts of others. The SEC uses it to argue that many crypto offerings, including some staking services, are unregistered securities.
What's Next: Legal Precedent vs. Technological Reality
The Howey Test's 70-year-old framework is structurally incompatible with modern, non-custodial staking infrastructure.
No Investment of Money: Capital deposited into a non-custodial liquid staking protocol like Lido or Rocket Pool is not an 'investment' in a common enterprise. The user retains ownership and control of the staked asset via a smart contract, a distinction the SEC's case against Coinbase failed to properly litigate.
No Common Enterprise: Staking-as-a-Service providers like Figment or Blockdaemon operate as infrastructure, not a horizontal common enterprise. Profits are not pooled; validator rewards are algorithmically generated by the underlying consensus layer (e.g., Ethereum, Solana), not the service's managerial efforts.
No Expectation of Profits: The primary expectation is for network security provision, not speculative profit. Rewards are payment for a verifiable service, analogous to AWS credits for providing compute. This is a fundamental technological reality the Howey Test ignores.
Evidence: The SEC's own case against Ripple established that programmatic sales on secondary exchanges lack a common enterprise. This precedent directly undermines the argument against non-custodial staking, where user assets never enter a promoter's treasury.
Key Takeaways for Builders and Investors
The Howey Test's four prongs systematically dismantle the legal fiction of Staking-As-A-Service. Here's why it's a flawed product-market fit.
The Investment of Money Prong: The Capital is Already at Risk
Users deposit ETH or other tokens, constituting a clear capital investment. The service provider's role is purely managerial, failing to create a novel asset. The legal risk is front-loaded for the user.
- User's capital is locked and subject to slashing
- Provider's fee is a management charge on a pre-existing asset
- No new 'common enterprise' is created; the asset (ETH) existed prior
Common Enterprise Prong: Horizontal vs. Vertical Commonality
Courts look for 'horizontal commonality' (pooled investor funds) or 'vertical commonality' (investor fortunes tied to promoter success). Most SaaS models exhibit vertical commonality.
- User rewards are tied to the provider's uptime and infrastructure, not a pooled fund
- This creates a direct dependency, satisfying the 'common enterprise' criteria
- Provider profit is a direct function of user deposits
Expectation of Profits Prong: The Marketing is the Evidence
SaaS platforms explicitly market based on yield and returns, not utility or governance. This directly triggers the 'expectation of profits' prong. Promotional language is self-incriminating.
- APY comparisons and yield calculators dominate marketing
- Profits are derived from the managerial efforts of the provider
- Contrast with true utility services like AWS or Infura
Managerial Efforts of Others Prong: The Core Service is Management
The entire value proposition is outsourcing node operation, key management, and slashing risk. Users are passive; the provider's efforts are solely responsible for generating rewards.
- User delegates all technical execution and security responsibilities
- Provider's software, monitoring, and upgrades are the sole source of 'profit'
- This is the definition of relying on 'managerial efforts of others'
The Builder's Alternative: Non-Custodial, Permissionless Tooling
The viable path is building infrastructure that enables self-custody. Think DVT (Distributed Validator Technology) like Obol and SSV Network, or solo-staking toolkits like Rocket Pool. These are software, not securities.
- Tools enable user sovereignty; they don't manage assets
- Shift from 'we stake for you' to 'here's how you stake safely'
- Product is a license, not an investment contract
The Investor's Lens: Value Accrual in Compliant Layers
Capital should flow to protocol-layer infrastructure and middleware, not regulatory-liability-as-a-service. The real value is in secure, decentralized coordination software.
- Invest in the picks and shovels (DVT, MEV tooling, RPCs), not the gold miners
- Protocol fees from decentralized networks are more defensible than management fees
- Assess legal liability as a core risk factor in any staking-related investment
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.