SEC Liquid Staking Guidance: Contract Conditions for LSTs

Video transcript

Under the SEC's 2026 crypto interpretation, a liquid staking token for ETH is not a security when it works as described. Each condition is something a contract does, or an admin key can undo.

The release took effect March 23 and names 16 example digital commodities, including ETH and SOL. This is the technical side, not legal advice.

The provider never decides whether, when or how much to stake, and never guarantees or sets rewards. Tokens issue one-for-one and redeem at any time, subject to unbonding.

In code, deposit routing governs staking, oracles and fee setters govern rewards, mint logic governs issuance, and the withdrawal queue governs redemption.

Code that fits the release today can stop fitting it after a single admin transaction.

A proxy upgrade can rewrite any rule. Withdrawal pauses threaten redemption, uncapped fees can decide what holders keep, and extra minters threaten one-for-one issuance. Holders matter as much as functions.

Counsel owns the legal reading, engineering owns the facts. Hand over every contract, deposit path, oracle and fee cap, supply against deposits, a redemption test, and every role holder.

Guardian audits staking tokens with invariant fuzzing and senior manual review. Our regulatory work maps every privileged role, and configuration drift tracking dates each change against what was reviewed.

Read the full article, or talk to Guardian at guardian.security to check your token against the release.

The SEC's March 17, 2026 crypto interpretation, joined by CFTC guidance, took effect on March 23. It has a section on Liquid Staking.

Each condition it sets is something a contract does, or an admin key can undo.

This article explains the technical and security side of SEC Release No. 33-11412 and the Division of Corporation Finance's crypto asset FAQs. It is not legal advice; confirm how it applies to you with counsel.

What the Release Says

The release supersedes earlier staff statements, including the August 5, 2025 statement on liquid staking.

It describes Liquid Staking as one of four types of Protocol Staking:

• A Depositor gives a Liquid Staking Provider a digital commodity, such as ETH.
• The provider stakes it, through its own node or an operator it selects.
• The Depositor receives a Staking Receipt Token evidencing the deposit and its rewards.

Providers can be protocol-based, run by self-executing code, or third parties such as custodians.

The Commission's view: such a token, as described, is not a security if the underlying asset is neither a security nor subject to an investment contract.

If the asset is either, the receipt is a security. The release names 16 example digital commodities, including ETH and SOL.

The Four Conditions

Footnotes 125 and 126 put a provider that selects whether, when or how much to stake, or guarantees or sets rewards, outside the release.

Two details for token design:

• One-for-one allows fractions: one unit deposited may be issued as less than one whole token (footnote 115).
• Rewards may show as a rising rate per token, or as extra tokens. As mechanics only, Lido's wstETH works the first way, stETH the second.

FAQs 1.2 and 1.3

The Division of Corporation Finance's crypto FAQs, first issued September 25, 2026, are staff views with no legal force or effect.

FAQ 1.2 calls such a token a "digital tool" because it is a receipt. It "also may be classified as a digital commodity if it is issued by a protocol-based Liquid Staking Provider."

FAQ 1.3 defines a receipt. It does not transfer ownership or control of the deposit to the issuer.

The issuer "cannot transfer, lend, pledge, rehypothecate, or otherwise use the deposited asset for any reason, or subject the asset to claims by third parties."

The release says much the same of custodial staking, and calls Liquid Staking "like" it. It leaves restaking out entirely (footnote 107).

Footnote 131 adds a limit: where the provider supplies the means to earn extra returns on the token, that activity is outside the release.

Where Each Condition Lives in Code

Lido's docs show where these functions sit in a live protocol. They illustrate mechanics, not whether Lido meets the conditions.

Deposit routing

In Lido, only the DepositSecurityModule can call the StakingRouter's deposit(), and an allocation algorithm splits ether across modules.

Lido's pauseStaking() stops accepting new ether, and setStakingLimit() rate-limits it. How intake controls bear on discretion is for counsel; list each with its holder.

Operator registry

Choosing operators is the provider's only decision, and the release says it may be automated. Record who can add, remove or reweight them.

In Lido, new staking modules go through a DAO vote, and STAKING_MODULE_MANAGE_ROLE updates module fees and limits.

Fee setters and oracles

Fees are allowed, fixed or percentage. Rewards should come from reported validator balances, not an admin-entered number.

Lido's oracle committee reaches quorum when more than half submit the same report hash. A sanity checker bounds balance changes.

Check the cap on every fee setter; an uncapped fee can decide what holders keep.

Mint and burn

Every mint should trace to a deposit at the current rate, or to a stated fee. Look for admin mints, bridge mints and fee shares.

Lido, for example, pays protocol fees by minting new stETH on each oracle report.

See how mint rights fail in DeFi security by protocol type.

Withdrawal queue

In Lido, a holder requests a withdrawal and receives an NFT. An oracle report finalizes requests, and the holder then claims ether.

Lido's PAUSE_ROLE can pause requests and finalization, for a set time or indefinitely. Claims stay open while paused.

The release does not discuss pauses. For any protocol, give counsel each pause, its holder and its longest possible duration.

Admin Powers That Can Break Them

Code that fits the release today can stop fitting it after one admin transaction.

Holders matter as much as functions. A pause behind a DAO vote and a timelock differs from one an EOA can call.

Our post on the SEC central party test covers which admin powers the staff single out.

Ancillary Services the Release Allows

The release treats four services as administrative or ministerial:

• Slashing coverage: reimbursing stakers for slashing losses.
• Early unbonding: returning assets before the unbonding period ends.
• Alternate reward schedules: a different cadence, never fixed, guaranteed or above protocol rewards.
• Aggregation: pooling deposits to meet a staking minimum.

Other services fall outside the release (footnote 127). In code, keep each apart from the core redemption path.

The Inventory to Hand Counsel

Counsel owns the legal reading; engineering owns the facts. Stamp each item with a block number.

1. Scope: every contract on every chain, with verified source matching deployed bytecode.
2. Deposit flows: every path deposits can take, and the function behind each.
3. Staking decisions: what runs by rule, and what any role can pause, cap or redirect.
4. Rewards: oracle members, quorum, sanity limits, fee setters and fee caps.
5. Supply: every minter, and a check that supply matches deposits at the current rate.
6. Redemption: a request-to-claim test on a fork, with every pause listed.
7. Roles: each holder as EOA, multisig, timelock or DAO, with thresholds, delays and change history.

How Guardian Helps

Guardian's smart contract audits cover staking tokens with a design review, an invariant fuzzing suite and senior manual review.

Invariants such as "every token is backed at the current rate" and "a withdrawal request can be made" turn the release's description into tests.

Guardian's regulatory and compliance work adds a privileged role and upgrade path map. It lists every role that can move value, upgrade, pause or change parameters, with its holder.

Contract configuration drift then dates every change against what was reviewed.

Frequently Asked Questions

Is liquid staking a security under the SEC's 2026 interpretation?

Not as Release 33-11412 describes it, for a receipt for a non-security asset such as ETH. The provider has no staking discretion and sets no rewards; tokens issue one-for-one and redeem at any time, subject to unbonding.

Does the release cover liquid restaking tokens?

No. Footnote 107 says the release does not address restaking. Footnote 131 also leaves out any means a provider supplies to earn extra returns on the token.

Does a withdrawal pause break the redemption condition?

The release does not discuss pauses; it says tokens can be redeemed at any time, subject to unbonding. Give counsel every pause that can block requests, with its holder and longest duration.

Are the SEC's crypto FAQs binding?

No. They are Division of Corporation Finance staff views with no legal force or effect. The release itself is a Commission interpretation, with CFTC guidance, effective March 23, 2026.

Sources

• Federal Register: Release No. 33-11412, Application of the Federal Securities Laws to Certain Types of Crypto Assets, 91 FR 13714 (Mar. 23, 2026)
• GovInfo: FR Doc. 2026-05635, official PDF of Release No. 33-11412 (Mar. 23, 2026)
• SEC Division of Corporation Finance: Frequently Asked Questions on crypto assets, Questions 1.2 and 1.3 (issued Sept. 25, 2026; updated Nov. 2, 2026)
• Lido Docs: Lido (stETH) contract
• Lido Docs: wstETH
• Lido Docs: StakingRouter
• Lido Docs: AccountingOracle
• Lido Docs: WithdrawalQueueERC721