a16z has reportedly submitted a comment letter to the U.S. Commodity Futures Trading Commission supporting a regulated U.S. market for computing-power derivatives under the existing Commodity Exchange Act and CFTC rules. The procedural answer is yes: the CFTC already has an established listing framework, but that does not mean any compute futures contract has been cleared to launch.

a16z's argument and the status of the CFTC process

The current report says a16z urged the CFTC to use its existing authority under the Commodity Exchange Act, Part 38, and Part 40 to support computing-power derivatives in the United States. According to the report, a16z argued that exchanges do not need new statutory authority or new pre-listing rules before moving toward cash-settled compute futures.

That procedural argument aligns with the current official framework. In August 2026, the CFTC opened a formal request for comment on compute derivatives under Docket CFTC-2026-1850, seeking views on how derivatives using compute as the underlying asset should be assessed. The agency issued a request for comment, not a compute-specific rule or an approval order for any contract.

CFTC listing guidance states that a designated contract market may list a product through Part 40 self-certification without prior CFTC approval, or seek Commission approval under Part 40.3. Part 38 remains the broader rulebook governing designated contract markets and the contracts they list.

The comment period has already closed, with October 20, 2026 set as the deadline. The latest a16z development therefore matters as a policy and legal argument within an established CFTC consultation, rather than as evidence that the regulator has formally adopted its position.

Why benchmark design is the real listing test

Even if existing rules are sufficient in principle, a compute futures contract would still need to satisfy the substantive requirements for a U.S. regulated listing. Under Part 38 guidance, a designated contract market should list only contracts that are not readily susceptible to manipulation.

This is especially important for cash-settled products. Federal guidance says cash-settlement terms should reflect the underlying cash market, provide a reliable pricing basis, and promote convergence between cash and futures prices. In practice, that places significant weight on the benchmark behind any compute contract: how its price is formed, how transparent the underlying market is, and whether the reference market is robust enough to support settlement.

The current report says a16z supported benchmarks aligned with International Organization of Securities Commissions principles, as well as both fixed-term futures and perpetual contracts. However, the CFTC's August request indicates that some of these issues remain under active review. The agency specifically sought comment on cash-market size and liquidity, manipulation risks, customer protection, and perpetual compute futures.

This is the key distinction for readers asking whether the CFTC “already has authority.” The answer is yes on process, but not for every product design. Existing authority gives exchanges a path to file, but it does not remove the need to show that a specific benchmark and contract structure meet current futures-law standards.

What this means for ICE and any future launch

This does not yet represent a confirmed launch step for U.S. compute futures. A May report said ICE planned GPU computing-power futures with Ornn and described the product as subject to regulatory approval, offering the market a concrete example of where this policy debate could matter.

However, no reviewed filing in the supplied record shows that ICE, CME, or another exchange has completed a Part 40 self-certification, obtained approval, or launched a U.S. computing-power futures product. The a16z intervention therefore strengthens the case for using the existing framework more than it changes the confirmed status of any live contract.

The next meaningful signal would be an actual exchange filing under Part 40 or a published contract specification showing how a compute benchmark, settlement design, and customer safeguards are being presented to the regulator. Until then, this is best understood as an argument over the regulatory path with real market relevance, not a completed listing decision.