Pass-through tokens are not legal shields. The model, where a protocol issues a claim token (like stETH) representing an underlying asset, creates a direct legal obligation. Regulators like the SEC view this as creating an investment contract, as seen in the LBRY and Ripple cases. The legal liability does not 'pass through'—it originates with the issuer.
Why 'Pass-Through' Economics Don't Pass Legal Muster
A technical and legal breakdown of why the 'we just pass through rewards' defense is a losing argument against the SEC. The service itself, through pooling and delegation, creates the essential profit opportunity that defines an investment contract.
The Flawed Legal Shield
Protocols using 'pass-through' token models for legal insulation are building on a foundation of sand, not law.
The 'sufficient decentralization' defense is a myth. Projects like Uniswap and MakerDAO operate under constant regulatory scrutiny, not blanket immunity. The SEC's action against decentralized exchange DEBT Box demonstrates that a protocol's technical architecture does not preclude enforcement if founders maintain control or promote the asset.
Real-world enforcement targets the point of value accrual. The SEC's case against Coinbase for its staking service proves regulators target the centralized entity facilitating the yield. A protocol's native token, especially if used for governance or fee capture, is the primary target, not a secondary technical abstraction.
Evidence: The Howey Test is applied to utility. Courts assess whether a purchaser expects profits from the efforts of others. Protocols like Helium (HNT) and Filecoin (FIL), which tie token rewards to network growth driven by a core team, fail this test. Pass-through mechanics do not alter this fundamental economic reality.
Executive Summary: The CTO's Legal Reality Check
The naive model of passing native token rewards directly to users is a legal minefield that threatens protocol sustainability.
The Problem: The Howey Test's Broad Net
The SEC's framework for an 'investment contract' is a three-pronged trap for token distributions.\n- Money Invested: User stakes capital (e.g., ETH, stablecoins).\n- Common Enterprise: Protocol's success is tied to collective effort.\n- Expectation of Profit from Others: Pass-through rewards are pure yield, creating a clear profit motive derived from the work of developers and other users.
The Solution: Work-Based Reward Models
Shift from passive yield to active contribution. Legally defensible rewards must be compensation for verifiable work, not a financial return.\n- Fee-for-Service: Pay users for providing a resource (e.g., bandwidth for Akash, storage for Filecoin).\n- Bounties & Grants: Discrete payments for completing specific tasks or building integrations.\n- Loyalty/Utility Points: Non-financial incentives that accrue value through protocol utility, not a promise of future profit.
The Precedent: Uniswap vs. LBR Airdrops
Contrast the regulatory outcomes of two major airdrop models.\n- Uniswap (UNI): Distributed as a 'governance token' for past usage. No ongoing yield mechanism. Result: No SEC action to date.\n- LBR (Lybra Finance): Promised and delivered ongoing staking APY in its native token. Result: Deemed a security, forced to shut down US operations and buy back tokens. The key differentiator was the explicit promise of future yield.
The Fallacy: 'Decentralization' as a Shield
CTOs often assume sufficient decentralization immunizes a token. This is a dangerous miscalculation.\n- Legal Threshold is High: The SEC's view of decentralization is far stricter than the crypto community's. Ethereum only escaped after its transition to Proof-of-Stake, which the SEC reluctantly accepted.\n- Control is Key: If a core development team or foundation controls >20% of supply or can materially influence development, the 'common enterprise' prong is likely satisfied. Pass-through economics centralizes the profit expectation on that team.
The Operational Risk: Tax & Accounting Nightmare
Beyond securities law, pass-through models create intractable operational burdens.\n- Taxable Event Per Epoch: Each micro-reward is a new income event for the user, creating a logistical nightmare for reporting.\n- Protocol Liability: If classified as a security, the protocol may be liable for withholding taxes on global users.\n- Balance Sheet Poison: Native tokens paid as expenses must be marked-to-market, creating massive earnings volatility for the issuing entity.
The Strategic Pivot: Value Accrual to Non-Equity Assets
The endgame is building sustainable value without creating a security. Learn from successful models.\n- Protocol-Owned Liquidity (POL): Fees accrue to a treasury-controlled pool (e.g., Olympus DAO model), funding development without user-facing yield.\n- Burn Mechanisms: Use protocol revenue to buy and burn a non-security asset (e.g., EIP-1559 burning ETH). This increases scarcity for all holders without a profit promise.\n- Fee Switches for Governance: Allow token holders to vote to activate a fee on protocol usage, with proceeds directed to POL or burns—this ties value to utility, not passive yield.
The Core Argument: The Service *Is* the Enterprise
Protocols that rely on pass-through economics are structurally identical to traditional service businesses in the eyes of regulators.
Pass-through economics are a legal fiction. Protocols like Helium and early Filecoin models attempted to create passive income by merely passing token rewards to hardware operators. Regulators see this as a centralized service wrapper paying contractors, not a decentralized protocol generating organic yield.
The enterprise is the service layer. If a core team controls the oracle updates, parameter governance, or treasury allocations, they are the service provider. This is the SEC's Howey Test applied to web3 infrastructure: profit must come solely from the efforts of others, which includes the founding entity's ongoing development.
Contrast with credibly neutral protocols. Ethereum's consensus rewards derive from a fixed, algorithmic issuance schedule, not a team's discretion. Uniswap's fees accrue to LPs based on immutable code. The absence of a centralized profit conduit is the critical legal distinction that pass-through models lack.
Evidence: The SEC's enforcement actions. The case against LBRY established that even utility tokens sold to fund development constitute an investment contract. For infrastructure protocols, this precedent means token sales to bootstrap node operators are a high-risk activity unless the network achieves full algorithmic autonomy at launch.
SEC Enforcement Matrix: The 'Pass-Through' Defense on Trial
Comparative analysis of key legal arguments and outcomes in SEC enforcement actions against token projects claiming 'pass-through' economics.
| Legal Factor | SEC Position (Howey Test) | Defense Argument (Pass-Through) | Court Ruling Trend |
|---|---|---|---|
Investment of Money | Token purchase = capital contribution | Payment for utility/software license | Consistently favors SEC |
Common Enterprise | Network success drives token value | Value derived from user activity, not promoter effort | Favors SEC (e.g., Telegram, LBRY) |
Reasonable Expectation of Profits | Marketing emphasized price appreciation | Profits are incidental to utility | Favors SEC if any profit motive present |
Efforts of Others | Development team controls protocol upgrades | Decentralization or 'sufficiently decentralized' state | Initial sales almost always fail this prong |
Token Distribution Model |
| Fair launch, airdrops, community treasury | Mixed; airdrops may avoid security label (e.g., Tornado Cash) |
Post-Sale Promotional Activity | Active marketing, exchange listings | Passive, community-driven ecosystem | Critical factor; ongoing promotion = security |
Key Precedent Case | SEC v. W.J. Howey Co. (1946) | SEC v. Ripple (2023) - Programmatic Sales | Ripple ruling created limited safe harbor for secondary sales |
Deconstructing the Howey Test for Staking Pools
Pass-through staking models fail the Howey Test because they create a common enterprise with an expectation of profit from others' efforts.
A common enterprise exists when user funds are pooled and the pool's success depends on the operator's managerial efforts. This is the foundational element of an investment contract under the Howey Test.
Profit expectation from others is explicit in pass-through models like Lido's stETH or Rocket Pool's rETH. Token holders expect yield from the protocol's node operators, not their own direct work.
The 'efforts of others' is the operator's technical infrastructure. The SEC's case against Kraken's staking service established that managing validator nodes constitutes this critical managerial effort.
Counter-intuitive insight: A truly decentralized pool like a solo-staker collective might pass, but centralized entities like Coinbase or Binance offering staking-as-a-service are high-risk targets for enforcement.
Case Studies in Failed Defenses
Protocols that attempt to outsource legal risk to token holders or third parties have repeatedly failed in court, creating a dangerous playbook for regulators.
The SEC vs. LBRY: The 'No-Function Utility' Trap
LBRY argued its LBC token was a utility for accessing a decentralized file-sharing network. The court ruled it was a security because its primary use was speculative investment, not platform access. The 'pass-through' of governance rights did not negate the investment contract.
- Key Precedent: Utility must be the primary use case at launch, not a theoretical future feature.
- Failed Defense: Tokenomics designed to incentivize holding (e.g., staking rewards) were cited as evidence of investment expectation.
The Terraform Labs Ruling: Algorithmic 'Decentralization' is Irrelevant
Terra argued UST and LUNA were decentralized algorithmic stablecoins, not securities. The court dismissed this, focusing on Terraform Labs' central managerial efforts to promote the ecosystem and maintain the peg. The 'pass-through' of protocol fees to stakers was seen as a profit-sharing mechanism.
- Key Precedent: Developer marketing and active ecosystem management can establish a 'common enterprise,' even for algorithmic systems.
- Failed Defense: Claims of technical decentralization did not offset the central promotional role of the founding entity.
Uniswap's Wells Notice: The 'Pure Protocol' Litmus Test
Despite Uniswap Labs' careful separation from the UNI token and protocol, the SEC's Wells Notice signals scrutiny of the entire economic stack. The 'pass-through' of fee switches to token holders is a direct profit-sharing mechanism that regulators view as a security hallmark, regardless of technical decentralization.
- Key Precedent: Even a legally separated foundation and a fully deployed protocol can be targeted based on tokenholder economics.
- Active Risk: The $1.7B+ UNI treasury and proposed fee mechanism create a clear link between token ownership and expected profits from the enterprise.
Steelman: The Builder's Perspective (And Why It's Wrong)
The 'pass-through' token model is a legal fiction that fails under regulatory scrutiny.
Pass-through is a legal fiction. Builders argue a protocol's token is a 'pass-through' for underlying assets, like a Uniswap LP token. This framing attempts to sidestep securities law by claiming the token is a pure utility.
The SEC rejects this analogy. The Howey Test examines economic reality, not technical structure. A token's value derived from a common enterprise's profits is a security, regardless of its on-chain utility wrapper.
Precedent exists with staking-as-a-service. The SEC's actions against Kraken and Coinbase establish that bundling a service with a tokenized yield constitutes an investment contract. Pass-through models are a direct parallel.
Evidence: The Hinman Speech is dead. The 'sufficient decentralization' safe harbor builders cite was an unofficial speech, not law. The SEC's enforcement against Ripple, Terraform Labs, and others proves functional utility is irrelevant to the security determination.
FAQ: Navigating the Legal Minefield
Common questions about why 'Pass-Through' Economics Don't Pass Legal Muster.
'Pass-through' economics is a flawed legal structure where a protocol's token is misrepresented as a direct claim on underlying revenue or assets. It attempts to mimic traditional securities by promising token holders a share of fees generated by protocols like Uniswap or Aave, but without the legal standing of an equity share.
TL;DR: Actionable Takeaways for Builders
The SEC's Howey test doesn't care about your clever tokenomics. Here's how to avoid building a security from day one.
The Problem: 'Value Accrual' is a Red Flag
Promising token price appreciation via protocol fees or buybacks is a direct path to a security classification. The SEC's core argument against projects like Uniswap (UNI) and SushiSwap (SUSHI) hinges on this expectation of profit.
- Key Risk: Linking token value to revenue creates an 'investment contract' under Howey.
- Builder Action: Decouple token utility from direct fee distribution. Use it for governance or access, not as a profit-sharing coupon.
The Solution: The 'Pure Utility' Model
Emulate Filecoin (storage) or Ethereum (gas). The token's primary, non-speculative function must be undeniable.
- Key Benefit: Creates a defensible 'consumptive use' argument, weakening the 'investment' premise.
- Builder Action: Design the token as a required input for a core, non-financial service. Its value should stem from operational demand, not investor speculation.
The Problem: Centralized Promotion = Centralized Liability
Founder and VC hype trains marketing token price potential are exhibit A for the SEC. This satisfies the 'efforts of others' prong of Howey.
- Key Risk: Public statements by the team can implicate the entire project, as seen with Ripple (XRP).
- Builder Action: Enforce strict communication policies. Focus messaging on technology and utility, never on investment returns or price.
The Solution: Decentralization as a Shield
A sufficiently decentralized network, where no single entity controls development or promotion, can exit security status. This is the Ethereum precedent.
- Key Benefit: Transforms the asset from an investment contract into a commodity-like resource.
- Builder Action: Architect for credible neutrality from day one. Cede protocol upgrades to on-chain governance and foster independent developer ecosystems.
The Problem: Airdrops as Unregistered Offerings
Free tokens aren't free from scrutiny. The SEC views retroactive airdrops to early users as a form of investment solicitation, rewarding past contributions to the network.
- Key Risk: Creates an implied promise of future value for ecosystem support, as argued in cases against Coinbase and others.
- Builder Action: If you airdrop, avoid tying it directly to prior financial contribution or specific, rewardable actions. Frame it as a pure user acquisition tool for a functional network.
The Solution: Build for Function, Not Finance
Stop optimizing for 'tokenomics' and start building a machine that needs a token to run. This is the first-principles shift.
- Key Benefit: Aligns incentives with long-term protocol health and legal durability, not short-term speculation.
- Builder Action: Ask: 'Does this feature make the protocol more useful, or just the token more valuable?' Kill any feature that only serves the latter.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.