If you build a crypto wallet that lets users access derivatives markets, are you a broker? According to the CFTC, the answer for Phantom wallet is no—at least not under the specific architecture Phantom proposed. The Commission has determined it will not pursue broker registration enforcement against Phantom over its planned derivatives trading feature, treating the wallet as a passive software interface rather than a regulated intermediary under the Commodity Exchange Act (“CEA”), 7 U.S.C. §§ 1 et seq.

This position matters well beyond Phantom. It is the clearest signal yet from the CFTC on where the line falls between “technology tool” and “regulated broker” in the crypto derivatives stack—a question that wallet providers, DeFi front-ends, and aggregator platforms have been navigating without definitive guidance for years.

Key Takeaways

• Passive interface, not broker: The CFTC has determined that Phantom’s proposed derivatives feature functions as a passive software interface, not a broker requiring registration under the CEA.
• Direct user-to-broker relationship preserved: The critical factor is that users transact directly with CFTC-registered intermediaries. Phantom does not stand between the user and the regulated counterparty.
• Fact-specific determination: This position is tied to the specific design of Phantom’s proposed feature. Other wallet providers cannot assume blanket exemption without analyzing their own architecture.
• Regulatory obligation shifts, not disappears: The CFTC is clarifying that registered brokers—not passive interfaces—bear the compliance burden. Derivatives trading remains fully regulated.

What Is the CFTC’s Position on Phantom?

The CFTC has indicated—through what appears to be either a no-action letter, staff advisory, or statement of enforcement discretion—that Phantom’s proposed derivatives trading integration does not require the wallet provider to register as a futures commission merchant (“FCM”) or introducing broker (“IB”).

Under the CEA, an FCM is any entity that solicits or accepts orders for commodity futures or swaps and accepts money or property to margin such trades. 7 U.S.C. § 1a(28). An introducing broker solicits or accepts orders for futures or swaps but does not hold customer funds. 7 U.S.C. § 1a(31). Both categories trigger registration with the CFTC and compliance with National Futures Association (“NFA”) requirements. See 7 U.S.C. § 6d (registration requirements); 17 C.F.R. Part 3 (registration regulations).

The CFTC’s conclusion rests on a determination that Phantom’s feature does not perform the functions that define brokerage activity under these provisions. The wallet provides a user interface through which traders access registered brokers—but Phantom itself does not solicit, accept, or execute orders, and does not hold customer margin.

Note: The exact form and citation of this CFTC determination should be confirmed against the primary source document before relying on it for compliance purposes. [Review flag: Seth to confirm whether this is formal no-action relief, a staff letter, or public statement, and insert proper citation.]

What Makes an Interface “Passive” Under CFTC Analysis?

The CFTC has long applied a functional analysis to registration questions—examining what an entity actually does, not what it calls itself. This approach, consistent with the CEA’s broad definitions, looks at the substance of the activity rather than its label.

Based on the available information, Phantom’s feature appears to satisfy several criteria that distinguish a passive technology tool from an active broker:

• No solicitation of orders: Phantom does not recommend specific trades, provide research or analysis, or actively encourage users to enter derivatives positions.
• No discretion over execution: Users independently select their broker and determine the terms of their trades. Phantom transmits instructions without modification.
• No custody of margin: Funds flow directly from the user’s self-custodied wallet to the registered broker. Phantom does not accept, hold, or control margin deposits.
• No counterparty exposure: Phantom does not take the opposite side of any derivatives transaction.

These factors mirror the functional indicia that courts and regulators have used to identify broker activity in the securities context as well. Under the Securities Exchange Act of 1934, courts examine whether a person is “engaged in the business” of effecting transactions “for the account of others,” looking at factors including whether the entity handles customer funds, participates in negotiations, or receives transaction-based compensation. See 15 U.S.C. § 78c(a)(4)(A); SEC v. Hansen, No. 83 Civ. 3692, 1984 WL 2413 (S.D.N.Y. Apr. 6, 1984) (articulating functional broker factors).

The CFTC’s parallel application of functional analysis under the CEA provides useful symmetry for entities that must navigate both regulatory regimes.

How Does This Compare to Prior CFTC Enforcement?

The Phantom position is best understood by contrast with cases where the CFTC did find broker or platform activity requiring registration:

• CFTC v. Ooki DAO, No. 3:22-cv-05416 (N.D. Cal. 2022): The CFTC brought enforcement against a decentralized protocol that directly offered leveraged and margined derivatives trading to US retail users without registering as a designated contract market or FCM. Unlike Phantom, Ooki DAO was the trading platform—it matched orders, facilitated margin, and operated as the market itself.
• CFTC enforcement against unregistered platforms (2020–2025): The Commission has consistently pursued entities that operate trading venues, hold customer collateral, or exercise control over order execution without registration. The common thread is functional intermediation—the entity inserts itself into the transaction chain.

Phantom’s feature, by contrast, sits upstream of the transaction. It provides access to a regulated market but does not operate, control, or intermediate within that market. The CFTC’s position recognizes this architectural distinction.

Where Are the Boundaries?

Practitioners should be cautious about extrapolating this position too broadly. Several factors could push a wallet or interface from passive technology into regulated brokerage territory:

Revenue model

Transaction-based compensation is a significant indicator of broker activity under both CFTC and SEC frameworks. If a wallet earns commissions, per-trade fees, or referral payments tied to derivatives volume, regulators may view this as evidence that the wallet is “in the business” of effecting transactions. A flat subscription or software licensing fee presents less risk than a per-trade revenue model. See 17 C.F.R. § 1.3 (defining introducing broker by reference to solicitation and order acceptance).

Curation and preferential routing

A wallet that selects which brokers users can access, negotiates preferential terms with specific venues, or applies algorithmic order routing that exercises discretion over execution venue or timing may cross the line from passive display to active intermediation.

Marketing and solicitation

Actively marketing the derivatives feature—particularly with emphasis on potential returns, leverage ratios, or specific trading strategies—could constitute solicitation under the CEA. The distinction between “our wallet connects to derivatives markets” and “trade 50x leverage through our wallet” is legally significant.

Bundled services

If the wallet pairs derivatives access with advisory services, portfolio management, copy-trading features, or automated trading bots, the combined offering may constitute brokerage even if the interface component alone would be passive.

State-Level and Parallel Federal Considerations

The CFTC’s position addresses federal derivatives regulation only. Wallet providers should also evaluate:

• State money transmitter laws: Depending on how funds flow through the wallet’s derivatives feature, state money transmission licensing obligations under individual state statutes and the Uniform Money Services Act may apply. The CFTC’s determination does not preempt state-level licensing requirements.
• SEC jurisdiction: If any instruments accessible through the feature qualify as security-based swaps or securities, separate registration obligations may arise under the Securities Exchange Act of 1934, 15 U.S.C. § 78a et seq. The jurisdictional boundary between CFTC-regulated swaps and SEC-regulated security-based swaps remains a live issue. See 15 U.S.C. § 78c(a)(68) (defining “security-based swap”).
• FinCEN obligations: If the wallet’s derivatives feature involves the transmission of value—even to facilitate margin deposits—FinCEN money services business (“MSB”) registration and Bank Secrecy Act compliance may independently apply. See 31 U.S.C. § 5330; 31 C.F.R. § 1010.100(ff).

Practical Implications

• For wallet providers: This decision provides a framework—but not a safe harbor—for integrating derivatives access. The key design principle is clear: maintain genuine passivity. No solicitation, no discretion, no custody of margin funds, no counterparty role. Document your architecture thoroughly.
• For CFTC-registered brokers: Expect increased retail volume through wallet integrations. Ensure your compliance programs—KYC/AML, risk disclosures, suitability (where applicable), and large trader reporting—account for users onboarded through third-party wallet interfaces.
• For DeFi protocols: This position favors interfaces that route users to registered intermediaries. Protocols offering direct, unregistered derivatives trading to US users (the Ooki DAO model) remain exposed to enforcement action.
• For compliance counsel: Advise clients to map their specific feature architecture against the passive interface criteria on a function-by-function basis. Consider proactively seeking CFTC no-action relief rather than relying on the Phantom-specific determination.

What to Do Now

1. Obtain and review the full CFTC guidance document once published. Identify the specific parameters the CFTC relied on and whether any conditions or limitations were imposed on its determination.
2. Audit your product architecture. Map every function of your wallet’s derivatives feature against the passive interface criteria. Pay particular attention to order routing logic, fee structures, and data flows involving customer funds.
3. Evaluate your revenue model. If you earn transaction-based fees from derivatives activity, consult CFTC counsel on whether this constitutes introducing broker activity.
4. Assess multi-regulator exposure. Do not treat the CFTC’s position as resolving SEC, FinCEN, or state-level obligations. Conduct a parallel analysis under each applicable regime.
5. Consider seeking independent relief. If your architecture differs from Phantom’s in any material respect, consider requesting your own no-action or interpretive guidance from the CFTC’s Division of Market Oversight.

Conclusion

The CFTC’s decision not to pursue broker registration against Phantom represents a meaningful step toward regulatory clarity in the crypto derivatives space. By recognizing that a passive software interface routing users to registered brokers does not itself constitute brokerage under the CEA, the CFTC has provided a workable—if narrow—framework for wallet providers expanding into derivatives access.

The operative word is narrow. This determination is fact-specific, tied to the particular design of Phantom’s proposed feature. It does not exempt wallet providers from registration generally, does not address SEC or state-level obligations, and does not apply to wallets that exercise discretion, solicit trades, or hold customer margin. Wallet providers and their counsel should treat this as a starting point for analysis, not a conclusion.

---

This article is for informational and educational purposes only and does not constitute legal advice. Reading this content does not create an attorney-client relationship. Laws and regulations in the cryptocurrency space change rapidly — consult a qualified attorney for advice specific to your situation and jurisdiction. Seth Goettelman is licensed to practice law in Wisconsin and Florida.