CFTC Staff Clarifies Tokenized Customer-Fund Investments and Blockchain Records
Tokenization does not expand the list of permitted customer-fund investments, while onchain records can satisfy existing rules if firms preserve authenticity, reliability and production controls.
CFTC staff updated its crypto and blockchain FAQs on September 24 to address two operational questions for derivatives firms: when customer funds may be invested in tokenized instruments, and when blockchain records can satisfy regulatory recordkeeping duties.
The update does not amend Commission regulations or create new enforceable rights. It records views of staff in the Market Participants Division, Division of Market Oversight and Division of Clearing and Risk, and the document says those views do not necessarily represent the Commission. CFTC.
Tokenization does not change eligibility
A futures commission merchant or derivatives clearing organization may invest customer funds in a tokenized form of an instrument only when the underlying asset is already permitted under CFTC Regulation 1.25, according to the new FAQ 12.
The tokenized version must give its holder legal and economic rights that are the same as, or functionally equivalent to, the rights attached to the traditional form. It must also satisfy the existing limits on liquidity, concentration, time to maturity and instrument features and be held with an acceptable depository.
For an eligible government money-market fund, staff also expects the FCM or DCO to obtain the required written acknowledgment from the custodian. Putting fund shares or a Treasury exposure on a distributed ledger does not remove the custody and customer-protection controls that apply to the underlying investment.
This form-over-substance boundary is the useful market signal. Tokenization can change issuance, transfer and recordkeeping mechanics, but it does not convert an ineligible asset into an eligible customer-fund investment.
Payment stablecoins remain outside Regulation 1.25
The FAQ separately says an FCM may not invest customer funds in payment stablecoins. The staff no-action position governing certain crypto assets used as margin does not change the permitted-investment list in Regulation 1.25.
That distinction prevents three different uses from being conflated. An FCM may hold certain customer crypto assets as margin under the cited no-action conditions; it may deposit its own qualifying payment stablecoins as residual interest subject to capital treatment; and it may invest customer funds only in instruments Regulation 1.25 permits. The September update addresses the third category through tokenized forms of existing instruments.
The CFTC's examples involving tokenized money-market fund shares therefore do not amount to a general approval of stablecoins as customer-fund investments.
Onchain records can meet existing duties
New FAQ 13 says Regulation 1.31 is technology-neutral. A regulated records entity can create and maintain records on a blockchain if it fully satisfies the rule, including systems and controls that ensure authenticity and reliability and the ability to produce records for inspection.
FAQ 14 applies the same approach to swap-data records under Regulation 45.2 for swap execution facilities, designated contract markets, clearing organizations, swap dealers, major swap participants and covered counterparties. Using a blockchain does not displace the substantive reporting and retention duties incorporated by those rules.
The practical test is the firm's control environment, not whether a record is called onchain. A distributed ledger may improve integrity or shared access, but the regulated entity remains responsible for production, retention and risk-management procedures.
No automatic offchain copy, but an outage plan is required
Staff says it would not object solely because a covered entity chose not to maintain a separate offchain version of its records. That is not permission to depend on an inaccessible network or block explorer.
If a firm uses a public permissionless blockchain, it should maintain systems and controls that can retain and produce records during an emergency, network outage or block-explorer failure. The same operational principle applies to any design: the Commission must be able to inspect the required record when the primary technology is unavailable.
The next evidence to watch is whether the Commission adopts binding amendments or individual firms disclose compliant production systems. The September FAQs clarify how staff reads existing rules; they do not approve a particular blockchain, tokenized fund or recordkeeping vendor.