SEC’s New Playbook: Building After Launch Without Howey

• Developers can continue maintaining and improving a functional crypto network without those activities alone satisfying the managerial-efforts element discussed by SEC staff.
• Token buybacks receive different treatment depending on whether the network is functional and how the buyback is marketed.
• The FAQs also clarify the treatment of staking receipt tokens, crypto marketing and secondary-market platforms. 

For years, crypto projects have faced an awkward securities-law question: when does development stop being an investment promise and become ordinary software work?

The SEC’s Division of Corporation Finance has now drawn a clearer boundary.

In FAQs published September 25, staff said developers can continue securing, maintaining and improving a functional crypto network, fund development projects and help expand network effects without those activities constituting the “essential managerial efforts” relevant under the Howey test.

The same document addresses something even closer to traditional finance: token buybacks. Once a crypto system is functional, announcing a buyback of a non-security crypto asset does not, by itself, amount to a promise of essential managerial efforts. Before functionality, however, marketing that buyback as a source of yield or return can change the analysis.

The emerging distinction is not between active developers and absent developers.
It is between developers maintaining a product that already works and purchasers funding promises about what that product will become.

Crypto Doesn’t Have to Become Abandoned Software

The problem begins with something ordinary technology companies rarely need to explain: software keeps changing.

Blockchains need security updates. Developers fix bugs. Protocols add functionality. Foundations finance development. Ecosystems spend money attracting applications and users.

In crypto, those activities can intersect with Howey because an investment-contract analysis can consider whether purchasers reasonably expect profits based on someone else’s essential managerial efforts.

That creates a strange potential outcome. A network might already work, yet the developers responsible for maintaining it could appear to remain economically important to token holders simply because they have not stopped developing it.

The SEC staff’s answer is much more practical.

Once a crypto system is functional, services that secure, maintain, improve or enhance it, or facilitate network effects, do not constitute essential managerial efforts under the interpretation referenced in the FAQ. Sponsoring and funding development projects can fall within that category too.

So continued development is not automatically the problem.

What purchasers were promised before functionality remains far more important.

The Whitepaper May Matter More Than the GitHub Commits

That becomes especially clear in the section on marketing.

Staff says promoting the current utility and capabilities of a crypto system likely would not, without more, amount to a promise of essential managerial efforts.

Projects can even discuss potential features and future utility using indefinite, aspirational language, provided those communications do not promote the potential for profit. The assessment remains dependent on the facts and circumstances.

That gives development teams a meaningful distinction when communicating with users.

A project explaining what its network does, or discussing functionality it hopes to develop, is different from telling token buyers that the team’s future work will generate their financial returns.

This makes marketing copy more than a branding issue.

Websites, token documentation, social posts and buyback announcements can help establish what purchasers were actually led to expect from the people building the network.

Buybacks Expose the Difference Better Than Almost Anything Else

Token buybacks are where the SEC staff’s approach becomes particularly interesting because they look so familiar to traditional investors.

Projects can use protocol revenue or treasury assets to repurchase their own tokens. Sometimes the assets are burned. Sometimes supply is reduced. Sometimes projects openly discuss the potential effect on token holders.

But staff does not treat the existence of a buyback as decisive.

For a functional crypto system, announcing a buyback program for a non-security crypto asset would not constitute a promise to undertake essential managerial efforts.

For a system that is not yet functional, the result can be different when the issuer presents the program as creating yield or returns for holders.

The buyback itself is therefore only part of the analysis.

How the project sells the idea to purchasers matters too.

That is a useful warning for crypto teams tempted to borrow the language of public-company capital returns.

Calling a token repurchase a source of investor yield can carry a very different implication from describing it as treasury management, supply reduction or a protocol-funded burn.

Staking Receipts Get a Test Based on What They Actually Do

The FAQs take a similarly functional approach to staking receipt tokens.

A staking receipt token representing a digital commodity that is not subject to an investment contract can qualify as a digital tool when it simply evidences the holder’s ownership of the deposited asset.

A receipt issued by a protocol-based liquid staking provider may instead qualify as a digital commodity because its value is intrinsically linked to the programmatic operation of a functional crypto system and market supply and demand.

But staff also places tight boundaries around what counts as a receipt.

The instrument cannot add new economic rights or incentives to the deposited asset. More importantly, ownership or control cannot effectively pass to the issuer.

That means the issuer cannot lend, pledge, rehypothecate, transfer or otherwise use the deposited asset, or expose it to third-party claims.

This separates two structures that can look similar on a trading screen.

One token may simply prove ownership of an asset sitting somewhere else. Another may sit on top of a structure in which those underlying assets are being deployed economically.

Calling both a “receipt” does not make them the same thing.

A Crypto Exchange Isn’t Automatically a Promoter

The SEC staff also removes one potential complication for secondary trading.

Simply offering a market for a crypto asset does not automatically make an exchange a promoter of that asset.

A trading platform would be treated as a promoter for this analysis only if it meets the definition of “promoter” under Securities Act Rule 405.

That separates providing liquidity from becoming part of the promotional machinery surrounding a token.

It is a narrow clarification, but an important one for a market where hundreds of assets can trade on the same venue without the exchange having participated in their development or original distribution.

Decentralization Can Eventually Weaken the Power of the Original Issuer

The FAQs then describe what happens at the far end of a project’s development.

Suppose a crypto system is functional and no central party controls it.

Staff says statements by the original issuer would then be unlikely to create a new investment contract because neither that issuer nor another person controls the system sufficiently to take actions determining its success or failure.

That creates an interesting lifecycle.

Early in a project’s existence, the developer’s promises can be crucial because purchasers may be relying on that team to create something that does not yet function.

Later, the same developer can become progressively less important to the legal analysis as the functioning network becomes less dependent on any central party.

The token has not necessarily changed.

What changed is who, if anyone, holders still need to trust to make the system work.

What Crypto Projects Actually Need to Review

The September FAQs therefore give projects something more useful than a generic instruction to “decentralize.”

Teams with functional networks can examine whether their ongoing development really resembles maintenance and improvement rather than fulfillment of investment promises.

Marketing deserves a separate review. Describing current utility is one thing; linking future development to holder profits can create a different factual record.

Buyback communications require the same discipline, particularly before functionality. And projects issuing staking or wrapped receipts need to look beyond the token’s name to whether deposited assets remain genuinely owned and controlled by the depositor.

None of these points operates as an automatic safe harbor. The staff repeatedly grounds its answers in specific circumstances and existing securities-law concepts.

This Is a Map, Not a New SEC Rule

There is one limitation that should sit beside every interpretation of the document.

These FAQs come from the staff of the Division of Corporation Finance. They are not an SEC rule, regulation or Commission statement. The Commission has neither approved nor disapproved them, and the document expressly says the FAQs carry no independent legal force and create no new obligations.

Their value is instead in showing how staff currently approaches situations crypto projects encounter after launch.

And the most consequential clarification may be the simplest one.

A functioning blockchain does not need its developers to vanish.

They can keep fixing code, financing development and expanding the network. The securities-law question increasingly turns on something more specific: whether token holders are still buying into promises that those developers will create their profit, or simply using and holding an asset attached to software that continues to evolve.