SEC tightens cryptocurrency repo guidance, attaching decentralization conditions

Securities and Exchange Commission's important limitations on guidance on cryptocurrency repurchase

Securities and Exchange Commission (SEC) staff have added an important limitation to their new guidance on cryptocurrency repurchase: the network must be in a "functional" state and no "centralized entities" exist for the answers described in the FAQ to apply. The September 28 revision narrows the scope of provisions that might have previously been interpreted as granting broad exemptions to functional networks simply because the software is running.

This change appeared in the frequently asked questions (FAQ) on crypto assets first released by the corporate finance department on September 25. The question in this section is whether announcing a repurchase constitutes a commitment to the management work on which token buyers rely. For projects that promote destruction, treasury purchases or supply reductions, these additional qualifiers are more noteworthy than general titles claiming buybacks have been approved.

Running software is only part of the problem

The revised answer distinguishes functional systems with decentralized agents from systems that have not yet achieved functionality. In the latter case, promoting buybacks as a source of revenue or return may constitute management commitments considered in the investment contract analysis. The document does not state that all tokens purchased by the Treasury are securities transactions; similarly, it does not approve all projects known as decentralization.

这种区分至关重要，因为即使是一个活跃的网络，仍可能高度依赖少数群体。一个项目可能在处理交易，但发行方仍控制着升级、国库支出或支持需求商业安排。因此，关注代币是否“能工作”的投资者，与关注谁来决定其经济未来的投资者，面临的是不同的问题。将这两个问题混为一谈，忽略了此次更新中最具影响力的部分。

周围的承诺仍然重要

该FAQ与委员会3月发布的解释性声明并列，并直接引用了后者。其更广泛的讨论将推广网络的现有能力与对未来管理努力及利润的具体承诺区分开来。运营中的产品并不意味着随后的所有宣传陈述都无关紧要。

考虑两个假设性的公告。一个说明协议已完成例行国库交易；另一个则承诺由可识别的管理团队反复购买代币，以提供特定的投资者回报。现金流可能看起来相似，但向买方提供的陈述却不同。更新的措辞使得难以将此类分析简化为单一的标签，如“回购”、“销毁”或“收入分享”。

Caution is also needed when it comes to decentralized statements. Governance votes alone cannot answer all questions about control. Who can change the rules, who implements decisions, and whether other parties assume outstanding commitments are all relevant factors in understanding the arrangement. The FAQ clearly states that transferring the issuer's commitment to another party does not automatically separate the token from the relevant investment contract.

Guidelines are not approvals for individual tokens

Staff papers are not new committee rules and do not change the law. This limits what projects and investors can infer from it. Listing assets on trading platforms, announcing repurchase plans by the treasury, and describing network upgrades by developers are still independent activities with their own facts.

Recognizing the existence of blockchain infrastructure does not remove the legal rights and responsibilities attached to the tool. The technology used to record ownership and the legal nature of what is owned are different levels of the same transaction.

For token holders, the real question is what the repurchase has changed. Purchases may temporarily reduce the circulation supply, but if the tokens are not permanently removed, they may later be re-entered into circulation. Treasury expenditures also consume resources that could otherwise be used for development or operations. Whether the number of tokens is reduced or the regulatory interpretation is more relaxed, there is no guarantee that demand will increase or market prices will rise.

Matters needing attention after revision

The next useful evidence will be how issuers describe their projects and whether their disclosures explain control, funding and execution. Clear announcements should allow readers to distinguish between authorization caps and completed purchases, discretionary policies and enforceable obligations, and token transfers and permanent destruction.

The September 28 edition is small but of far-reaching significance. It tells markets to look at the organizational structure behind functional networks, not just the fact that there is running code. Projects that rely on earlier terms need to read the updated answers in full before using them as support for their own arrangements.