CFTC staff clarifies tokenized customer-fund investments and blockchain recordkeeping

CFTC staff has updated its frequently asked questions for registrants and registered entities to address two practical uses of blockchain infrastructure: holding customer-fund investments in tokenized form and using blockchain technology to satisfy recordkeeping duties.[1][2]

The Market Participants Division, Division of Market Oversight and Division of Clearing and Risk issued the 24 September update. Their answers apply the existing framework to new forms of representation and record storage; they are staff guidance, rather than an amendment adding investment categories to the rules.[1]

The March FAQs also addressed matters covered by Staff Letter 25-39 on tokenized collateral and Staff Letter 26-05 on digital assets accepted as margin. That history helps distinguish the September customer-fund and recordkeeping questions from the separate permissions and conditions governing collateral.[1]

Start with the investment and the rights it supplies

A token claiming to represent a Treasury bill, money-market instrument or other permitted investment still raises questions about legal title, redemption, custody, settlement finality, valuation and control. Those features determine whether the tokenised position truly delivers the rights and liquidity associated with the underlying instrument.[1][4]

For a firm implementing the guidance, the first practical question is how the ledger position maps to the legal investment and the correct customer-fund account. Custody and control must support that allocation, while the token’s market and redemption process inform valuation and available liquidity. These are the operational consequences of preserving the existing investment and segregation requirements in tokenized form.[1][4]

A ledger entry must remain usable as a regulatory record

Recordkeeping requires more than an entry surviving on a network. The firm needs a way to retrieve complete, readable records for the required period and produce them when requested. Permissioned access, specialised software and dependence on a provider become part of that retrieval process.[1][2]

Key loss, outages and entries that cannot be overwritten create different continuity and correction problems. The useful control test is whether the firm can recover the record, explain its history and demonstrate the relevant account and transaction information when the usual access path fails. These practical implementation questions should be assessed against the actual FAQ answers and underlying rules.[1][3]

Report an error or submit an update