The Securities and Exchange Commission's staff issued guidance saying that when a project announces a token buyback on a functioning network, that announcement by itself doesn't create a promise that turns the token into a security. The guidance narrows one of the tests the agency has used to decide when a digital asset falls under U.S. securities law. It applies to tokens on networks that are already operational, not to pre-launch projects or tokens sold with other promises attached.
What the guidance actually says
The core point is straightforward. A buyback announcement, on its own, isn't an investment contract. Under the long-standing Howey test, a security exists when there's an investment of money in a common enterprise with an expectation of profit from the efforts of others. The SEC staff's position is that saying you'll buy back tokens on a live network doesn't, by itself, create that expectation of profit from someone else's work. The token can keep functioning as a token.
The qualifier matters: "on a functional network." A network that isn't up and running yet is a different situation. So is a token whose buyback comes bundled with other promises, like a share of future revenue or a management team actively driving price. The guidance doesn't cover those cases, and it doesn't rewrite the Howey test. It just says one common feature of token projects—the buyback announcement—isn't enough on its own to trigger securities treatment.
Why this lands now
The SEC has spent years arguing in enforcement actions that token issuers' public statements and marketing helped turn their tokens into securities. Buyback promises have been part of that argument. Projects that said they'd repurchase tokens from the market, or that tied buybacks to network activity, gave the agency evidence that holders expected price support from the team's efforts.
This staff guidance pulls back from that position in a specific way. It says the announcement of a buyback, without more, doesn't flip a functional-network token into a security. That's a narrow carve-out, but it's a meaningful one for projects that have avoided buybacks for fear of securities liability. The staff guidance is not a rule, and it doesn't bind the Commission itself or the courts. It does signal how the staff is likely to treat these facts going forward.
The reaction from securities lawyers
One attorney's reaction cut to the heart of it: the guidance makes securities laws look "opt-in." The point isn't that the law changed—it's that the agency is now telling projects which behaviors will and won't trigger it. If a buyback announcement on a live network is fine, and a buyback plus a revenue share is not, then issuers can structure around the line. That's the opt-in framing: you decide whether to take on securities obligations by choosing which promises to make.
That reading is likely to get pushback. Critics of the agency's approach have long argued that crypto regulation happens through enforcement rather than clear rules, and staff guidance—issued without a formal notice-and-comment period—can be reversed by a future Commission or ignored by a court. The guidance also doesn't resolve the larger question of when a token sale itself is a securities offering, or how secondary-market trading fits in. It answers one narrow question about buybacks.
What the guidance does not cover
Several open items remain. The guidance is limited to buybacks on functional networks, so it says nothing about tokens on networks still in development. It doesn't address whether a buyback funded by token sales proceeds changes the analysis. It doesn't say how the agency will treat buyback announcements made before a network launches and then carried out afterward. And it doesn't resolve the status of tokens already subject to pending enforcement actions, where buyback promises may be one of several allegations.
For projects weighing a buyback, the immediate effect is that the staff's stated view is now on the record. Whether that view survives a change in leadership at the agency, or a court test, is unresolved. The guidance itself doesn't have a comment period or an effective date. It's staff-level, and it stands until it doesn't.
