What the Phantom No-Action Letter Means for Web3 Builders

The Commodity Futures Trading Commission (CFTC) has issued a significant no-action letter that could reshape how crypto wallet providers and frontend platforms interact with regulated derivatives markets.

In CFTC Staff Letter No. 26-09 (March 17, 2026), the agency signaled a more nuanced approach to applying traditional broker registration rules to modern, non-custodial crypto technologies.

For Web3 founders, infrastructure providers, and legal teams, this is a meaningful step toward regulatory clarity.

The Core Issue: When Does Software Become a Broker?

Under the Commodity Exchange Act, entities that solicit or accept orders for derivatives must register as:

• Introducing Brokers (IBs), and

• Associated Persons (APs)

Historically, the CFTC has taken a broad view of what constitutes “solicitation,” capturing a wide range of intermediary activities.

This creates friction for modern crypto products—especially:

• Wallets

• Trading interfaces

• Aggregators

• Frontend dApps

These tools often enable trading without directly executing or controlling it.

Enter Phantom: A Test Case for Web3 Infrastructure

Phantom Technologies, known for its self-custodial crypto wallet, proposed expanding its product to allow users to access CFTC-regulated derivatives markets via integrated frontend software.

Key features of the model:

• Users submit orders directly to registered entities (FCMs, IBs, or exchanges)

• Phantom does not custody assets

• Phantom does not execute trades or provide trading signals

• The software acts purely as an interface layer

Despite this, some of Phantom’s activities like marketing and introducing users to trading venues would typically trigger broker registration requirements.

The CFTC’s Position: Conditional Relief

The CFTC’s Market Participants Division granted no-action relief, meaning it will not recommend enforcement action if Phantom operates under specific conditions.

Why the Relief Was Granted

The CFTC emphasized that Phantom:

• Plays a passive role in order routing

• Does not influence execution decisions

• Does not generate buy/sell signals

• Does not custody or control user funds

In essence, the platform functions more like infrastructure than an intermediary.

The Conditions: Guardrails for Web3 Builders

The relief is not unconditional. Phantom must comply with a robust framework, including:

1. Transparency & Disclosures

• Clear disclosure of relationships with trading counterparties

• User acknowledgment of risks and conflicts

2. No Custody, No Control

• Users maintain assets with regulated entities (e.g., FCMs, DCOs)

• Phantom cannot control or route trades

3. Compliance-Like Behavior

• Must follow marketing standards similar to registered brokers

• Cannot engage in misleading promotions

4. Joint Liability Structure

• Phantom and its partners must accept shared liability for violations

5. Recordkeeping & Oversight

• Maintain detailed compliance records

• Notify regulators of insolvency or major changes

Why This Matters

1. A Blueprint for “Non-Custodial Frontends”

This letter provides one of the clearest signals yet that:

Not all trading-related software must be regulated as a broker.

If structured correctly, frontend platforms can:

• Enable access

• Facilitate interaction

• Without triggering full broker-dealer style obligations

2. Recognition of Modern Market Architecture

The CFTC implicitly acknowledges a shift:

From:
Intermediary-driven markets

To:
Interface-driven, user-directed systems

This aligns closely with how Web3 ecosystems operate today.

3. A Step Toward Regulatory Clarity 

Important caveat:

• This is staff-level guidance, not binding law

• It can be modified, withdrawn, or superseded at any time

Still, it signals how regulators are thinking and where policy may go next.

Key Takeaways for Founders & Builders

If you’re building in Web3, especially:

• Wallets

• Trading interfaces

• Aggregators

• DeFi frontends

This letter offers a strategic roadmap:

Design Principles to Consider

• Avoid custody of user assets

• Avoid trade execution or routing discretion

• Avoid generating trading signals

• Maintain clear separation from regulated counterparties

• Build in disclosures and compliance frameworks early

The Bigger Picture

This development sits at the intersection of:

• Traditional financial regulation

• Decentralized infrastructure

• User-controlled finance

It reflects a growing recognition that:

Code is not always a broker and interfaces are not always intermediaries.

Learn more