CFTC to Protect Non-Custodial Devs After Phantom Case

CFTC to Protect Non-Custodial Devs After Phantom Case 2

The Commodity Futures Trading Commission (CFTC) is contemplating formal rulemaking to establish clear guidelines regarding the registration requirements for software developers, particularly concerning non-custodial wallet providers. This initiative aims to solidify the agency’s stance and provide greater certainty for businesses operating within the digital asset space.

Key Takeaways

  • CFTC Chair Michael Selig intends to transition the agency’s recent no-action letter regarding software developers into formal rulemaking.
  • The proposed rules aim to protect non-custodial software developers from being required to register as brokers under certain conditions.
  • This move aligns with recent guidance from the Securities and Exchange Commission (SEC) concerning DeFi interfaces.
  • The CFTC also affirmed its exclusive jurisdiction over prediction markets, signaling continued enforcement against state-level infringements.

CFTC Chair Michael Selig has indicated that the agency is moving towards codifying its position on whether software developers need to register as brokers. This follows a March no-action letter that provided relief to Phantom, a crypto wallet provider. The letter clarified that developers of self-custodial wallet software, under specific circumstances, are not required to register as brokers with the CFTC. Selig expressed a preference for formal rulemaking, stating, “I prefer rulemaking, and so we’re going to work to codify that and get it in rules very soon.” This approach is part of a broader strategy to foster a more favorable regulatory environment for the cryptocurrency industry in the United States, following a “crawl, walk, run” methodology to provide clear guidance.

This regulatory development appears to parallel efforts by the Securities and Exchange Commission (SEC). Last month, the SEC’s Division of Trading and Markets issued a staff statement suggesting that certain interfaces, including those associated with decentralized finance (DeFi) wallets, would generally not be classified as brokers. This guidance was presented as an interim measure while the SEC continues to evaluate various regulatory considerations.

Potential Regulatory Precedent

The CFTC’s stated intention to codify protections for non-custodial software developers could establish a significant regulatory precedent. By moving from no-action letters to formal rulemaking, the CFTC would create a more definitive legal framework, reducing ambiguity for innovators in the digital asset sector. Such a move could influence how other regulatory bodies, both domestically and internationally, approach the classification and oversight of blockchain-based software and services. The alignment with the SEC’s recent staff statement suggests a potential for inter-agency cooperation or at least a shared understanding of the evolving technological landscape, which could foster greater regulatory coherence across different aspects of the digital asset market. The legal stakes for companies involved are substantial, as clear rules can facilitate investment and innovation while mitigating the risk of enforcement actions.

Furthermore, Selig used the Consensus Miami conference to reiterate the CFTC’s exclusive jurisdiction over prediction markets. He confirmed the agency’s commitment to pursuing legal action against states that attempt to regulate these markets, asserting federal authority. The CFTC has already filed lawsuits against several states, including Wisconsin, Illinois, Arizona, Connecticut, and New York, for enacting bans that conflict with federal jurisdiction, particularly concerning predictions related to sports betting. Selig emphasized, “We’ll continue to bring lawsuits whenever we see these impinge on our authority,” underscoring the CFTC’s assertive approach to maintaining its regulatory purview.

Source: : www.theblock.co

No votes yet.
Please wait...

Leave a Reply

Your email address will not be published. Required fields are marked *