SEC staff FAQs separate issuer promises from token classification

On Sept. 25 the SEC's Division of Corporation Finance published its first staff reading of the Commission's March 17, 2026 interpretive release on crypto assets, a set of answers about how the federal securities laws apply to tokens and transactions in them, and three days later the page carried an updated date of Sept. 28. The front matter is unusually emphatic: the answers are the views of Corp Fin staff, not a rule or a Commission statement, the Commission has neither approved nor disapproved them, and like all staff guidance they have no legal force or effect, alter no applicable law, and create no new obligations.

None of that binds issuers because the statutory layer does not exist: the Senate's Clarity Act failed at 49-50, and the definitions a market-structure statute would have fixed are now coming out of the agencies — SEC and CFTC releases, staff guidance, examiners' expectations. The SEC is working with two members after Peirce's exit, a thin bench for decisions as consequential as the five-year tokenized-stock exemption still before it, so guidance published into that gap binds nobody; for an issuer weighing whether to list a token or how to describe a staking product, a staff FAQ is the nearest thing to an operating manual.

The answers also inherit their vocabulary wholesale: unless a term is defined in the document itself, it carries the meaning given in the March 17 release, which makes the FAQ a supplement rather than a substitute. An issuer reading only the FAQ is reading commentary on a text it still has to consult, one issued by the Commission rather than by its staff, and that distinction is what gives the underlying release its weight.

Question 1.1 addresses a split the March release set up: the release defines "functional" and "decentralized," and provides that whether an issuer fulfilled its representations or promises to engage in essential managerial efforts is judged by how the issuer defined or otherwise described those terms, not by any general market conception.

Staff's answer separates the two uses: the definitions do not bear on whether an issuer kept its promises, because each issuer sets the thresholds that must be met for its own representations, but they do bear on how the Commission classifies crypto assets under Section III of the release, the section to which both published questions point.

The consequences land on anyone drafting offering materials: the label the Commission attaches to an asset under Section III is measured against the Commission's own definitions, while whether an issuer delivered on a decentralization promise is measured against its own words, a standard that reaches how a project otherwise described the term as well as how it defined it, so an informal characterization can supply the yardstick as readily as a defined milestone. An issuer that wrote a modest definition of decentralization into its own materials has set itself a low bar on the promise question and moved nothing on the classification question; the two tracks do not trade off. That reading is an inference from the staff's answer rather than a statement in it, and the answer itself goes no further than saying the definitions are not relevant to fulfillment and are relevant to classification.

A quieter point in the same answer: staff does not say the release's definitions are irrelevant to issuers, only that they are irrelevant to one question and controlling of another, so a project that has argued the Commission's own definitions are too demanding to meet has been arguing about the wrong document. Its representations are measured against its own description whatever the release says, and the release's definitions govern the asset's label whatever the issuer says.

Question 1.2 takes up Staking Receipt Tokens, the transferable claims a holder receives when staked assets are pooled, and staff offers two routes: under the circumstances in the release, a Staking Receipt Token that is a receipt for a digital commodity not subject to an investment contract is itself a digital tool, because a receipt evidences the holder's ownership of the underlying commodity, while the same instrument may instead be classified as a digital commodity when a protocol-based Liquid Staking Provider issues it and the token is intrinsically linked to, and derives its value from, the programmatic operation.

The fork runs through the issuer rather than the holder: two receipt tokens can give an investor the same exposure, a claim on assets staked through a protocol, and land in different categories depending on whether the issuer is a protocol-based Liquid Staking Provider, with nothing in the holder's experience to distinguish them. Which label applies is the sort of determination that feeds listing and disclosure analysis at a venue or broker, though the FAQ does not work through those downstream steps.

The answer also lands beside a separate staff project: the staking guidance now in preparation, itself revocable. Both documents are staff-level, both can be rewritten or withdrawn without a Commission vote, and between them they supply most of what an exchange or a staking provider has to work from when it decides what it can offer and how to describe it.

That matters more as the wrapper becomes the distribution channel: once a spot product clears the SEC, flows follow the wrapper rather than the statute, a pattern visible in record inflows into Solana spot ETFs. Whether a staking receipt token is a digital tool or a digital commodity is upstream of what can be packaged and sold that way, and the answer now turns on an issuer attribute that no investor can see on a statement.

The page's architecture reinforces that reading: the two published questions are numbered 1.1 and 1.2, a set organized to be extended rather than closed, and the header records an original issuance of Sept. 25 and an update three days later without identifying what the revision changed. A three-day revision cycle on a guidance document reads as maintenance, a living page kept the way a compliance desk keeps its own, while the two-member Commission that issued the underlying release decides what else it wants to say.

The Commission can amend or abandon an interpretive release, and this one sits with a body that will operate at two members for the near term; staff can revise these answers again; and the definitions the FAQ declines to apply to issuer promises will eventually be read against the marketing language of an actual offering. The operative text today is the one issued Sept. 25 and revised Sept. 28: no legal force, no Commission approval, and a revision history three days long.