Staking, Airdrops, and the Gratuitous Distribution Doctrine

(oh my)

June 17, 2026

For nine years after the IRS published Notice 2014-21 treating Bitcoin as property, the federal regulatory posture on staking and airdrops was a collection of unanswered questions held together by enforcement risk. Was a staking reward a security under SEC v. W.J. Howey Co., 328 U.S. 293 (1946)? The SEC took that position in SEC v. Kraken, No. 3:23-cv-06003 (N.D. Cal.), and the consent order required Kraken to shut down its U.S. staking-as-a-service program. The SEC tried again in the Earn program allegations in SEC v. Coinbase, Inc., 2:24-cv-04734 (S.D.N.Y.). Was the receipt of a staking reward a taxable realization event? Rev. Rul. 2023-14, 2023-33 I.R.B. 484, said yes on dominion-and-control. Was an airdrop a security distribution? SEC v. LBRY, Inc., 639 F. Supp. 3d 211 (D.N.H. 2022), suggested the answer could be yes for programmatic protocol rewards. Was a liquid staking token its own security? In re Voyager Digital Holdings, Inc., 1:22-bk-10943 (Bankr. S.D.N.Y.), and the CFTC’s position in related proceedings hinted at yes. The Corporation Finance staff statements on protocol staking (May 29, 2025) and liquid staking (August 5, 2025) softened some of these positions on a staff-only basis, but the Commission had not spoken and the statutory law remained as it was in 1933. Adding a note because I have had a couple people be confused – CLARITY is still a draft, so this is all subject to change.

Two things changed in early 2026. The first is the joint SEC-CFTC interpretation effective March 23, 2026, Release Nos. 33-11412 and 34-105020, which the Commission issued (with CFTC concurring guidance) and which expressly supersedes the 2019 Framework and all prior staff statements on these topics. The release sets out a detailed framework for protocol mining, protocol staking (in four flavors), staking receipt tokens, wrapping, and airdrops. The second is CLARITY’s §4B(a)(5), which codifies a six-clause statutory taxonomy of “gratuitous distribution” and applies the §4B(b)(4) non-security presumption to each clause. Read together, the interpretation and the statute substantially eliminate the staking-and-airdrop enforcement risk that consumed industry attention from 2021 through 2025. The interpretation defines the analytical method; the statute codifies the bottom-line treatment. This post reads them together.

§4B(a)(5) of the Securities Act, added by §102 of CLARITY, replaces the enforcement-risk soup with a defined term and a six-clause taxonomy. The defined term is “gratuitous distribution,” and it sweeps far more broadly than the word “gratuitous” suggests. The taxonomy enumerates self-staking, self-custodial third-party staking, liquid staking, custodial and ancillary staking services, programmatic and automated distributions, and a technology-neutral residual. Each receives a non-security presumption under §4B(b)(4)(A). The cumulative effect is the most consequential statutory accommodation of staking and airdrop economics anywhere in U.S. law.

The Definition Does the Work

§4B(a)(5)(A) defines a gratuitous distribution as “a distribution of a network token, including a distribution effected by an agent or other service provider engaged solely in an administrative or ministerial capacity, in exchange for not more than a nominal value of cash, property, services, or other assets in a broad, equitable, and non-discretionary manner.” The substantive elements are four: distribution of a network token, optional agent involvement in a strictly administrative capacity, exchange for not more than nominal value, and broad-equitable-non-discretionary character.

The “not more than a nominal value” formulation is the principal limit on the otherwise expansive definition. A distribution made in exchange for substantial consideration is not gratuitous. An airdrop sized to a holder’s prior on-chain activity but with no payment required is. A staking reward delivered in exchange for staked capital and validator effort is, on a literal reading of “exchange for,” not in exchange for nothing, but the bill’s enumerated clauses confirm that staking falls within the term. The drafting is best read as: gratuitous means without significant out-of-pocket cash payment to the distributor. Staking is gratuitous because the staker provides validator effort to the protocol and receives rewards from the protocol, not from a counterparty who is selling them. The broad-equitable-non-discretionary requirement screens out targeted private placements dressed up as airdrops. A distribution made only to accredited investors who pay a tokenization fee is not gratuitous. A distribution made to everyone who held a particular NFT before a snapshot date is.

§4B(a)(5)(B) then enumerates six specific mechanisms that are gratuitous distributions, “without limitation.” The enumeration is not exhaustive; the technology-neutral residual in clause (vi) makes that explicit. But each enumerated mechanism receives statutory recognition, and reading the six side by side is the cleanest way to understand the doctrine.

The Six Clauses

Clause (i), self-staking, covers the distribution of a network token as a programmatic result of validating or staking activity for a consensus mechanism, where the owner of the staked token and the operator of the node, validator, or similar software are the same person. The paradigmatic example is the solo Ethereum validator running her own node on her own staked ETH. The reward she receives is statutorily a gratuitous distribution. So is the reward a solo Solana, Cosmos, or Polkadot validator receives. The clause is technology-agnostic on consensus mechanism; proof-of-stake, delegated proof-of-stake, proof-of-history, and any future consensus mechanism producing token rewards for validating activity are within its scope, provided the validator is the token owner.

Clause (ii), self-custodial staking with a third party, extends the same treatment to the case where the staked token owner and the node operator are different persons, but the operator does not maintain custody or control of the staked token. The paradigmatic example is the Lido validator running infrastructure on behalf of stakers who hold the staked tokens themselves through a smart-contract escrow. Rocket Pool’s minipool architecture is similar in structure: the node operator stakes its own ETH plus rETH-routed customer ETH, and operates the validator software without holding direct custody of the customer’s principal. The clause confirms that non-custodial delegated staking is gratuitous. The structural test is custody. If the operator does not control the staked token, the distribution remains gratuitous.

Clause (iii), liquid staking, addresses the LST architecture that has become the dominant form of staking in the Ethereum ecosystem. The clause covers “the distribution of network tokens, as the issuance, transfer, or redemption of liquid staking tokens representing a pro rata interest in staked network tokens, and their associated rewards, provided that such tokens are issued as administrative or ministerial receipts and not providing discretionary management authority.” The administrative-or-ministerial language is the operative limit. An LST that conveys a pro rata interest in the underlying staked tokens and accruing rewards, without conferring discretionary management authority on the issuer, is a gratuitous distribution. An LST that conveys a discretionary right (a yield-optimizing manager’s authority to redirect capital among validator sets in exchange for performance fees) is not, or at least not within clause (iii). Lido’s stETH, Rocket Pool’s rETH, ether.fi’s eETH, and Coinbase’s cbETH all sit within the safe side of the line as currently designed, with cbETH the closest to the edge because the validator selection is centralized but the holder rights are still pro rata receipt rights.

Clause (iv), custodial and ancillary staking services, is the SEC-rulemaking clause. It covers custodial or ancillary staking services enabling the owner of a network token to participate in validating or staking activity, where the services are “exclusively administrative or ministerial in nature.” §4B(a)(5)(B)(iv)(I). §4B(a)(5)(B)(iv)(II) directs the Commission to issue rules defining what custodial and ancillary staking services qualify as exclusively administrative or ministerial. This is the post-Kraken, post-Coinbase Earn clause. Custodial staking-as-a-service is gratuitous if it is administrative or ministerial, and the operational content of that test has substantially been resolved at the federal-securities-law level by the joint SEC-CFTC interpretation. Under Release No. 33-11412, a “custodial arrangement” in which a custodian stakes deposited digital commodities on behalf of a depositor does not involve essential managerial efforts under Howey if the custodian does not decide whether, when, or how much of the depositor’s digital commodity to stake; does not guarantee or otherwise set the amount of rewards; selects a third-party node operator (where applicable) as its only staking-process decision; and holds the deposited digital commodities in a manner that (1) does not use them for operational or general business purposes, (2) does not lend, pledge, or rehypothecate them for any reason, and (3) is designed not to subject them to claims by third parties. The depositor retains ownership of the deposited digital commodity throughout. The release also expressly identifies four ancillary services that do not constitute essential managerial efforts: slashing coverage, early unbonding, alternate rewards payment schedules and amounts (provided rewards are not fixed, guaranteed, or greater than protocol-set amounts), and aggregation of digital commodities to meet protocol minimums. The Commission’s eventual §4B(a)(5)(B)(iv)(II) rulemaking will have to honor the structure the joint release establishes; the remaining contested area is custodial arrangements that involve discretionary validator selection, pooled-customer-asset management, or other features beyond the release’s conditions.

Clause (v), programmatic and automated distributions, is the airdrop catch-all. The mechanism must be automated, programmatic, protocol-defined, or rules-based; achieved through the transparent functioning of the DLS; subject to five conditions. The conditions track the language elsewhere in the bill on decentralization and transparency. (I) Distributions must occur pursuant to public, transparent, rules-based parameters publicly available and accessible on a permissionless basis, without individualized or real-time negotiation with recipients. (II) Recipients receive tokens as a direct programmatic result of objective, verifiable network participation, consumption, or contribution, including consensus participation, data availability, bandwidth, governance, or use and interaction with the protocol or application. (III) The number of tokens received is proportionate to the verifiable service, usage, or contribution. (IV) Any expected utility or value of the tokens arises primarily from decentralized network participation and market forces, rather than the discretionary actions of any single person or affiliated group. (V) No person or group has unilateral authority to alter, restrict, or direct the issuance parameters or distribution mechanisms, and any modification occurs only through a DGS.

The five conditions read together describe the difference between a properly-structured retroactive airdrop and a sweetened insider distribution dressed up as a community reward. The Optimism retroactive airdrops to Ethereum bridge users, the Arbitrum airdrop to active arbitrum.io users, and the Uniswap airdrop to historical LPs all sit comfortably within clause (v) if the eligibility rules are objective and rules-based. A discretionary “community contributor” airdrop curated by the founding team’s judgment of who counts as a contributor is harder to fit. The (II) requirement of objective, verifiable network participation does not, on its face, permit the team to award tokens based on subjective merit. Point programs that resolve into token distributions face a similar analysis: if the point allocation is rules-based and the conversion to tokens is mechanical, clause (v) covers it. If the point allocation is discretionary, it is not.

Clause (vi), the technology-neutral catch-all, covers any distribution employing a mechanism, protocol, or technology not specifically described in clauses (i) through (v), without regard to whether the mechanism is in existence at the time of enactment, provided the distribution meets the §4B(a)(5)(A) general requirements. This is the future-proofing clause. Whatever the next generation of staking and reward mechanisms turn out to be, if they distribute network tokens in exchange for nominal or no value in a broad-equitable-non-discretionary manner, they get gratuitous-distribution treatment. The clause is structurally similar to other technology-neutral residual clauses in the bill and protects against the recurring problem of statutory definitions overtaken by technical innovation.

The §4B(b)(4) Non-security Presumption

§4B(b)(4)(A) provides that, notwithstanding §4B(b)(1), a gratuitous distribution by itself does not constitute an offer, sale, or distribution of a security under §2(a)(1) of the Securities Act, §3(a) of the Exchange Act, §2(a) of the Investment Company Act, §202(a) of the Advisers Act, §16 of SIPA, or any state-law equivalent that is not commodity-consistent. The presumption is rebuttable, but the burden of proof shifts. A plaintiff or enforcement agency contending that a gratuitous distribution is in fact a securities transaction must affirmatively prove it.

§4B(b)(4)(B) is the anti-fraud savings clause. The non-security presumption does not displace the anti-fraud, anti-manipulation, or false-reporting authorities of the SEC, the CFTC, or state regulators. A gratuitous distribution that is structured to defraud or manipulate is still actionable on those grounds. The non-security status applies to the registration-and-disclosure architecture of the federal securities laws, not to the anti-fraud overlay.

The doctrinal effect of §4B(b)(4)(A) on the existing case law is direct. LBRY‘s holding that LBC distributions to early users were unregistered securities offers does not survive §4B(b)(4)(A) as applied to the LBRY fact pattern, at least prospectively. The SEC’s theory in Coinbase Earn that pooled-customer staking constituted a securities transaction is preserved only to the extent the staking service does not qualify as exclusively administrative or ministerial under the §4B(a)(5)(B)(iv)(II) rulemaking, which is to say only to the extent the Commission’s rule says so. The Kraken consent order is preserved as a historical compliance matter, but the substantive theory underlying it is foreclosed prospectively. Jarrett v. United States, 1:21-cv-00419 (M.D. Tenn.), and the tax-side staking-rewards realization analysis remain live questions on a different track; §4B(b)(4) deals only with the securities-law treatment of staking.

Cross-Reference to Bank-Permitted Activities

§401(g)(2), covered in Post #9 of this series, authorizes national banks and federally insured depository institutions to provide staking and “related services” to customers. The provision works alongside §4B(a)(5)(B)(iv). Banks may offer custodial staking under the §401(g)(2) authority; the staking rewards delivered to customers in connection with that activity are gratuitous distributions under §4B(a)(5)(B)(iv) to the extent the bank’s service satisfies the exclusively administrative or ministerial standard the SEC will define. The combined effect is that banks can offer custodial staking products in the same way they offer custodial securities-lending and cash-sweep products, without the principal product (the reward) being a separate security.

The state-bank parity provisions in §401(d) extend the same authority to state-chartered banks meeting the FDIC’s parallel determinations. The credit-union provisions in §401(e) and (f) extend it to federally insured credit unions. The customer experience under CLARITY is that staking will become a routine banking product, indistinguishable in user interface from a savings account except in the substantive economics of the underlying mechanism. The SEC rulemaking under §4B(a)(5)(B)(iv)(II) will set the operational rules.

Liquid-Staking Carve-Out and the Administrative-or-Ministerial Framing

Clause (iii)’s “administrative or ministerial receipts and not providing discretionary management authority” qualifier is the load-bearing element of the LST treatment. The SEC’s pre-CLARITY interpretive posture, as developed in the joint interpretive release of March 2026, treated LSTs as receipts for non-security digital commodities, subject to specified conditions including no rehypothecation, no lending without consent, and custody designed to prevent third-party claims. CLARITY codifies a compatible position and, importantly, does not require the joint-release conditions to be satisfied as a matter of definition. The statutory test is administrative-or-ministerial-receipt character and non-discretionary management.

A well-structured LST satisfies the test. The token represents a pro rata claim on a pool of staked tokens and accruing rewards. The issuer’s role is limited to running validator infrastructure, accepting deposits, issuing receipt tokens, and processing redemptions according to a predetermined formula. No discretionary management is involved. The rewards flow mechanically from the protocol to the staking contract to the token holders, with the issuer taking a fixed fee from the gross reward stream.

A poorly-structured LST does not. An LST that confers on the issuer discretionary authority to redirect capital among different chains, to engage in leveraged staking strategies, or to execute MEV-extraction-and-share programs on staked capital is, structurally, an actively-managed pooled investment vehicle. Clause (iii) does not protect it. The administrative-or-ministerial language is the gating test.

Two structuring implications follow. First, LST issuers who want clause (iii) treatment should design the issuance-and-redemption mechanism to be fully programmatic. The smart contracts should accept ETH, deposit it with predetermined validator operators, and mint stETH or rETH or equivalent in proportion. Discretionary validator selection by the issuer is permissible, but discretionary capital reallocation outside the staking activity is not.

Second, restaking protocols (EigenLayer and its analogs) sit at the edge of clause (iii). A restaking position involves the staking of an already-staked LST or LRT to secure additional services. The restaker accepts additional slashing risk in exchange for additional reward streams. The restaking layer’s treatment depends on whether the issuance, transfer, and redemption of the restaking receipt token operates as administrative-or-ministerial receipts of the additional reward stream, or as a more discretionary management of additional risk-reward exposure. The joint SEC-CFTC interpretation expressly declines to address restaking (Release No. 33-11412, footnote 107), which means the SEC’s eventual rulemaking under §4B(a)(5)(B)(iv)(II) (and any subsequent interpretive release) will carry the analytical weight. The structural answer for a properly-built restaking protocol is that the receipt token tracks a programmatic position with no discretionary management, in which case clause (iii) covers it. But restaking-specific guidance is not yet available, and practitioners structuring restaking offerings should plan for an extended period of interpretive uncertainty.

The joint release’s Staking Receipt Token analysis is, however, fully applicable to ordinary (non-restaked) liquid staking. The release treats an SRT that is a receipt for a non-security crypto asset not subject to an investment contract as itself a receipt rather than a security, on the theory that the SRT evidences ownership of the deposited digital commodity (and its accruing rewards) without providing any independent essential managerial efforts. The definition of “security” in §2(a)(1) of the Securities Act expressly includes a “receipt for” a security, but a receipt for a non-security is not a security. The release reaches this conclusion for both protocol-based liquid staking providers (Lido, Rocket Pool) and third-party liquid staking providers (custodial models with receipt-token issuance), subject to the same custody-and-non-discretion conditions described above for custodial staking. The SRT secondary-market trading is also covered. This is the substantive interpretive piece that practitioners structuring LST offerings have been pressing for since 2022, and it is now in place.

Airdrops and the LBRY Problem

The LBRY holding deserves attention because it was the high-water mark of the SEC’s pre-CLARITY airdrop theory. The court held that LBC, distributed through a series of programmatic mechanisms including mining rewards, content-creator rewards, and operating-system airdrops, constituted unregistered securities offers because purchasers had a reasonable expectation of profits from LBRY Inc.’s ongoing development efforts.

Under §4B(b)(4)(A), the same fact pattern (programmatic mining rewards, content-creator rewards, operating-system airdrops) is presumptively not a securities offering. Each of the three distribution mechanisms maps onto clause (v) of §4B(a)(5)(B): they are automated, programmatic, protocol-defined, rules-based, and proportionate to verifiable contribution. The non-security presumption applies. To rebut, the SEC would need to establish, against the §4B(b)(4)(B) carve-out, that some anti-fraud or anti-manipulation violation occurred, not merely that the distributions otherwise satisfied Howey.

The structural shift is that Howey compliance with respect to a gratuitous distribution is now decided by the §4B(b)(4) presumption, not by a fresh four-prong analysis. The four prongs continue to operate as the theoretical foundation; an originator-controlled offering of an ancillary asset in exchange for cash is still an investment contract under §4B(b)(1). But a gratuitous distribution, by statutory presumption, does not satisfy the offer-or-sale element of §5. The case is over.

The retroactive cleanup in §4B(k)(3) extends the presumption to pre-effective-date gratuitous distributions, foreclosing future SEC enforcement based on historical airdrop conduct, provided the originator complies with the §4B(c)(3) transition disclosure obligations. The LBRY judgment remains as a final adjudication, but no future LBRY-style case can be brought.

The joint SEC-CFTC release adds a doctrinal layer that runs alongside the statutory presumption. Section VII of Release No. 33-11412 interprets the Howey “investment of money” prong with respect to airdrops, concluding that recipients who do not provide money, goods, services, or other consideration to the issuer in exchange for the airdropped non-security crypto asset have not made an “investment of money,” and that the Howey test therefore fails at the first prong. The release identifies three illustrative scenarios within the interpretation: an airdrop to existing holders of another specified crypto asset where the issuer does not announce the airdrop before dissemination; an airdrop to users of a testing-environment version of a crypto system after deployment; and an airdrop to users of a related software application based on prior use, where the issuer does not announce the airdrop before dissemination. The release excludes airdrops in which the recipient provides consideration in exchange for the asset (such as a service performed in exchange for the airdrop) or where recipients must fulfill conditions subsequent to the airdrop announcement to receive the asset. For airdrops that fit within the release’s interpretation, the conclusion that no investment contract is created is independent of CLARITY’s §4B(b)(4) presumption: the Howey test simply does not apply because one of its required elements is missing. The two frameworks operate in parallel, with the joint release providing the constitutional-and-doctrinal foundation and CLARITY providing the statutory backstop and procedural mechanisms.

Practitioner Structuring Takeaways

For protocols planning post-CLARITY token launches, the gratuitous-distribution architecture is the most generous channel available. A retroactive airdrop sized to historical on-chain activity, distributed proportionately to objective metrics, with no individualized negotiation and no discretionary “contributor” allocations, satisfies clause (v) and receives the §4B(b)(4) non-security presumption. The originator avoids §5 registration, avoids the §4B(d) disclosure menu (which attaches only to ancillary assets, not to gratuitous distributions, and the asset itself can be a network token without ancillary-asset status if its value does not depend on continuing originator efforts), and lands in a posture closer to the pre-2017 ICO-era treatment of community distributions, but with statutory rather than enforcement-discretion support.

For staking-service operators, the path forward is the §4B(a)(5)(B)(iv) rulemaking. The crypto-industry comment-letter effort will be focused on getting “administrative or ministerial” defined broadly enough to cover the operational realities of custodial staking. The traditional-securities-bar position will be that the term should be construed against the issuer in cases of pooled customer assets and aggregated validator selection. Operators should plan for a regulatory line that covers operational custody but does not protect discretionary capital management of staked assets.

For liquid-staking protocol issuers, the design principle is administrative-or-ministerial-receipt character. Issuance, transfer, and redemption should be programmatic. Discretionary management should be excluded from the issuer’s role. Fee structures should be fixed and transparent. The Lido and Rocket Pool architectures are within the safe side of the line; any restaking or active-validator-selection design needs to be evaluated against the (iii) standard with care.

For airdrop designers, the design principle is rules-based proportionate distribution. Snapshot dates, eligibility criteria, and allocation formulas should be objectively measurable and publicly disclosed in advance. Discretionary contributor awards should be moved to a separate program with separate documentation; mixing rules-based and discretionary distributions in a single airdrop transaction is the principal way to lose clause (v) coverage for the entire transaction.

The §4B(a)(5) framework is, in the aggregate, the most consequential statutory accommodation of post-Ethereum token economics yet enacted. Staking is gratuitous. Airdrops are gratuitous. LSTs are gratuitous receipts. Custodial staking can be gratuitous once the SEC defines administrative-or-ministerial. And the technology-neutral clause means the framework keeps working as the underlying mechanics evolve. The tax treatment of these distributions remains a separate question, sequenced with the tax-article queue covered in Post #16 of this series, but the securities-law treatment is now resolved.

Written by David Lopez Kurtz