The CFTC is seeking public input on a potential framework for retail crypto transactions and the markets that facilitate them. With comments due December 14, the notice allows trading platforms, leveraged-product developers, and DeFi builders to explain how their products work—and how future rules should address them.

The next phase of crypto regulation is increasingly about market architecture.

For founders, questions about financing, custody, settlement, and customer control belong alongside questions about the asset itself. A product’s legal analysis needs to account for what happens throughout a transaction: how a customer enters a position, who supplies the financing, where assets are held, and what the customer can actually do with them.

The CFTC’s latest initiative brings those operational questions into focus.

On October 13, 2026, the Federal Register published the Commission’s advance notice of proposed rulemaking concerning Regulation Crypto Asset Transactions, or Regulation CTX, and Regulation Crypto Asset Markets, or Regulation CAM. Comments are due December 14, 2026.

What Is the CFTC Considering?

The initiative has two connected components:

• Regulation CTX would address the scope and treatment of covered retail crypto transactions.

• Regulation CAM would establish a tailored framework for markets facilitating those transactions.

The CFTC describes its objective as developing crypto-specific rules under its existing Commodity Exchange Act authority, including protections against abusive practices and a purpose-built subcategory of designated contract market registration. A designated contract market, or DCM, is a CFTC-regulated exchange.

For businesses evaluating the initiative, it helps to separate two questions.

First, does the product involve a transaction within the relevant statutory framework?

Second, what would a regulated business need to look like to offer that transaction?

The answers may affect product design, partnerships, compliance costs, and the responsibilities assigned to different entities.

The Starting Point: Retail Transactions Involving Leverage or Financing

The underlying statutory provision is section 2(c)(2)(D) of the Commodity Exchange Act.

Subject to exceptions, it covers commodity transactions entered into with, or offered to, customers who are neither eligible contract participants nor eligible commercial entities, where the transactions involve leverage, margin, or specified financing arrangements.

The statute expressly addresses offers, even when a transaction is not entered into. It also includes an exception for contracts of sale resulting in actual delivery within 28 days, or a longer period established by Commission rule.

For product teams, this makes the customer journey a useful starting point for review.

A business should be able to explain:

• who can access the product;

• how leverage or financing becomes available;

• which entity provides or arranges it;

• what the customer purchases;

• where purchased assets and collateral are held; and

• how the customer exits the arrangement.

Those details should be documented together. Reviewing a lending agreement separately from the trading interface may miss how the overall product operates.

Why “Actual Delivery” Matters

Actual delivery is a central issue in the notice.

The CFTC’s preliminary view is that an exchange’s internal book entry does not itself establish actual delivery of a covered crypto transaction. The notice also recognizes that some onchain arrangements may deliver assets despite an outstanding security interest. These are preliminary positions on which the agency is seeking feedback.

For builders, the practical question is what the customer receives beyond a displayed account balance.

Can the customer transfer the asset? Use it outside the platform? Exercise the rights associated with it? What approvals, restrictions, or technical dependencies stand between the customer and those actions?

Consider two hypothetical designs.

In one, a customer sees a purchased asset in an account but must rely on the platform to approve and execute any withdrawal.

In another, the customer receives an asset in a wallet and can use it across applications, while a financing arrangement separately governs collateral and liquidation.

Those examples require their own legal analysis. They also show why a useful rulemaking comment should explain permissions, control, and asset movement with precision.

A transaction diagram may communicate more than a general statement that a product is “onchain.”

Regulation CAM: The Market Behind the Transaction

The contemplated CAM framework addresses trading, clearing, margin, and intermediation. It also considers integrated structures involving exchanges, futures commission merchants, and derivatives clearing organizations.

For founders, these issues belong in business planning.

A platform considering a future regulated model should map which functions it expects to perform itself and which functions it expects partners to provide. That exercise should identify responsibility for customer assets, financing, risk monitoring, liquidations, and operational failures.

Integration also deserves careful attention.

Where related businesses perform several functions, teams should be able to explain how decisions are made, how conflicts are managed, and how customers understand the role of each entity.

These are useful questions to address while a product is being designed. Retrofitting responsibilities after commercial agreements and technical systems are in place can make the work considerably harder.

Why DeFi Builders Should Pay Attention

The notice specifically asks about access to onchain vaults through exchange interfaces and the treatment of onchain delivery.

That creates a concrete opportunity for developers to explain the differences between architectures.

A strong submission could describe:

• what the interface enables;

• which actions occur through smart contracts;

• who can change contract parameters;

• who controls assets at each stage;

• how collateral and liquidation work; and

• what happens when an oracle, network, or other dependency fails.

The explanation should connect each technical feature to its practical consequence for the customer.

For example, identifying an administrator key is only the beginning. A useful submission would explain what that key can change, which safeguards constrain its use, and whether those changes can affect a customer’s ability to move assets.

How This Fits Into the Broader Crypto Regulatory Picture

The CFTC’s initiative should be considered alongside the securities-law questions facing crypto businesses.

For planning purposes, founders should distinguish the analysis of an asset’s issuance and distribution from the analysis of a trading, financing, or custody service built around it. Each requires attention to the relevant activities and parties.

A project may therefore need several connected workstreams: one addressing the asset and its offering, another addressing transactions and market infrastructure, and another addressing customer agreements and operational controls.

Keeping those workstreams coordinated can help identify assumptions that otherwise fall between teams.

What Should Businesses Do Now?

The most useful immediate step is to prepare a clear description of the product as it operates today.

That description should align the technical architecture, customer-facing materials, and contractual arrangements. If the interface promises customer control, the underlying permissions and agreements should support that description.

Businesses considering comments should then identify the specific regulatory question their experience can help answer.

A focused submission might explain a delivery mechanism, compare two custody designs, describe the consequences of a proposed intermediary structure, or recommend a safeguard that addresses a defined risk.

Concrete evidence will make those recommendations easier to assess. Useful supporting material could include transaction diagrams, anonymized operational examples, cost estimates, and descriptions of failure scenarios.

What Happens Next?

This is an advance notice of proposed rulemaking. It seeks input to inform possible future agency action; it does not finalize the contemplated CTX or CAM framework.

For builders, the opportunity is to contribute while the agency is still developing its approach.

Comments should explain how a product works, where customers face risk, and how a workable regulatory framework could address that risk. The strongest submissions will give the CFTC enough detail to evaluate both the proposed approach and practical alternatives.

Learn More

This blog post is for informational purposes only and is not legal advice. Please consult with a Launch Legal attorney regarding your specific situation.