No positions in the markets we measure BY 07:30 ET
CCIR Compute Credit
Index Research
Research · monitor · updated 2026-11-06 · docket CFTC-2026-1850

Compute Derivatives at the CFTC

On August 19, 2026 the Commodity Futures Trading Commission (CFTC) asked what a market in compute derivatives and compute futures should look like. It also asked what could be trusted to settle one. Comments closed October 20. This page gathers the letters on the docket and the ones posted publicly outside it, and summarizes what each one asks. For where the letters stand on each question, see our summary of public comments.

The entrance to the Commodity Futures Trading Commission at Three Lafayette Centre, Washington, DC, with the Commission's seal and CFTC sign on the brick wall.
The Commission's entrance at Three Lafayette Centre, Washington, DC, where paper comments are delivered. Photo: G. Edward Johnson, via Wikimedia Commons (CC BY 4.0).
Release9286-26, issued August 19, 2026
Federal Register91 FR 54259, August 21, 2026 (FR Doc. 2026-17163)
DocketCFTC-2026-1850 · RIN 3038-AF77
Comments closedOctober 20, 2026
Questions23, in four topics
VoteChairman Selig in the affirmative; no Commissioner in the negative
Product filingCME: two compute futures (H100 and B200 rental-index contracts), CFTC product records 62544 and 62545 (NYMEX Submission No. 26-370), status Approval Pending. On September 21, 2026 the CFTC extended its review by 45 days, to November 9, 2026, citing “novel or complex issues” and this request for comment. On November 4, 2026, “at the Commission’s request,” NYMEX consented to a further 60-day extension, to January 8, 2027. The consent depends on other registrants “not self-certifying, obtaining Commission approval, or otherwise listing comparable contracts” in that time. If one does, the earlier date controls. CME had announced an October 5, 2026 first trade date.

01 What the CFTC asked about compute derivatives

The request is a set of questions. The Commission states a preliminary understanding and asks the market to correct it with data. The contract class references "the price of access to computing power". Compute, in the notice's words, "has become a multi-hundred-billion-dollar enterprise and is a scarce, capital-intensive commodity".

The underlier it has in mind is rented capacity. In the notice's words:

The commodity underlying a compute futures contract would typically be access to rented compute capacity from hardware the purchaser of such capacity does not own (e.g., the hourly rental price of compute from a B200), though the underlier may be a different type of compute-related commodity, such as access to a stated volume of LLM inference tokens.

The price of that capacity "would likely be derived from a bundle of factors (e.g., provider, region, contract structures)". A market in it would need those variables standardized. That applies "both with respect to the price index used as a settlement reference, and with respect to the standards of compute that is required to be physically delivered".

The Commission expects most contracts to settle in cash. It also describes the cash market it would be settling against. Compute markets "are fragmented and price formation primarily occurs in opaque bilateral transactions, hindering the availability of current and historical price data". Dominant participants "may wield significant pricing power that may lead to manipulability, preferential pricing arrangements, and, in turn, unfair market dynamics". Pricing "can vary dramatically across providers, regions, and contract structures". The Commission's preliminary view is that compute "may not yet exhibit" fungibility, standardization, and sufficient liquidity.

The legal test sits in one paragraph of the notice. A cash-settled contract passes Core Principle 3 only if its settlement price is "reliable, acceptable, publicly available, and timely". The cash market beneath it must be "sufficiently liquid and not itself readily susceptible to manipulation". Question 2(g) asks whether any compute price series meets that standard today. It also asks what the Commission should do if none does.

The Chairman set the sequence the next day, at the first meeting of the Commission's Innovation Advisory Committee: "Our first step was to issue a request for comment on compute markets, which was released earlier this week. From there, we'll take stakeholder feedback into consideration and develop a gold standard regulatory framework for these new commodity markets."

The four topics, and what each one asks:

  • Cash markets (seven questions). How compute trades, in what modes, at what disclosed prices, and whether a listed contract would change how providers post and reserve.
  • Oversight and manipulation (nine questions). What stops a provider moving an index by moving a posted rate or a venue. What surveillance a market would need. Whether a qualifying price series exists.
  • Customer protection (five questions). Anti-money-laundering, retail disclosure, and the risks a contract's terms should name.
  • Perpetual futures (two questions). Whether a perpetual compute contract adds anything a dated contract cannot, and what it risks.

The request primarily addresses exchange listings. Footnote 6 extends it to swap-execution-facility contracts settling to the price of compute, and to physically settled compute swaps. The Commission "particularly encourages commenters to provide empirical and data-driven input".

02 Comment letters

Ninety-seven comment letters are on the docket. The docket copy is the record. Each card gives the filer's own asks, in the filer's own words, with a link to the docket. A letter posted elsewhere is listed apart until it shows on the docket. Remarks to the press and at Commission meetings are in section 03. If you filed a letter or made a statement here and believe we summarized it poorly, email research@ccir.io and we will review it.

DateFilerTypeDocketTopics
2026-10-27 Managed Funds Association Company 0109 Cash markets · oversight · customer protection · perpetuals
2026-10-26 Belief Systems Company 0108 Cash markets · oversight · customer protection · perpetuals
2026-10-22 Stoa Markets Company 0107 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Multicoin Capital Management Company 0106 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Rose Bowlus Law Company 0105 Cash markets · oversight · customer protection · perpetuals
2026-10-20 CoopHive Inc. Company 0104 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Taylor Holland Individual 0102 Cash markets · oversight · customer protection
2026-10-20 Houman Shadab Individual 0101 Cash markets · oversight · customer protection
2026-10-20 Wei Wang Individual 0100 Cash markets · oversight · perpetuals
2026-10-20 Abaxx Technologies Inc. Company 0099 All four
2026-10-20 Andreessen Horowitz Company 0098 Cash markets · oversight · perpetuals
2026-10-20 Kottos AI Company 0097 Cash markets · oversight
2026-10-20 Futures Industry Association Company 0096 Cash markets · oversight
2026-10-20 Dragonfly Digital Management Company 0095 Cash markets · oversight · perpetuals
2026-10-20 DNA Compute Company 0094 All four · footnote 6
2026-10-20 Gemini Space Station Company 0093 Cash markets · oversight · customer protection · perpetuals
2026-10-20 The Compute Index Company 0092 Cash markets · oversight · perpetuals
2026-10-20 PSYCHE Company 0091 Cash markets · oversight · customer protection · perpetuals · footnote 6
2026-10-20 Kalshi Inc. Company 0090 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Squaretower Company 0089 Cash markets · oversight · customer protection
2026-10-20 Simeon Bochev Individual 0088 Cash markets · oversight · customer protection · states that Q2, 2, 2 and perpetuals are outside it
2026-10-20 Stark Executive Advisory Company 0087 Cash markets · oversight
2026-10-19 ICX Global Company 0085 Cash markets · oversight · customer protection · perpetuals
2026-10-20 QCX LLC d/b/a Polymarket US Company 0084 All four
2026-10-20 Nodal Exchange Company 0083 Cash markets · oversight
2026-10-20 Better Markets Company 0082 Cash markets · customer protection · perpetuals
2026-10-20 Federico M. Bandi and Yinan Su Individual 0081 Cash markets · oversight
2026-10-20 CME Group Inc. Company 0080 Cash markets and oversight
2026-10-19 Fullview Company 0079 All four
2026-10-20 Paradigm Operations LP Company 0078 Cash markets · oversight · customer protection · perpetuals
2026-10-20 PMEX Markets Company 0077 Cash markets · oversight · customer protection · perpetuals
2026-10-20 OrchestraOS Company 0076 Cash markets · oversight
2026-10-20 Intercontinental Exchange Company 0075 Cash markets · oversight
2026-10-19 DRW Holdings Company 0074 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Vast.ai Inc. Company 0073 Cash markets · oversight
2026-10-20 PTG Company 0072 Cash markets · oversight · perpetuals
2026-10-14 Andrew G. Huff Company 0071 Cash markets · oversight · customer protection · perpetuals
2026-10-20 AI Compute Markets Pty Limited Company 0070 Cash markets · oversight · perpetuals
2026-10-20 Hydra Host Company 0069 Cash markets · oversight
2026-10-20 OCX Group Company 0068 Cash markets · oversight
2026-10-19 The Digital Chamber Company 0067 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Solutions by Jewel Company 0066 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Crypto Council for Innovation and its Digital Energy Council Company 0065 Cash markets · perpetuals
2026-10-20 Silicon Data Company 0064 Cash markets · oversight
2026-10-20 Hyperliquid Policy Center Company 0063 Cash markets · oversight · customer protection · perpetuals
2026-10-20 Lida Liberopoulou Company 0060 Cash markets · oversight
2026-10-20 INFEREXUS Company 0059 Cash markets · oversight · customer protection · perpetuals
2026-10-19 Ornn AI Company 0058 Cash markets · oversight · perpetuals
2026-10-19 Simeon Bochev Individual 0057 All four
2026-10-19 Steven Skinner Company 0056 Cash markets · oversight · customer protection · perpetuals
2026-10-19 Jump Trading Group Company 0055 Cash markets · oversight · perpetuals · swaps
2026-10-17 CCE Company 0054 All four
2026-10-19 Clarke Index Company 0053 Cash markets · oversight
2026-10-19 InfraSight Software Corporation Company 0051 Cash markets · oversight
2026-10-19 Hyperbolic Labs Company 0050 Cash markets · oversight · customer protection · perpetuals
2026-10-19 De Silva Law Offices Company 0049 Cash markets · oversight · customer protection · perpetuals · footnote 6
2026-10-20 Fiftyrivers Company 0048 Cash markets · oversight · customer protection · perpetuals
2026-10-18 Mercatus AI Inc. Company 0047 Cash markets · oversight
2026-10-18 Babbage LTD Company 0046 Cash markets · oversight · customer protection
2026-10-17 Dartmouth Advisory Partners Inc. Company 0045 Cash markets · oversight · customer protection · perpetuals
2026-10-16 Voltry Company 0044 Cash markets
2026-10-16 Trevor Love Company 0043 Cash markets · oversight · customer protection · perpetuals
2026-10-16 Architect Financial Technologies Company 0042 All four
2026-10-15 Hedge Quantitative Research LLC Company 0041 Cash markets · oversight · customer protection · perpetuals
2026-10-14 Lee S. Dryburgh Company 0040 Cash markets · oversight
2026-10-13 Voltry Company 0039 Cash markets · oversight
2026-09-28 Samsung Next Fund LLC Company 0038 Cash markets · oversight
2026-10-13 Submitter listed as "Nico Company 0037 Cash markets · oversight
2026-10-12 Redr Labs Company 0036 Cash markets · oversight · customer protection
2026-10-12 Ola Ologunde Company 0035 Cash markets · oversight · customer protection · perpetuals
2026-10-10 Alec Snelling Company 0033 All four
2026-10-07 1791 Technologies LLC Company 0032 Cash markets · oversight
2026-10-06 TCX Company 0031 Oversight · term structure
2026-10-05 Ömer Demirel Individual 0030 Cash markets · oversight
2026-10-04 Submitter listed as "Grok Company 0029 All four
2026-10-04 FastGPU Company 0028 Cash markets · pricing methodologies
2026-10-03 Persistence Analytics Group LLC Company 0027 Cash markets · oversight
2026-10-02 NativX Company 0026 All four
2026-10-02 GPU Economy Company 0025 Cash markets · pricing methodologies
2026-09-24 OneChronos Company 0024 Cash markets · pricing methodologies
2026-09-29 Douro Labs LLC Company 0023 All four
2026-09-29 Dr Evelyse Carvalho Ribas Company 0022 Cash markets · oversight · customer protection · perpetuals
2026-09-25 Hivemind Capital Partners Company 0021 Cash markets · oversight · term structure · settlement and national security
2026-09-28 Vandermolen Power Limited Company 0020 All four
2026-09-25 Compute Capital Company 0018 Cash markets · oversight · customer protection · perpetuals
2026-09-24 VeloxVFX LLC Company 0016 All four
2026-09-10 Balthasar Issa Individual 0014 All four, answered question by question
2026-09-22 Persistence Analytics Group LLC Company 0013 Cash markets · oversight
2026-09-15 AI Compute Markets Pty Limited Company 0011 All four, answered question by question
2026-09-15 Capital Markets & Technology Partners Company 0010 Cash markets · index methodology and oversight · perpetual futures
2026-09-11 Steven Singleton Individual 0008 Oversight · customer protection · perpetual futures
2026-09-07 Li Li Individual 0007 Cash markets · oversight · customer protection
2026-09-04 Animica Labs Company 0006 Cash markets · oversight
2026-09-01 Setara Financial Corp Company 0005 All four
2026-08-24 Anonymous Anonymous 0004 Oversight
2026-08-24 Anonymous Anonymous 0003 Cash markets · oversight · customer protection
2026-08-21 Michael Ravnitzky Individual 0002 All four

Filed on the docket 97

Docket CFTC-2026-1850-0109 2026-10-27 Managed Funds Association (Jennifer W. Han, Chief Legal Officer & Head of Regulatory Affairs)
Comment letter, 7 pages · regulations.gov · received Oct 28, posted Oct 30 · topics: Cash markets · oversight · customer protection · perpetuals (not numbered; perpetuals in footnote 3)
  • The Commission "should allow the cash and derivatives markets to develop together under its existing principles-based framework."
  • "Requiring a single definition of “compute” at the outset could unnecessarily inhibit useful innovation."
All 8 asks
  • A DCM listing a cash-settled contract "should explain the nature and hierarchy of the inputs used to calculate the benchmark, including the extent to which it relies on executed transactions, firm bids or offers, posted rates, or other data."
  • Benchmark governance should include "independent verification and auditability, appropriate recordkeeping and regulatory access, and credible fallback and cessation procedures." The Commission should set principles "without endorsing a particular exchange, benchmark administrator, data source, or product."
  • "Information-sharing arrangements with relevant compute venues, capacity providers, benchmark administrators, and data contributors may be appropriate where those entities supply material inputs to settlement."
  • For capital providers financing GPU infrastructure: "Even before liquidity supports a full hedge, a transparent forward curve extending beyond the front months could provide an independent reference for underwriting and collateral valuation."
  • The Commission "should avoid treating limited historical data as a permanent obstacle to listing when prudent risk controls can address the uncertainty."
  • On perpetuals: "These considerations warrant careful, product-specific review, but do not support a categorical presumption against perpetual compute derivatives."

MFA "represents the global alternative asset management industry." It has "more than 180 fund manager members, including traditional hedge funds, private credit funds, and hybrid funds." It writes that "MFA supports the responsible introduction and development of compute derivatives." The letter names no compute index, administrator, venue or provider, and cites no other comment on this docket. Signed by Jennifer W. Han, Chief Legal Officer & Head of Regulatory Affairs, with copies to Chairman Selig and DJ Hennes, Acting Director of the Division of Market Oversight. The letter is dated October 27.

Docket CFTC-2026-1850-0108 2026-10-26 Belief Systems (True Craft Ventures LLC; James Stewart, Founder)
Comment letter, 6 pages · regulations.gov · received Oct 26, posted Oct 26 · topics: Cash markets (Q1(c)) · oversight (Q2(a)-2(d), 2(i)) · customer protection (Q3(c)) · perpetuals (Q4(b))
  • "Compute derivatives can be listed under the existing Core Principles and the Appendix C Guidance. We see no need for a new rule."
  • On event contracts: "Contract terms should also state the precision of the index used for settlement and what happens when the index equals the strike."
All 8 asks
  • Showing volume, open interest, spread and depth beside a curve built from event-contract prices "would let users weigh each point. We suggest the Commission recognize this as good practice, not a requirement."
  • "A compute methodology should say where provider-posted rates fall in that order and why. It should also measure contributor concentration in the settlement window and explain why its controls are adequate at that level."
  • Each settlement value could carry a short record of how it was formed. "The DCM and the Commission would see exact figures. Because exact shares can reveal confidential commercial terms, the public would see ranges."
  • For perpetuals: "Contract terms should state how often the index is sampled for funding, which inputs count, and what happens to funding when inputs are stale."
  • "We suggest the Commission say that, for compute indices, changes to the input hierarchy, contributor rules, fallbacks, and stale-input handling affect the pricing basis and require certification."
  • On pinned contract months: "A DCM's agreement with the administrator should require that, or name a fallback in advance."

Belief Systems "is a benchmark administrator for prediction markets." It publishes indices, a volatility measure and market-quality grades derived from prediction-market prices. It states: "We do not publish a compute index and have no compute market data." Prediction-market venues, "including some that have commented on this Request, may be licensees or commercial partners." It does "not ask the Commission to approve, designate, or endorse any index, administrator, or venue, including us." The letter names no compute index, venue or provider. It cites its August 2026 comment to the SEC on Novel ETFs, the IOSCO benchmark principles and Part 40. It offers to brief staff, including the Innovation Task Force. Signed by James Stewart, Founder. The letter is dated October 26.

Docket CFTC-2026-1850-0107 2026-10-22 Stoa Markets, Inc. (Berat Celik, Chief Executive Officer)
Comment letter, 9 pages · regulations.gov · received Oct 26, posted Oct 26 · topics: Cash markets (Q1(e), 1(g)) · oversight (Q2(b), 2(c), 2(f)-2(i)) · customer protection (Q3(b)-3(c)) · perpetuals
  • Look for the terms of rental-settled contracts, and any risk disclosure, "to state that the contract references the price of compute hours and not the value of the hardware, and to identify residual-value risk as distinct from rental-rate risk."
  • "Where a submission presents a rental-settled contract as a hedge of GPU collateral, fleet value or residual value, look for evidence of how the reference index has moved with hardware prices for the same GPU class, or a statement that no such evidence exists."
All 6 asks
  • "Consider accelerator hardware as a distinct compute-related commodity and assess any submitted contract referencing its price under the existing Core Principles and Parts 38 and 40."
  • A methodology "should give firm, time-bound commitments priority over posted prices, treat comparable and recent executed transactions as the strongest evidence, and disclose with each determination the indicative share of each type of input on which it rests."
  • Where a contract or its index specifies geography, "it should also specify whether the capacity behind the rate is subject to export-license conditions or end-user restrictions on who may use it."
  • Stoa "would welcome the opportunity to meet with staff of the Division of Market Oversight and to provide aggregated, de-identified hardware price data."

Stoa "operates an institutional request-for-quote marketplace on which GPU servers and racks are quoted and sold for physical delivery." Its interest "is commercial" and includes "developing hardware price data, valuation analytics and price benchmarks." It is "not registered with the Commission in any capacity." It does "not ask the Commission to adopt new rules, to delay the contracts now under review, or to prefer any index." It does "not object to perpetual contracts in principle" and takes "no position on retail access." It cites the NYMEX Silicon Data submission, the ICE and Ornn and ICE and NATIVX announcements, and other comments on this docket by document ID. Among them are Architect, Polymarket US, DRW, DNA Compute, Compute Capital, Bandi and Su, FIA, Hydra Host, Clarke Index and CoopHive. It compares Baltic freight futures and vessel valuations, LME warrants and aircraft appraisal. Signed by Berat Celik, Chief Executive Officer. The letter is dated October 22.

Docket CFTC-2026-1850-0106 2026-10-20 Multicoin Capital Management, LLC (Gregory E. Xethalis, General Counsel)
Comment letter, 12 pages · regulations.gov · received Oct 23, posted Oct 23 · topics: Cash markets · oversight · customer protection · perpetuals (Q4(a)-4(b) numbered)
  • The Commission should "state expressly that it welcomes physically settled compute futures, and the commercial physical markets that support them, alongside cash-settled contracts."
  • Confirm "that access to compute capacity is an exempt commodity, that dedicated reserved capacity is a nonfinancial commodity."
All 7 asks
  • Confirm that a firm that "procures, certifies, and provisions compute capacity as principal" and "assumes delivery obligations" may qualify as a “merchant handling the commodity.”
  • Confirm "that physically settled options on compute capacity, including stand-alone renewal and expansion options, entered into by commercial parties may rely on the trade option exemption, subject to its conditions."
  • Confirm "that the use of blockchain-based records or tokenized capacity receipts does not, by itself, disqualify a transaction from the forward exclusion or a contract from listing."
  • "Perpetual contracts should not be deferred, and their funding mechanisms should be anchored, where possible, in physical transactions."
  • It joins commenters who say Part 40 procedures, "including self-certification, are sufficient for dated compute contracts." A DCM can meet Core Principle 4 "through an information-sharing arrangement with the administrator of a settlement index rather than with every provider whose data enters the index."

Multicoin "is an SEC-registered investment adviser, founded in 2017." It writes "as an investor." It has "invested in decentralized compute networks and marketplaces for several years." It expects "to allocate capital to the venues, intermediaries, and infrastructure that serve this market." It takes "no position on any particular index or venue." It cites other comments on this docket by document ID. Among them are Architect, The Digital Chamber, OneChronos, Paradigm and Andromeda, Kalshi, Polymarket, a16z, DRW, Jump, PMEX, DNA Compute, Better Markets, Dragonfly and Shadab. It compares two published H100 rates: Hyperstack at $3.20 per GPU-hour on demand and AWS Capacity Blocks at $5.970 per accelerator-hour. It also cites CoreWeave financing releases, a partner's October 8 post "Compute Capital Markets," electricity locational pricing and the COMEX aluminum Midwest premium contract. Signed by Gregory E. Xethalis, General Counsel; Daniel Leonardo, Deputy General Counsel and Chief Compliance Officer; and Jay Stolkin, Deputy General Counsel. The letter is dated October 20.

Docket CFTC-2026-1850-0105 2026-10-20 Rose Bowlus Law, APC (Dr. Tripti Prasad Thakur)
Comment letter, 4 pages, with six recommendations · regulations.gov · received Oct 20, posted Oct 23 · topics: Cash markets (Q1(a), 1(c), 1(f), 1(g)) · oversight (Q2(a), 2(b), 2(d), 2(e)) · customer protection (Q3(a)-3(d)) · perpetuals (Q4(a)-4(b))
  • "Clearly define what is being traded. Not all computing power is interchangeable, so contracts should identify exactly what is being priced."
  • For on-demand, interruptible and reserved capacity: "We recommend separate contract series for these arrangements rather than combining them in one price."
All 8 asks
  • "Use actual transactions as the main source for its settlement price, with posted or quoted prices used only under disclosed fallback rules."
  • "The Commission should not permit a contract to settle to a price that cannot be meaningfully verified or monitored."
  • An exchange may get contributor information "through an agreement with an independent index administrator, rather than through a separate agreement with every provider."
  • For limits, an exchange "should generally exclude capacity already committed to long-term contracts unless there is evidence that such capacity regularly returns to the short-term market."
  • "Perpetual contracts, which do not have a fixed expiration date, should come later."
  • For initial listings: "we encourage the Commission to publish a concise list of the supporting evidence it expects."

RBL "is a boutique business law firm with offices in Rancho Santa Fe and Burlingame, California." It comments "rather than on behalf of any particular client." It states: "We support the development of a regulated market that helps businesses manage changes in the cost of computing power." It does "not recommend changing the existing routes for listing a new futures contract." The letter names no index, venue or provider. It cites Core Principles 3, 4 and 5, Appendix C and the June 2026 policy statement on perpetual contracts.

Docket CFTC-2026-1850-0104 2026-10-20 CoopHive Inc., dba Arkhai (Levi Rybalov, Founder and CEO)
Comment letter, 11 pages, with six recommendations · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a)-1(g)) · oversight (Q2(a)-2(i)) · customer protection (Q3(b)-3(d)) · perpetuals (Q4(b))
  • "Define the measurement and its use: specify the population, rights, units, timing and how the derivative uses the index."
  • "Assess incentives and conflicts: include coalitions of independent firms, administrators, verifiers and combined exposure across physical and financial contracts."
All 7 asks
  • "Enable independent review of inputs and decisions: identify lawful, timely access to necessary records for every source of index inputs."
  • State "testable limits: under specified contributor powers, input ranges and reporting assumptions, how far can an individual or coalition move the index, at what cost, and how quickly can that be detected or corrected?"
  • Where evidence on incentives is insufficient: "limit decisions by parties with conflicts of interest, change the design or avoid new reliance on the index for that purpose until sufficient evidence is available."
  • "Compensate contributors for independently checked reporting coverage, rather than price direction or raw volume."
  • "The recommendation is to demonstrate assurance properties, not adopt a mandatory technology stack."

"Arkhai builds programmable markets for agentic economies, starting with compute." The filer is CoopHive Inc., doing business as Arkhai. The submission "draws on research in distributed computing, game theory, and agentic systems." Its recommendations "are contract-specific, not a general position on listing compute derivatives." It offers "conceptual analysis, not a completed audit, executed simulations or evidence that a particular index is fit for use." Its attack mechanisms "are hypothetical, not allegations." The letter names no index, venue or provider. It cites Duffie and Dworczak, “Robust Benchmark Design” (2021), and a FERC surveillance overview. Its assurance table cites FIPS 186-5, RFC 9162, RFC 9334 and NIST PEC.

Docket CFTC-2026-1850-0102 2026-10-20 Taylor Holland
Comment letter, 5 pages, with one chart · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a)-1(c), 1(e), 1(f)) · oversight (Q2(a), 2(d), 2(e), 2(g)) · customer protection (Q3(c), 3(d))
  • On Questions 3(c) and 3(d): "Cash settled compute futures based on an index should disclose, in addition to index data sources, calculation methodology, and price history, the index’s limitations and reasons it may not fully proxy and converge to compute’s underlying economic cost."
  • Among the attributes of a well-constructed index: "Inclusion of a wide set of anonymized private, nonpublic transaction data."
All 6 asks
  • "Published aggregated statistics about the mix of transactions that underpin the index, including portions that are on-demand, RI, location, and detailing various tenors and origination dates."
  • "An appropriate algorithm to extricate a one-month price from the many RIs providing compute that month."
  • "A futures market characterized by open access with appropriately low barriers to entry."
  • The Commission’s anti-fraud and anti-manipulation authority "would be aided by guardrails on transparency into bilateral procurement transactions and provision of data to index providers."

The filer has "spent my career in Silicon Valley as a consumer of computing infrastructure, including running one of the first “compute trading desks” at Heroku nearly a decade ago." The letter adds "deep experience in the ensuing years at large infrastructure providers including Microsoft and Meta." No organization or title is given. It states that "the top three providers collectively account for approximately 63% of global cloud infrastructure revenue." It includes a chart of "three “H100” GPU indices, names redacted," normalized on August 4, 2025. It cites the AI Action Plan and Executive Order 14179.

Docket CFTC-2026-1850-0101 2026-10-20 Houman Shadab, in his individual capacity (Fellow, Stanford CodeX; Co-founder, ICME Labs)
Comment letter, 21 pages, with three figures and an appendix · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(c), 1(d), 1(e)) · oversight (Q2(a)-2(e), 2(g)-2(i)) · customer protection (Q3(d), 3(e))
  • On Question 1(c), "the question should turn on whether the data can be made verifiable." It adds: "Non-public data is therefore not disqualifying under existing guidance. Unverifiable data should be."
  • State that "cryptographic attestations and proofs may form part of a DCM’s record: under Core Principle 3, as evidence supporting index-input eligibility, methodology execution, and delivery terms."
All 7 asks
  • Describe an acceptable compute settlement series in outcome terms, including "priority to bona fide executed transactions over posted rates where transactions suffice."
  • "Expect contract terms to identify the operative version of any settlement methodology," and "encourage administrators to publish a verifiable proof of each settlement computation alongside the price."
  • Clarify that the DCM's information-sharing arrangement with an index administrator "may use layered access," with "source transaction records and supporting identity and affiliation data retained and promptly available to the DCM, and through it the Commission, on request."
  • "Write physical-delivery standards so that attested delivery records may form part of a DCM’s demonstration under the quality, delivery-instrument, and inspection provisions of appendix C."
  • "Set outcome standards, chiefly verifiability by a party without access to the raw data, rather than prescribing particular technologies."

Submitted "in my individual capacity." Shadab taught law at New York Law School for 14 years and is now "a Fellow at Stanford CodeX." He is "a co-founder of ICME Labs (icme.io), a company that builds cryptographic verification tools for AI agents." He states: "I therefore have a commercial interest in verification technology being usable in regulated markets." "The letter recommends no vendor, product, or specific technology." It names NYMEX Submission No. 26-370 and the Silicon Data methodology pages. In them it found "no description of attestation or audit of contributor inputs." It cites comments by FastGPU, Hyperbolic, Silicon Data, Voltry, TCX, InfraSight and others. Precedents include Chicago Board of Trade grain grading, the 2023 London Metal Exchange nickel warrants, IOSCO, LIBOR, ISDAFIX and Regulation Automated Trading. It also cites CME futures on the Nasdaq Veles California Water Index. The same letter is also posted as CFTC-2026-1850-0103, with a different comment-box summary.

Docket CFTC-2026-1850-0100 2026-10-20 Wei Wang, independent researcher
Comment letter, 3 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets · oversight · perpetuals (not numbered)
  • "I respectfully ask the Commission to make “recalculable, auditable, with published fallback settlement rules” an explicit listing precondition for compute futures contracts."
  • "Methodology and raw panel data must be public and independently recalculable." That means "the panel composition, segment weights, and the calculation code or specification sufficient for a third party to reproduce the index from public sources."
All 7 asks
  • The administrator "should publish, per settlement, the share of the target market represented, the number of contributing quotes, and the publication-success rate."
  • "The contract must specify which vintage of the index is final for settlement (e.g., T+1 revision policy)."
  • "Executed prices only. The index should weight only consummated transactions, not indicative listings."
  • "Contributors affiliated with parties holding positions above a threshold should be disclosed; persistent, directionally biased contributors should be down-weighted or excluded."
  • For perpetual contracts, "funding-rate caps or automatic pauses when the index is stale beyond that bound."

Signed as an "Independent researcher." The research "focuses on the economics of compute and energy markets, including independent measurement of GPU rental-price index data sources." The letter states no affiliation. It says Silicon Data "states that its H100/B200 rental indices cover 80%+ of the GPU rental market." It names "DRW / Compute Exchange / Silicon Data" as one corporate group. It names Vast.ai, RunPod, gpuhunt and Scaleway public APIs as public sources. It cites Core Principle 3 and Appendix C to Part 38.

Docket CFTC-2026-1850-0099 2026-10-20 Abaxx Technologies Inc. (Ian H. Forester, Head of Abaxx Labs)
Comment letter, 11 pages, including 2 pages of footnotes · regulations.gov · received Oct 20, posted Oct 21 · topics: All four (all 23 questions, by heading)
  • "We recommend the Commission treat settlement by transfer of a claim ticket as the presumptively appropriate settlement form for compute futures, with cash settlement permitted only where the Appendix C index standard is met."
  • In guidance, "expressly recognize settlement by transfer of a standardized verifiable claim ticket as physical delivery by document of title and as an alternative to cash settlement, with issuer capacity certification and registry-based deliverable-supply data."
All 7 asks
  • On Question 1(g): DCMs "may satisfy the deliverable-supply inquiry for compute contracts using live claim-registry data, supplemented by issuer capacity certification."
  • It agrees "that a cash-settled compute contract should not be listed until (a) an independently governed, multi-provider benchmark exists and (b) mandatory data sharing (utilization, posted rates, committed capacity) is in place."
  • On Question 2(c), it supports a "minimum monthly transaction count in the settlement population" and a "maximum share of index input attributable to any single contributor (we suggest a 20–30% cap, calibrated to compute's actual concentration)."
  • "We recommend the Commission require DCMs to assess, for any compute contract, the feedback channel between settlement price and automated capacity management, and to consider rate limits on claim redemptions that decouple derivative expiry from instantaneous physical provisioning."
  • For any cash-settled compute contract: "mandatory reporting of bilateral terms (aggregated as necessary), utilization, committed capacity, and posted rates."

The letter does not describe Abaxx's business. It states that "this comment does not ask the Commission to endorse a particular design through the RFC." On perpetual hedges, "The Company takes no position on which hedge structure is appropriate." It copies Abaxx CEO Josh Crumb, Chairman Selig, two advisers to the Chairman and the CFTC Innovation Task Force. The letter cites the W3C Verifiable Credentials Data Model 2.0, ISO/IEC 18013-5, UCC Article 7 and Merrill Lynch v. Curran. It names the CME Group and Silicon Data plan for H100 and B200 rental-index futures on NYMEX. It relies on the Michael Ravnitzky comment (0002) and the parallel RFC on perpetual energy contracts (RIN 3038-AF75).

Docket CFTC-2026-1850-0098 2026-10-20 Andreessen Horowitz (a16z) (Miles Jennings, Head of Policy & General Counsel, a16z crypto; Michele R. Korver, Head of Regulatory, a16z crypto; Jai Ramaswamy, Chief Legal Officer; Scott Walker, Chief Compliance Officer)
Comment letter, 7 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a), 1(e)) · oversight (Q2(a), 2(b), 2(g)) · perpetuals (Q4(a), 4(b))
  • "We encourage the Commission to support multiple benchmark methodologies, provided each demonstrates verifiable resilience against manipulation and adheres to the IOSCO Principles for Financial Benchmarks."
  • "Administrators should give priority to executed, arm’s-length transactions from secondary markets and brokerages." Where posted rates or bids and offers are used as inputs, "their weight should be limited and their sources identified."
All 7 asks
  • "Benchmarks should precisely isolate standardized economic units, such as rental costs per GPU-hour for specific chip families, rather than blending dissimilar hardware tiers into an unrepresentative composite."
  • On perpetuals: "Index succession rules and generation-adjusted compute units may address this, and fixed-date contracts should be listed alongside in any event."
  • "Initiate technical roundtables bringing together hardware manufacturers, cloud platforms, AI lab founders (including startup founders), data center operators, and futures exchanges to establish common nomenclature, standardized metrics, and verification procedures."
  • "The self-certification and approval procedures in Part 40 are sufficient for these products, and new rulemaking is not needed before listing."
  • "Guidance confirming that an IOSCO-aligned, transaction-based settlement index can satisfy Appendix C to Part 38 notwithstanding a predominantly bilateral cash market would be helpful."

"a16z is a venture capital firm that invests in seed, venture, and growth-stage technology companies." It reports "more than $100 billion of regulatory assets under management across multiple funds." Its new "Machine Age Fund" will invest in "all of the computer infrastructure on which AI runs, including chips, memory, networking, and storage." It discloses: "a16z crypto is an investor in Ornn." The letter names the Ornn Compute Price Index (OCPI), administered by Ornn Data LLC, and the plan by Intercontinental Exchange and Ornn, announced in May 2026, to launch GPU compute futures on the OCPI. It cites Platts, Argus and OPIS, power futures, the IOSCO benchmark and oil price reporting agency principles, and the White House AI Action Plan.

Docket CFTC-2026-1850-0097 2026-10-20 Kottos AI, Inc. (Lluís Antoni Jiménez Rugama, Founder)
Comment letter, 3 pages, with a summary in the docket comment box · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(e)(ii), 1(e)(iv), 1(e)(v)) · oversight (Q2(a), 2(c), 2(d), 2(g))
  • "The Commission should distinguish three layers: GPU-hour products, compute indexes, and inference tokens."
  • "I recommend beginning with a narrow open-weight grade, where the checkpoint can be identified and the serving configuration can be specified."
All 7 asks
  • On counting tokens by type: "If a contract combines them, it must fix and publish the weights."
  • For each grade, "a transaction tape should record each request's time, venue, region, quantity by token type, paid price, and delivery outcome."
  • "A contract that references a basket should disclose its components, weights and adjustment rules, so participants can assess the resulting risk."
  • Before listing an inference contract, the DCM "discloses market coverage and contributor concentration, justifies minimum transaction and independent-contributor thresholds, and explains when insufficient data prevents publication of a reliable reference price." "If there are too few eligible transactions, the reference price must be marked unavailable and the contract must specify how settlement proceeds in that situation."
  • "Once the service grade is defined, prices can emerge through RFQs, block trades, or periodic auctions. A continuous order book is not necessary."

Kottos AI "develops inference routing and provider-performance measurement infrastructure." Its "gateway records request usage, timing, outcomes and cost estimates." The founder writes: "I have a commercial interest in this area, Kottos AI does not operate an exchange, and these views are my own." He "spent nine years in high-frequency and electronic trading at Virtu and UBS." The letter names Silicon Data's LLM Token Expenditure Index and Ornn's token indexes. It cites Moonshot AI's K2 Vendor Verifier results for Moonshot, Fireworks, Together and Chutes. It reports its own October 5 latency test of Claude Opus 5.5 on Anthropic's API and AWS Bedrock. It cites FINRA TRACE and comments by Michael Ravnitzky (0002), Silicon Data (0064) and Hydra Host (0069).

Docket CFTC-2026-1850-0096 2026-10-20 Futures Industry Association (Allison Lurton, General Counsel and Chief Legal Officer)
Comment letter, 6 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(f)) · oversight (Q2(a)-2(d), 2(g))
  • FIA "believes strongly that only contracts that can be effectively risk-managed should be listed and cleared."
  • "FIA encourages the Commission to articulate a public standard regarding spot and forward market data and when such data is sufficient to support compliance with Core Principle 3."
All 7 asks
  • "Thinly traded markets may require more robust surveillance and safeguards such as calibrated position accountability levels and real-time monitoring for anomalous price movements."
  • "Provide guidance or otherwise clarify that a DCM listing a cash-settled Compute derivative contract should, where practicable, maintain an information-sharing arrangement with the index administrator."
  • "Provide guidance or otherwise clarify that DCMs should seek to use index administrators for Compute benchmarks that adhere to governance, methodology, conflict-of-interest, and audit standards comparable to the PRA Principles and Financial Benchmark Principles."
  • Address the concern that "Compute providers that administer posted rates" may also supply Compute or contribute observations, and "encourage methodologies that distinguish executed transactions, executable bids and offers, and indicative posted rates."
  • "Consider whether the Commission itself should have a right of access to index input data for Compute benchmarks used to settle listed contracts, as a condition of a DCM’s Core Principle 3 demonstration."

FIA is "the leading trade organization for the futures, options, and cleared derivatives markets globally." Its membership "includes clearing firms, exchanges, clearinghouses, principal traders, asset managers, execution firms, commodity firms, end users," and service firms. The letter names no compute index, venue or provider. It cites the IOSCO Principles for Oil Price Reporting Agencies (2012) and Principles for Financial Benchmarks (2013). It cites CFTC enforcement cases on Argus and Platts indexes, FX benchmarks and LIBOR. It names natural gas (LNG), freight and electricity as index-priced markets. Copies went to Chairman Selig, General Counsel Tyler S. Badgley and Aaron Levine.

Docket CFTC-2026-1850-0095 2026-10-20 Dragonfly Digital Management, LLC (Lindsay Lin, Chief Operating Officer; Rob Hadick, General Partner; Bryan Edelman, Associate General Counsel; Yoon Soo Shin, Associate General Counsel)
Comment letter, 6 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(b)-1(d), 1(e)(ii), 1(e)(iv), 1(g)) · oversight (Q2(a)-2(d)) · perpetuals (Q4(a), 4(b))
  • "Permit DCMs to develop commercially useful contract units, including GPU-hours with hardware and service characteristics necessary for economic comparability, without prescribing a single Commission-wide compute specification."
  • "Treat inference throughput as a separate potential contract class where model choice, version, and measurement protocol can be standardized reliably."
All 7 asks
  • "Treat on-chain leases, bids, and payment records as eligible primary transaction evidence on the same terms as records from brokers, cloud providers, and other venues, subject to validation of execution, economic comparability, and representativeness." It adds: "Do not treat bids or posted prices as executed cash-market transactions."
  • "Do not make a mandatory independent audit or marketplace-wide reconciliation a condition of eligibility."
  • "Do not mandate a uniform minimum number of contributors, source-weight caps, or other fixed quantitative tests for all compute indexes."
  • On provider rates: "do not disqualify a supplier's price solely because the supplier is also a legitimate derivatives hedger."
  • "Permit perpetual compute futures to be proposed under Regulation 40.3 and reviewed on their merits, consistent with the Commission's current policy." It also asks for "a predictable path" for comparable contracts to use Regulation 40.2 self-certification.

"Dragonfly is a global investment firm that invests in cryptocurrency assets, infrastructure, applications, and markets." It "manages approximately $4 billion in assets across multiple funds." Its investments include "blockchain infrastructure, compute markets, and market data." It submits "on its own behalf and not on behalf of any portfolio company." The letter names Akash Network as a marketplace with on-chain orders, provider bids, leases and escrow payments. It cites 17 C.F.R. §§ 38.253 and 38.254. It also cites the Commission's June 2026 policy statement on perpetual contracts and the bitcoin perpetual futures contract permitted in May 2026.

Docket CFTC-2026-1850-0094 2026-10-20 DNA Compute, Inc. (Keith Lambert, Chief Strategy Officer)
Comment letter, 21 pages, with 11 numbered recommendations, plus a docket summary · regulations.gov · received Oct 20, posted Oct 21 · topics: All four (all 23 questions, numbered) · footnote 6
  • "Name the settlement series in the contract terms." For each print: "the effective contributor count, meaning the inverse of the sum of squared contributor weights; the share of inputs that are verified arm's-length executed transactions rather than posted or listed rates."
  • "no restatement of history for contract months with open interest, other than correction of a calculation error or a falsified input within a published correction window with the original value kept."
All 7 asks
  • An administrator "should neither trade the referencing contract nor hold balance-sheet exposure to capacity whose price it publishes."
  • On Question 1(g): "We recommend that the exchange publish V and its method in summary, and set accountability levels and any spot-month limit as a fraction of V/730, for which the Commission's convention of no more than one quarter of estimated deliverable supply is the natural starting point." V is the "month's index-eligible volume."
  • On Question 2(d): "a material input whose records cannot be produced should not enter a settlement price."
  • "Regulation 40.3 review for first-of-kind compute contracts, and a staff advisory that states listing expectations once, for every venue."
  • "We do not ask the Commission to delay approval of any contract." It asks "that the Commission complete the pending review on the record it has built."

"We write as a prospective intermediary." Its futures business, DNA Futures, "is being organized to introduce customer business in exchange-listed compute derivatives through a registered introducing broker." DNA Compute "owns graphics processing units and is developing additional capacity." It would participate "most likely as a seller of price risk." It has "no commercial relationship with any index administrator or exchange referred to in this letter." The letter names NYMEX Submission No. 26-370 (Silicon Data H100 and B200) and the ICE Futures U.S. OCPI H100 and B200 futures (Ornn). It names ICE with NATIVX, Nodal Exchange with Compute Desk, and Architect’s American Innovation Exchange. It also names Polymarket US, Bitget and a ProShares fund filing. It compares Silicon Data and Ornn readings on October 19, 2026. It cites SOFR futures, the ISDA IBOR fallbacks, FERC’s 2003 price index policy statement and the 2018 virtual currency staff advisory. It also cites power, freight and housing futures.

Docket CFTC-2026-1850-0093 2026-10-20 Gemini Space Station, Inc., for Gemini Titan, LLC, Gemini Olympus, LLC and Gemini Galactic Markets, LLC (Andrew R. Beatty, Head of Policy and Senior Regulatory Counsel)
Comment letter, 11 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(b), 1(c), 1(f), 1(g)) · oversight (Q2(a)-2(e), 2(g), 2(i)) · customer protection (Q3(a)-3(d)) · perpetuals (Q4(a), 4(b))
  • "The Commission should not adopt compute-specific numerical thresholds or require that the compute cash market resemble mature commodity markets before contracts may be listed."
  • Asks the Commission to "confirm that the “publicly available” element of the Appendix C Guidance is satisfied where the DCM publishes the final settlement price and the index methodology is public, even if constituent data are licensed or held in confidence."
All 7 asks
  • On Question 1(f), it recommends "(i) a cap on the weight any single contributor or venue may have in the index; (ii) a minimum number of independent contributors; (iii) a preference for executed or binding transactions over indicative posted rates, with posted rates used only where corroborated by transactions."
  • "Gemini does not believe a DCM should be required to maintain an information-sharing arrangement with each compute venue and each capacity provider whose data enters a settlement reference price." It proposes "a single arrangement between the DCM and the index administrator."
  • On Question 2(g): "If no series fully satisfies Appendix C today, the Commission should not conclude that no contract may be listed."
  • Retail protections "should be keyed to the features of the product, such as leverage, funding mechanics, and liquidity, and not to the underlier or to a separate retail regime for compute."
  • "Gemini requests that the Commission confirm that this process is available for perpetual compute contracts and publish the criteria it will apply."

Gemini writes from "the perspective of a registered designated contract market (“DCM”) that would be responsible for applying the Commission’s framework in practice." Its affiliates are Gemini Titan, a registered DCM, and Gemini Olympus, a registered DCO. Gemini Galactic Markets is a broker-dealer that has applied to register as an FCM. Gemini "is actively evaluating the listing of compute-referencing contracts." It "does not participate in compute cash markets and does not expect to administer its own compute reference price." It names no index provider. It cites Kalshi compute forward curves and compute futures announced by CME Group and Intercontinental Exchange. It also cites the IOSCO Benchmark Principles, the May 29, 2026 perpetual contracts policy statement and the AI Action Plan.

Docket CFTC-2026-1850-0092 2026-10-20 The Compute Index, Inc., dba Compute Desk (Andrawes Bahou, Chief Executive Officer)
Comment letter, 11 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(e)) · oversight (Q2(a), 2(b), 2(d), 2(g)) · perpetuals (Q4(a))
  • Asks the Commission "to apply heightened review, rather than self-certification, to any settlement methodology designed or controlled by a firm with significant market-making, proprietary trading or capacity-ownership interests in the contracts or the GPU compute it prices."
  • "Compute Desk cautions against any index whose input data comes from an on-demand compute marketplace, even if the data represents executed transactions."
All 7 asks
  • "Contributors should flag transactions with related parties, and either provide transparency of those transactions or preferably exclude them entirely."
  • On Question 2(g): "Existing retail-scraped on-demand price points (even if based on completed transactions), do not easily meet Appendix C criteria as a referenced price for a cash-settled futures contract." It states that "Compute Desk’s transaction-invoiced bare metal benchmark complies with the criteria in Appendix C(c)(2)."
  • Its conclusion lists "Establishing bare metal hardware as the bulk “crude” physical benchmark" and "Anchoring cash-futures convergence in an EFP framework analogous to energy and power markets."
  • Also "Enforcing information-sharing protocols that provide unmasked counterparty auditability to the DCMs and the Commission."
  • On Question 4(a): perpetual compute futures "will have limited utility to, or success with, natural buyers" of compute. "Fixed-term derivatives align naturally with delivery dates, and loan terms underlying much of the compute purchase and sale patterns."

"Compute Desk provides compute data and benchmark indexes for the GPU (Graphics Processing Unit) compute ecosystem." It "will serve as the index provider for" Architect’s American Innovation Exchange, a registered DCM. The letter describes its own indexes. They "use completed transactions executed by data partners, with counterparties anonymized at source, blended with published neocloud list prices." They focus on "bulk reserved “bare metal” GPU compute." General Index Limited calculates them under the IOSCO Principles for Financial Benchmarks. It states that "No proprietary transaction or listed data is included in the calculation of Compute Desk’s indexes." It also states that it "is not owned by, nor holds any investment by a market-making firm trading or intending to make markets in compute derivatives." The letter names Architect’s ComputeConnect EFP network, Nodal Exchange, NYMEX, ICE, CME and Bloomberg. It cites the FERC staff report on Western markets, the FERC price index policy statement and LIBOR.

Docket CFTC-2026-1850-0091 2026-10-20 PSYCHE (Yifei “Fée-Fée” Yang, Founder)
Comment letter, 25 pages, four numbered requests, with three exhibits (6, 15 and 4 pages) and the 39-page SQCD-1 text · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a)-1(g)) · oversight (Q2(a), 2(b), 2(d), 2(g)-2(i)) · customer protection (Q3(b), 3(c)) · perpetuals (Q4(a)) · footnote 6
  • On Question 3(c): "I suggest the contract terms state what the settlement reference measures, and that basis of this kind is retained by the hedger." Its model text: "The position holder retains the exposure to whether contracted compute is delivered."
  • On Question 2(g): "the enumerated standardization dimensions of that series and its change-control procedure should be described in the contract rules at a level a hedger can read and restate." It adds: "The proprietary normalization model stays proprietary."
All 7 asks
  • On Questions 1(g) and 2(h), the candidate units are "installed nameplate capacity, contracted hours, uncommitted hours, and delivered hours." "A deliverable supply methodology should state which quantity it uses and how that quantity is measured."
  • On footnote 6: a contract that settles by delivery "should be read to include the record by which delivery is established." On Appendix C ¶(b)(2)(i)(G): "Request 4 asks that a physically-settled compute contract’s rules do one or the other, and say which."
  • "One way to meet it is for the rules to settle certification, substitution, objection, figure finality and counterparty measurement."
  • For each delivery interval, a surveillance arrangement would need "the measured quantity, the party or instrument that produced the measurement, the treatment applied to intervals with no measurement, and the date after which the figure does not change."
  • "A physically-settled compute swap listed on such a facility is referred to the same paragraph, and the request applies to it through that cross-reference."

Filed by Yifei Yang, "founder of PSYCHE and author of SQCD-1." It is "submitted in my own name and in the name of PSYCHE." It discloses: "I wrote SQCD-1, and PSYCHE, which publishes it, may offer services built on it." It "asks the Commission to adopt, designate, endorse or require no text, SQCD-1 included." Exhibit 1 quotes the settlement rules of eight electricity markets, including CAISO, ERCOT, MISO, NYISO, PJM and ISO New England. Exhibit 2 reads ten compute agreements filed with the SEC, including those of CoreWeave, Nebius, Applied Digital, HPE and Sharon AI. Exhibit 3 traces one credit-dispute clause across four of them. The letter names the Silicon Data, Ornn OCPI and Compute Desk series, NYMEX, ICE Futures U.S., Nodal Exchange, and Architect's ComputeConnect. It cites CME Degree Days Index futures as a precedent.

Docket CFTC-2026-1850-0090 2026-10-20 Kalshi Inc. (Sudhir Jain, Chief Compliance Officer and Head of Regulatory Affairs)
Comment letter, 13 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets · oversight · customer protection · perpetuals (not numbered)
  • "The Commission should apply these well-established and effective tools, support dated, perpetual, and event contracts, and preserve access for retail participants and commercial hedgers."
  • "The Commission need not define one ubiquitous standard compute unit or product before permitting this important market to develop in the United States."
All 7 asks
  • It states that "eligible executed transactions should normally receive greater weight than untested posted rates." The index "should require a minimum number of contributors and caps on concentration as well as a time- or volume-weighted average over a window, as opposed to a single snapshot."
  • Providers that trade compute futures "should also be subject to position accountability, supported by large-trader reporting that identifies provider-affiliated accounts."
  • These safeguards work "without the need for exchanges to enter an information-sharing agreement with every compute provider, which is likely impracticable and unworkable."
  • "Where permitted under existing requirements, DCMs should be able to use position accountability in place of fixed position limits, particularly during the market’s early development."
  • The Commission "should not impose any compute-specific limitations on retail access to these markets." Existing NFA disclosure and suitability rules "are adequate to address the consumer protection risks associated with exchange-listed compute derivative products."

Kalshi files with its subsidiaries KalshiEX LLC, a designated contract market, and Kalshi Klear LLC, a registered derivatives clearing organization. It calls itself "the leading prediction market in the United States." It was "the first U.S. regulated exchange to offer perpetual contracts on digital commodities." It offers "compute forward curves" for B200, H200 and A100 rental prices. The letter names no compute price index. It cites Bitget's H100 and B200 perpetuals, the Freightos Baltic Index, NYMEX FBX01 futures, ICE Mid-Columbia power futures and CME WTI and Brent futures. It also cites the IOSCO principles, the EU Benchmark Regulation and LIBOR.

Docket CFTC-2026-1850-0089 2026-10-20 Squaretower, Inc. (Mackay Grant, Founder and Chief Executive Officer)
Comment letter, 11 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(e), 1(e)(iii), 1(e)(iv), 1(f)) · oversight (Q2(a)-2(i)) · customer protection (Q3(b)-3(e))
  • On Question 2(c): an index "could initially consider transactions involving at least two eight-GPU nodes (16 GPUs) and up to and including 128 such nodes (1,024 GPUs), subject to appropriate requirements for cluster contiguity."
  • "An index should clearly delineate how payment schedules are compared and what payment terms are assumed." It "should use the actual price after credits, rebates, and other applicable economic concessions."
All 7 asks
  • For prices negotiated alongside equity or financing, "Contributors should disclose these relationships to the index administrator." If the price cannot be assessed separately, "it may be reasonable to exclude the transaction from the settlement index."
  • It states that "market-wide firm quotes from sellers may be a better indication of the market value of the underlying compute."
  • "Exchanges should provide worked examples demonstrating the cash required to maintain a position through various price movements, alongside the eventual gain or loss."
  • "Indices relied on for the financing of compute infrastructure should meet a higher standard than those used solely for the settlement of futures." "Settlement-index standards should be firmly in place before the credit market relies on compute indices."
  • An index "should withhold publication when inputs fall below clearly defined criteria." "Administrators should not include transactions that they or their affiliates facilitate." Fallback rules "should be fixed and published in advance."

Squaretower is a San Francisco startup that "works closely with some of the largest buyers and sellers of compute." It "operates an asset-light execution desk that manages compute portfolios for its clients." In August 2025 its team "developed an H100 price index using vetted U.S.-based compute suppliers." It supported the launch of a compute perpetual futures product, and a footnote states: "This market no longer trades." The letter cites Platts, Argus, Fastmarkets, SemiAnalysis, Gain AM and FERC's 2003 Policy Statement on price indices.

Docket CFTC-2026-1850-0088 2026-10-20 Simeon Bochev (personal capacity)
Appendix C to his comment 0057, 10 pages, with a one-page summary (posted as PDF and PowerPoint) · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a)-1(g)) · oversight (Q2(b)-2(d), 2(f)-2(h)) · customer protection (Q3(a)-3(e)) · states that Q2(a), 2(e), 2(i) and perpetuals (Q4) are outside it
  • "The illustrative contract is a forward on one GB300 NVL72 rack." The price is "Fixed USD per GPU-hour for the whole-rack unit, quoted in $0.001 increments." "No fixed 730-hour multiplier applies; months carry 672, 696, 720 or 744 hours."
  • "The baseline is advance funding with an independent funds agent and evidence-based release to the service-charge creditor. Purchase funds are not available for construction before that trigger."
All 7 asks
  • "The unit is binary. The rack conforms or it fails." "A delivery obligor has no election to pay instead of delivering: a payment cannot restore a missed capacity window."
  • On Questions 1(g) and 2(h): "Measure legally and operationally available capacity by grade, location and delivery window, net of incompatible commitments, maintenance and access constraints." "Report commissioned availability and firm future-build commitments separately and exclude conditional reservations."
  • On Questions 1(b) to 1(e), 2(c), 2(d) and 2(g): "Require attributable records, protected access to the underlying evidence, independent review and governed publication."
  • On Questions 3(a) to 3(d): "Initial participation is proposed for commercial counterparties with verified ability and intent to receive or resupply the capacity."
  • "Settlement prices, exchange market controls, perpetual contracts and hedge effectiveness are not answered by a physical forward."

Appendix C to his October 19 comment (CFTC-2026-1850-0057), filed in a personal capacity. It sets out "a bilateral, physically performed forward purchase of a defined unit of compute for a fixed future service period." He states that it is "a design and an evidence method, not an executed agreement, a futures or swap specification, or an application to list anything." It also states that "nothing here concludes that any statutory forward exclusion applies." It "claims no compliance with or approval under" Appendix C to 17 CFR part 38. It cites IREN's Microsoft GB300 agreement at Childress, NYMEX Submission 26-370 and CFTC staff guidance on facility-use agreements.

Docket CFTC-2026-1850-0087 2026-10-20 Stark Executive Advisory (Isabelle Stark), New York
Comment letter, 5 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets · oversight (not numbered)
  • The reference framework "can establish separate indices or adjustments for hyperscalers and neoclouds."
  • "Independent auditors and regulators must possess the structural capability to reproduce the results completely through either substantive reperformance of cleared transaction data or macro reasonableness testing utilizing analytical procedures."
All 7 asks
  • "Settlement mechanisms are more reliable when anchored to continuous transaction averaging of cleared, cash-settled capital flows."
  • The Commission "could utilize cleared transaction data processed through independent, third-party clearing mechanisms or infrastructure boundaries." Data center operators could "attest to transaction volumes and capacity states" through "lightweight, cryptographic interfaces."
  • "Real-time on-demand rates reflect short-term marginal constraints and could be indexed separately from multi-year enterprise commitments." "Standard basis tables could be published to normalize regional power costs and technical networking topography."
  • For deliverable supply, committed take-or-pay capacity would be deducted. Unencumbered capacity "represents the metric for calculating deliverable market depth and position limits."
  • To check that capacity is online, "transaction inputs could be validated at the hardware layer," using "cryptographically signed silicon metrics (FLOPS, memory bandwidth, and active power draw)."

Signed by Isabelle Stark of Stark Executive Advisory, New York. The letter does not describe the firm or state any interest. It names no index, venue or provider. It cites the move from LIBOR to SOFR, Brent crude quality differentials and locational marginal pricing in wholesale power. It states that multinode training performance on poorly tuned RoCEv2 "can drop by 30% or more due to packet loss."

Docket CFTC-2026-1850-0084 2026-10-20 QCX LLC d/b/a Polymarket US (Nick Rice, Head of Markets)
Comment letter, 11 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: All four (all 23 questions, numbered)
  • States that "no compute-specific rule is needed" and that "a new underlying commodity should not, by itself, turn the ordinary self-certification process into a requirement for Commission approval."
  • The Commission should treat compute derivatives as including "binary and other fully collateralized contracts that settle to a compute price index, not only linear futures."
All 7 asks
  • "The Commission should welcome competition among index publishers rather than designate one." It disagrees with comments 0002 and 0008 that "urged the Commission to hold compute listings."
  • "We ask the Commission to confirm that position limits and accountability levels for compute contracts may be set by reference to manipulation and price-distortion risk rather than by estimating “deliverable” GPU-hours."
  • An index should "specify a minimum number of unaffiliated contributors for each published value and a maximum share of the index weight that any single contributor, together with its affiliates, may account for." Rather than fix these thresholds by rule, "the Commission should expect a DCM to show in its filing which thresholds its chosen index applies and why they are adequate for that market."
  • Encourage DCMs "to include index-administrator personnel, and large capacity providers and buyers, within the scope of their insider-trading surveillance." It adds that "these prohibitions should not prevent capacity providers and buyers from hedging their own exposure."
  • "The Commission should confirm that binary event contracts referencing a compute index are compute derivatives for purposes of any guidance."

Polymarket US is a DCM. Its affiliate Adventure One QSS Inc. operates Polymarket International, which "is not available for trading within the United States." Since February 3, 2026, Polymarket International "has listed cash-settled binary contracts" on daily GPU rental price indices. They "have settled against two index families: those of Silicon Data, which CME Group has since selected for its compute futures, and Ornn." The letter describes Silicon Data, the Ornn Compute Price Index and the Compute Desk indices (with General Index). It names NYMEX, ICE Futures U.S., Architect Financial Technologies and the American Innovation Exchange. Its financing case cites CoreWeave and Nebius facilities and Clifford Chance. It cites Bandi and Su, Argus, the Baltic Exchange and the Kalshi BTCPERP approval. It offers to share settlement data with staff.

Docket CFTC-2026-1850-0083 2026-10-20 Nodal Exchange, LLC (Ken McCracken, General Counsel)
Comment letter, 4 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets · oversight (not numbered)
  • "The existing Core Principles framework and the existing Commission regulations already provide the necessary regulatory oversight, anti-manipulation protection, and standards across all DCM product listings to support compute derivatives."
  • For index-settled products, "the index methodology should be provided showing how it is reflective of the underlying cash market, is not readily susceptible to manipulation, and based on prices that are acceptable, reliable, timely, and publicly available."
All 6 asks
  • "Utilizing benchmark indices from independent third-party index providers is a prudent path to managing the introduction of financially settled compute futures."
  • "A well-constructed index will not give disproportionate weight to quoted prices." It should balance "quoted prices, prices from market-based transactions, and prices from independent bilateral transactions."
  • "It is not necessary, for example, to impose new or novel surveillance requirements on DCMs with respect to compute derivatives."
  • "As the underlying compute market matures and compute index derivatives gain traction, financially settled locational futures are a logical next step."

Nodal Exchange is a DCM "at the forefront of innovation in the electric power, natural gas, and environmental futures markets." It states that it "plans to launch a new suite of GPU compute futures contracts on Nodal Exchange." The footnote to that sentence links to a Nodal Exchange release on launching compute futures with Compute Desk. Its clearinghouse is its wholly owned subsidiary Nodal Clear, a "Subpart C" DCO. "Nodal Exchange is part of EEX Group owned by the European Energy Exchange AG." The letter cites the 2013 IOSCO Principles for Financial Benchmarks and Appendix C to Part 38.

Docket CFTC-2026-1850-0082 2026-10-20 Better Markets, Inc. (Benjamin L. Schiffrin, Director of Securities Policy)
Comment letter, 3 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets · customer protection · perpetuals (not numbered)
  • "The Commission must ensure that compute derivatives contracts are able to be standardized, and are not susceptible to manipulation, before allowing them to trade on a DCM."
  • On the question of parties best positioned to influence the reference price: "The answer is yes." It adds: "The CFTC needs to address this concern before commencing trading."
All 6 asks
  • "Compute derivatives are a worthwhile innovation, but they need to be rolled out carefully."
  • "The Commission should focus on making traditional, fixed-date futures contracts with compute as the underlying commodity workable rather than promoting perpetual futures on compute."
  • The Commission "should ensure that compute derivatives marketed to retail investors include necessary risk disclosures."
  • "To the extent compute derivatives will be engineered for retail participants, the Commission needs investor protection requirements" for those users.

"Better Markets is a non-profit, non-partisan, and independent organization founded in the wake of the 2008 financial crisis to promote the public interest in the financial markets." The letter quotes Dave Friedman's Substack posts, including that Microsoft, Google, Amazon, "and to a lesser extent Oracle and Meta, control the vast majority of deployable capacity." It also cites Peter C. Earle (American Institute for Economic Research), a Cahill client alert and an Investment Executive article. It refers to its own August 26, 2026 letter on 24/7 trading and perpetual contracts.

Docket CFTC-2026-1850-0081 2026-10-20 Federico M. Bandi and Yinan Su, Johns Hopkins University
Comment letter, 15 pages, with a model and references · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets · oversight (not numbered)
  • "Contracts can reference specific configurations, with contracts on new configurations introduced as they become available."
  • "A clearly specified reference, or “par”, service may define the underlying, with transparent price adjustments for deviations from the “par” characteristics."
All 7 asks
  • "A settlement index should be simple and reproducible from verifiable transactions." "Nonbinding indicative quotes should be identified separately and their role in validation and weighting made transparent."
  • Regulators "could use unusually large net, settlement-linked futures exposures as a screening signal for closer scrutiny." In its example, "10,000 GPU-months is a model-based candidate exposure level for enhanced scrutiny, not a validated regulatory safe harbor or a stand-alone surveillance threshold."
  • "Capping very large contributor weights may therefore be useful, moving the weighting toward a more equal allocation."
  • States that "trimming is a reasonable index design choice for limiting manipulation gains from extreme price inputs."
  • "We support transparency enabling market participants to understand precisely which market segment the compute index surveys and measures." This "includes which providers are surveyed, which parts of their rental business enter the index, and how the surveyed observations are used to measure prices in that segment."

Joint comment by two Johns Hopkins University authors. "The Commission cites an earlier version of our paper, (Early) AI Compute Asset Pricing (Bandi and Su, 2026), in its request." The letter provides a revised version. It states: "We emphasize that our objective is not advocacy. Our contribution and interests are technical." Its model uses the 730 GPU-hour unit and business-day averaging in NYMEX Submission 26-370. It states that if futures prices "are mistakenly treated as a general guide to AI infrastructure investment and financing, they could distort credit decisions and amplify the credit cycle." It cites Becker (1968), Duffie and Dworczak (2021), Kumar and Seppi (1992), Zhang (2022), Morris and Shin (2002) and Kiyotaki and Moore (1997).

Docket CFTC-2026-1850-0080 2026-10-20 CME Group Inc. (John Marchese, Senior Managing Director and General Counsel)
Comment letter, 4 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets and oversight (Core Principles 3 and 4, not numbered)
  • "CME believes it is an appropriate, if not necessary, time for compute derivatives contracts to be offered to the industry for risk management and price discovery purposes."
  • Its Compute Futures are "financially-settled futures based on the arithmetic average of the settlement prices for the Silicon Data H100 Rental Index (“SD-H100”) and B200 (“SD-B200”) Rental Index."
All 7 asks
  • On Core Principle 3: "the underlying reference indices of CME’s Compute Futures are supported by a robust level of trading in the underlying cash market."
  • On reliability: "raw inputs are pulled directly through verified API logs and billing telemetry across a large number of independent providers." "Silicon Data uses a proprietary pricing model to standardize raw unit prices to equivalent benchmark configurations."
  • On objectivity: "By excluding manual overrides and discretionary inputs, the indices ensure that every daily settlement value is fully reproducible from historical archives."
  • On cash market depth: transactions are "aggregated by Silicon Data across a large number of independent providers, averaging thousands of daily transactions."
  • On Core Principle 4: "CME Group is bringing to bear all of the same robust surveillance, investigatory, and enforcement resources to Compute Futures that it deploys across all of its other asset classes."

CME Group "owns and operates multiple futures exchanges registered as designated contract markets," including NYMEX. Trading in its Compute Futures "will be subject to the Rules of NYMEX." It states the indexes are "published by Silicon Derivatives Inc. (“Silicon Data”)." It states they have been "published continuously without interruption since inception," with a 729-day H100 history and a 395-day B200 history. It names AWS, Microsoft Azure and Google Cloud as hyperscale providers. It cites the findings section of the CEA, the July 2025 AI Action Plan and the Bandi estimate cited in the RFC.

Docket CFTC-2026-1850-0078 2026-10-20 Paradigm Operations LP (Stefan Schropp, Senior Regulatory Counsel) and Andromeda Cluster, Inc. (David Popkin, General Counsel)
Joint comment letter, 9 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(g)) · oversight (Q2(b), 2(d), 2(e), 2(h)) · customer protection (Q3(b), 3(d)) · perpetuals (Q4(a), 4(b))
  • Supports guidance under which "the Commission could require that DCMs disclose the extent to which indices: (1) have a published methodology, (2) differentiate between transactions based on specifications and tenor, (3) are grounded in transaction-based inputs or, where quotes are used, are labeled as such, (4) publish the number of contributors and level of contributor concentration, and (5) are administered by an independent body."
  • "We therefore urge the Commission to permit DCMs and others to develop and launch compute derivatives under appropriate oversight but without the delays or onerous conditions that would hamstring these critical markets."
All 7 asks
  • On physical delivery: "The Commission should therefore not seek to set quality standards or otherwise limit listed compute derivatives based on quality, provided that the terms of such listed derivatives are fully disclosed."
  • On Question 2(d), information-sharing agreements with each venue and provider: "We believe this would be unwarranted, as the CFTC has already recognized."
  • On Questions 3(b) and 3(d): "We do not believe retail-specific protections are necessary."
  • "There is no need for the Commission or DCMs to evaluate compute derivatives differently than other futures contracts."
  • On Question 4: "We believe perpetual futures are a natural fit for compute, but that they are complementary to fixed-date contracts, rather than a replacement for them." It sees "no reason to apply different standards to perpetual compute futures."

"Paradigm is a frontier technology investment firm that invests and builds in crypto, AI, robotics, and across new frontiers from the earliest stages." "Andromeda is a GPU compute infrastructure company that sources, operates, and delivers dedicated compute capacity to AI developers." Andromeda reports demand "from compute providers seeking to lock in forward revenue," from investors and from lenders. The letter names no index or administrator. It cites CME Eurodollar futures volume in 1981 and the EEI Master Agreement. It cites CFTC Staff Advisory 18-14 and its 2025 withdrawal. It also cites the 2024 voluntary carbon credit guidance and its 2025 withdrawal. It refers to Paradigm's comment on perpetual contracts under RIN 3038-AF75.

Docket CFTC-2026-1850-0077 2026-10-20 PMEX Markets, Inc., operating as Liquid Compute (Ronit Jain, Chief Executive Officer)
Comment letter, 24 pages, with 11 consolidated recommendations · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a)-1(g)) · oversight (Q2(a)-2(i)) · customer protection (Q3(a)-3(e)) · perpetuals (Q4(a), 4(b))
  • On Question 1(c): "PMEX does not believe a listed contract should settle to a reference price whose material inputs cannot be made available, on an appropriate confidential basis, to the listing DCM and the Commission for verification and surveillance."
  • "Inputs should be executed transactions wherever available, with any indicative or assessed component separately disclosed as a percentage of the index."
All 7 asks
  • "In PMEX’s view, an administrator of a settlement reference generally should not take positions in contracts that reference it."
  • "Disclosure, with each published price, of the transaction count, notional, contributor count, and indicative share actually supporting that print." It calls this "the single most valuable index reform available and the cheapest to implement."
  • "Treat physical deliverability as a favored anti-manipulation feature." The Commission "should not inadvertently advantage the easier index-only path."
  • Position and large trader reporting for compute "should, in our view, capture hardware class at SKU granularity, delivery region, tenor bucket, and contiguity."
  • For perpetuals, "a seasoning requirement" before listing: "a period during which the reference index has published continuously with adequate transaction support."

PMEX "has applied for designation as a contract market." Its affiliate PMEX Clearing, Inc. "has applied for registration as a derivatives clearing organization." PMEX "intends to operate under the name Liquid Compute" and is building a physical compute venue. It states that "the parent company of PMEX publishes indices and does not take positions in contracts that reference them." It offers to "provide transaction-level data from our physical venue as it develops." The letter names no index or administrator. It cites the LedgerX DCO registration (2017) and DCM designation (2019), FERC Order Nos. 888 and 2000, and IOSCO Principle 3. It also cites Baltic Exchange freight indices and the 1999 to 2002 bandwidth trading attempts.

Docket CFTC-2026-1850-0076 2026-10-20 OrchestraOS (Friedrich Siemers, Founder), Germany
Comment letter, 4 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(e)(iv), 1(f)) · oversight (Q2(b), 2(d))
  • "I suggest that contract specifications distinguish configuration and service terms from measured performance."
  • "Any performance grade should state the software, workload, output-quality requirements and latency limits used to measure it."
All 7 asks
  • "Index administrators should also explain how they handle changes in delivered performance when the reported hardware specification stays the same."
  • Proposes "a performance reference measured on a representative sample of delivered instances under published test conditions, with results subject to independent verification."
  • "Where the same stack is supported, comparisons across providers should use the same published reference-software version."
  • Testing should cover "capacity available to ordinary customers, under published rules for selecting instances and re-testing, with verification effort proportionate to an input's weight in settlement."
  • "The Commission should ask administrators how they detect material performance changes and when they adjust prices, reclassify inputs or exclude them."

Filed by the founder of OrchestraOS, "an early-stage project based in Germany that is working toward an operating system for AI inference and training." "No company has yet been formed." He holds "no positions in compute derivatives" and does "not currently offer an index or benchmarking service." He recommends "no particular benchmark or administrator." The letter cites a Silicon Data study of more than 3,500 GPUs at 11 cloud providers, the Silicon Data index methodology overview and Ornn's OCPI methodology. It also cites NVIDIA MLPerf results and the MLCommons inference rules. It builds on comments 0011 (ACU Markets), 0020 (Vandermolen Power), 0021 (Hivemind Capital), 0022 (Carvalho Ribas), 0030 and 0031.

Docket CFTC-2026-1850-0075 2026-10-20 Intercontinental Exchange, Inc. (Kara Dutta, Head of Legal, U.S. Futures Exchanges and Clearing, ICE Futures U.S., Inc.)
Comment letter, 4 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (not numbered) · oversight (Q2(d), Core Principles 3 and 4)
  • "ICE believes that the Commission should analyze proposed compute futures contracts under the existing principles-based regulatory framework for new products set forth in Core Principle 3 and the related guidance in Appendix C to Part 38."
  • "We caution the Commission against issuing any “compute-specific” listing guidance as an outgrowth of this RFC. Such guidance would be unnecessary, could hinder innovation, and may have a negative effect on this developing market."
All 6 asks
  • Settlement indices "should identify with specificity what is being priced (providers, regions and contract structures for compute rental, as applicable), be representative of the underlying market, be robust and meet all other applicable requirements set forth in Section (c)(3) of Appendix C to Part 38."
  • "ICE does not believe that any “compute-specific” surveillance practices, such as mandatory information sharing agreements, are necessary."
  • On Question 2(d): a DCM "can require its customers and market participants to provide cash-market positions and related information on request." DCMs "can also share information with other DCMs and exchanges through the Joint Compliance Committee and the Intermarket Surveillance Group."
  • "ICE believes that the underlying spot market for compute is substantial and growing and will satisfy the “not readily susceptible to manipulation” standard."

ICE operates "13 regulated exchanges and seven clearing houses," including ICE Futures U.S., a designated contract market. "ICE intends to list a suite of exchange-traded compute futures contracts." The letter does not name an index or administrator for those contracts. It cites the withdrawn voluntary carbon credit guidance and CFTC Staff Advisory No. 18-14 on virtual currency products. It offers power and freight as non-storable precedents. It cites the Bandi and Su estimate of $430 billion to $1.3 trillion a year in compute service flow. The letter is copied to Chairman Selig.

Docket CFTC-2026-1850-0073 2026-10-20 Vast.ai Inc. (Travis Cannell, Chief Operating Officer)
Comment letter, 4 pages · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a), 1(c), 1(e)(ii), 1(f)) · oversight (Q2(a)-2(d), 2(g), 2(i))
  • "The Commission should clarify how designated contract markets (“DCMs”) should exercise reasonable, documented diligence on source authorization, methodology and reliability."
  • On lawful sourcing: "Written administrator representations should identify the sources and confirm that the data is licensed or otherwise lawfully obtained and used, including any required source authorizations." It adds: "Licensing the finished index does not establish rights to its underlying inputs."
All 7 asks
  • Quotes "should not be presented as executed prices or counted as transactions. For a benchmark intended to measure prices actually paid, verified executed data should be preferred."
  • "The disclosure should distinguish executed transactions, posted quotes and modeled estimates." "Transaction counts and volumes should be identified as such only when based on executed activity."
  • The DCM should "obtain contractual assurances that the administrator retains the inputs and calculations it uses, in a form sufficient to reproduce published values."
  • The administrator should "disclose material commercial relationships with its data sources, including licensing arrangements, and whether any licensed source or its affiliates may hold or trade index-linked positions."
  • "Benchmark review should assess that economic diversity rather than impose uniform caps that could exclude representative data."

"Vast is an AI compute platform." In the 30 days ended October 14, 2026, "more than 2,500 providers earned revenue from more than 34,000 distinct customer accounts across more than 650,000 executed GPU rentals." It "offers data generated by its platform for licensing and discloses its commercial interest in that activity." Its Terms of Use "restrict systematic or automated extraction and the use of its data in indexes or benchmarks without a separate written agreement." Its logs show "sustained automated retrieval of listing and pricing data by third-party accounts." That collection continued after a July 24, 2026 licensing notice and a September 1 terms update. Vast "makes no allegation that a particular published index uses that data." The letter names no index, venue or administrator. It cites Appendix C to Part 38 and Rule 38.253.

Docket CFTC-2026-1850-0072 2026-10-20 PTG (Joanna Mallers, Secretary)
Comment letter, 5 pages, four recommendations · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets · oversight · perpetuals (not numbered)
  • "The Commission should confirm that compute derivatives can list on regulated U.S. DCMs when the contract is well specified and the settlement reference is robust." It "should not presume that cash settlement is the only viable design."
  • "The Commission should instead articulate the standards that any compute settlement reference should satisfy." These cover methodology, data sufficiency, governance and independence, manipulation controls and regulatory access.
All 6 asks
  • The Commission should set out expectations for index administrators, "including that an administrator should not trade the derivative or hold material physical exposure to the compute capacity its index measures."
  • "PTG does not believe compute derivatives require a new or separate listing process."
  • "PTG also encourages the Commission to ensure that perpetual contract specifications cannot change while positions remain open."
  • "PTG respectfully urges the Commission to confirm that bona fide market-making in exchange-traded, cleared compute derivatives should not be counted toward swap dealer de minimis thresholds."

PTG "is an association of firms that trade their own capital on exchanges in futures, options, and equities markets worldwide." Its members "would quote, arbitrage, and provide depth" in these contracts. It states "a direct interest in whether, and on what terms, these products trade." It "does not recommend that the Commission endorse any particular index, benchmark administrator, venue, provider, hardware class, or contract structure."

Docket CFTC-2026-1850-0070 2026-10-20 AI Compute Markets Pty Limited, trading as ACU Markets (Brandon Combes, Founder), Queensland, Australia
Supplemental comment letter, 17 pages, 11 numbered recommendations, with three appendices · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(e)(iv)) · oversight · perpetuals (not numbered)
  • "State that CEA section 9(a)(2) applies to reports made to compute price index developers, whether or not a compute contract is listed."
  • Each settlement input should come from "a registered entity that has accepted a code of conduct" or be "a public, executable posted offer observed directly by the index administrator and independently verified for fillability." A verified transaction "always carries more weight than an offer."
All 7 asks
  • Adopt minimum records for posted offers and executed transactions, the latter "including the non-price consideration field."
  • "Publish criteria for a settlement-grade compute unit." A contract on such a unit should state "the measurement standard, its version and the workload class in its terms and conditions."
  • A contract on more than one accelerator grade should publish "an eligible grade list and the basis on which each differential is observed and settled." A grade without qualifying measurement "is never priced as a function of another grade."
  • Every compute contract should state "its delivery basis," "its delivery interval, its availability tier, and its package or interconnect class."
  • Treat alignment with the IOSCO benchmark principles, "confirmed by published independent assurance," as a condition of a compute settlement reference. Consult FERC on its 2003 price index policy.

A follow-up to its September 15 letter (CFTC-2026-1850-0011). The same letter is also posted as CFTC-2026-1850-0061 and CFTC-2026-1850-0062. It proposes pricing compute on "a unit of delivered work, defined by an independent, audited and published measurement standard." It cites natural gas pricing in MMBtu as the precedent. It names the MLPerf results published by MLCommons as existing measurement. It states that "ACU Markets has no relationship with MLCommons." Its data proposals follow the FERC 2003 price index standards. It sets out four stages. A contract on a single specified grade "can list at Stage 2." It states a commercial interest and that it "has built an index methodology to these criteria."

Docket CFTC-2026-1850-0069 2026-10-20 Hydra Host, Inc. (Ariel Deschapell, Chief Technology Officer)
Comment letter, 8 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(b), 1(e)(iv), 1(f)) · oversight (Q2(b), 2(d))
  • "The Commission should encourage compute quality grades calculated uniformly across providers, so that an index compares like with like and quality is priced transparently."
  • An index should "publish a separate series for each grade," and a series should "serve as a settlement reference only once it meets minimum depth and contributor thresholds."
All 7 asks
  • "The Commission should focus its framework on contracts that settle in cash against a published compute price index."
  • "Any such index should be built only from real, completed rental transactions for graded compute, reported once by the party closest to the servers, and quoted in dollars per GPU-hour."
  • "Hydra recommends against listing token-referenced contracts until one can be shown not to be readily susceptible to manipulation."
  • Audit price reports against transaction and delivery records, "exclude affiliate transactions; cap any contributor’s index weight; require a minimum number of independent contributors."
  • Route market surveillance "through the index administrator, which holds the contributor agreements and audit rights, rather than through each individual compute provider."

Hydra Host "deploys, leases, and manages SI compute infrastructure for the leading super intelligence platforms." It is "an NVIDIA Cloud Partner specializing in distributed, bare-metal compute infrastructure." It states that "Hydra’s transactions never settle in cash." It describes itself as "among the largest contributors" of completed-transaction prices to "a leading independent compute price index expected to serve as a settlement reference." The letter does not name that index. It suggests the Commission could invite the National Institute of Standards and Technology to help define grades.

Docket CFTC-2026-1850-0068 2026-10-20 OCX Group, Inc., doing business as OneChronos (Kelly Littlepage, Co-Founder and Chief Executive Officer)
Comment letter, 14 pages, with four figures and one table · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(a)-1(g)) · oversight (Q2(a), 2(b), 2(d), 2(e), 2(g), 2(h))
  • "No new regulations specific to compute derivatives are needed; rather, the Commission should hold DCMs to design and surveil compute contracts with the same rigor and uniformity across venues that it expects for established commodities."
  • "Compute derivatives can be listed today, provided contract design begins where the asset is well defined." It names two paths: "physically settled futures defined around a narrow view of the asset, and cash-settled contracts on indices that are only as broad as the observable data supports."
All 6 asks
  • For physical delivery, "a DCM’s rules must specify delivery standards (hardware model, interconnect topology, location, service levels, and nonperformance remedies)."
  • A DCM can obtain price and supply data through "approved delivery-facility standards," information-sharing arrangements with cash venues and index contributors, and "targeted position surveillance under Regulation 38.254."
  • "The Commission should also consider permitting cross-margining of cash-settled and physically settled compute contracts across DCMs and clearing organizations."
  • "We encourage the Commission to apply its principles-based framework rigorously and uniformly across DCMs."

A follow-up to its September 24 meeting with CFTC staff (CFTC-2026-1850-0024). OneChronos "develops and operates combinatorial auctions and mathematical optimization mechanisms for capital and commodity markets." It has applications pending to register "OneChronos DCM LLC as a designated contract market" and OneChronos SEF LLC as a swap execution facility. It cites OneChronos Labs, chaired by Professor Paul Milgrom. It reports about $6.3 million of Kalshi GPU rental contract volume through October 11, 2026. It charts four anonymized H100 rental indices.

Docket CFTC-2026-1850-0066 2026-10-20 Solutions by Jewel (Jewel Darlington, Chief AI Governance Officer and Founder)
Comment letter, 7 pages, six numbered recommendations · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(c), 1(d), 1(f)) · oversight (Q2(a)-2(d), 2(g), 2(i)) · customer protection (Q3(c)) · perpetuals (Q4(b))
  • Recommends "that each DCM submission under 17 CFR 40.2 or 40.3 for a compute derivative include an Input Evidence Profile for the settlement reference price." The profile shows input classes, contributor depth, adjustments, exclusions and assurance.
  • On Question 1(c): "Inputs the DCM is unable to produce on request carry zero weight in the settlement value."
All 7 asks
  • "Every contributor of transactions or posted rates operates under a code of conduct consistent with IOSCO Principle 14." The DCM "sets and publishes a maximum single-contributor weight and a minimum contributor count per determination."
  • An information-sharing arrangement "between the DCM and the index administrator, and with each venue or provider whose inputs exceed the disclosed weight threshold," with "a scheduled review, for example after twelve months of listing experience."
  • "A material change to the methodology, the contributor base or a standardization model would trigger re-demonstration of the Appendix C showing for each listed contract that settles to the series."
  • Contract terms should state the market segment, "basis risk from hardware heterogeneity," "obsolescence risk for longer tenors," fallback provisions and affiliations.
  • For perpetual contracts, these controls "apply at the frequency of the funding calculation," and "the DCM demonstrate index robustness at that interval."

Solutions by Jewel is "a global AI governance advisory firm serving mid-market and enterprise organizations." It cites its own AI Decision Record v2.0 and AI Governance Architecture V2.0 as the basis for its proposals. It names the Silicon Data H100 Rental Price Index, the Ornn Compute Price Index (OCPI) and the CME Group H100 and B200 rental index futures. It cites perpetual GPU and DRAM futures on Architect Financial Technologies’ AX exchange. It offers CFTC Staff Advisory No. 18-14 as a model.

Docket CFTC-2026-1850-0065 2026-10-20 Crypto Council for Innovation and its Digital Energy Council (Ji Hun Kim, Chief Executive Officer; Rashan Colbert, Policy Lead, Digital Energy Council)
Comment letter, 8 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (not numbered) · perpetuals (Q4(a), 4(b))
  • "The Commission should therefore permit exchanges to develop both structures," fixed-date and perpetual, "where the contracts satisfy applicable requirements under the Commodity Exchange Act and Commission regulations."
  • "The Commission should focus on the integrity of the reference benchmark and the mechanism connecting the perpetual contract to it."
All 6 asks
  • "Reference indices should draw from sufficiently representative and reliable transaction data, with appropriate protections against manipulation."
  • "Exchanges should explain source hierarchy, transaction eligibility, volume weighting, outlier treatment, publication frequency, and independent governance." Also: "Rather than endorsing a particular provider at this stage, CCI encourages the Commission to assess proposed data sources against these objective criteria."
  • "The Commission should nonetheless expect exchanges to disclose basis limitations and avoid implying that an index is representative of capacity it does not measure."
  • Exchanges and administrators "should be able to demonstrate that inputs are independently verifiable, sufficiently representative of the defined compute exposure, and accessible to appropriate regulatory oversight."

CCI describes itself as "a global alliance of leaders within the digital assets industry." Its Digital Energy Council "brings together leading companies operating across the energy, digital infrastructure, artificial intelligence (AI), and digital asset industries." The letter sets compute beside the histories of WTI crude, Henry Hub natural gas, electricity and Bitcoin futures. It cites a Hyperliquid Policy Center paper on perpetual futures.

Docket CFTC-2026-1850-0064 2026-10-20 Silicon Data (Carmen Li, Chief Executive Officer)
Comment letter, 9 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(c), 1(e), 1(f)) · oversight (Q2(a)-2(e), 2(g))
  • "We encourage the Commission not to delay listing until the physical market standardizes, nor to treat all compute derivative proposals as a single monolithic category."
  • A listing DCM "should verify that the settlement index administrator adheres to the IOSCO Principles for Financial Benchmarks." Here "mere self-certification by an administrator is insufficient."
All 7 asks
  • To satisfy Core Principle 3, "a benchmark administrator must be strictly prohibited from engaging in proprietary trading or holding physical risk exposure in compute assets."
  • On Question 2(c): a settlement index should be calculated each business day "from no fewer than 5 independent providers, with no single provider accounting for more than 20% of index weight."
  • On Question 2(d): agreements "with every individual compute supplier would render cash-settled compute futures operationally infeasible." A neutral administrator can serve "as a centralized surveillance conduit."
  • A benchmark "should combine verified transaction records (secured under binding legal agreements) with directly executable API quotes, while excluding static marketing rate cards and unverified aggregators."
  • The Commission should "independently evaluate the underlying index of each cash-settled filing to verify its data depth, methodological fitness, and administrator governance."

Silicon Data describes itself as "an independent benchmark administrator and market intelligence platform for the AI compute economy." It "does not trade compute derivatives and does not own, lease, or hold GPU capacity." Its shareholders "include financial institutions and trading firms." Its CEO, Carmen Li, also serves as CEO of Compute Exchange, a spot procurement marketplace. The letter states that she "is excluded from all benchmark production and validation processes." NYMEX has submitted its H100 and B200 Rental Indices "as the settlement references for its proposed compute futures." Syntax Data is the calculation agent. Silicon Data "has not licensed its indices for use in perpetual contracts and is aware of unlicensed use of its indices in connection with such products."

Docket CFTC-2026-1850-0063 2026-10-20 Hyperliquid Policy Center (Jake Chervinsky, Chief Executive Officer; Brad Bourque, Senior Counsel)
Comment letter, 16 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(a)-1(g)) · oversight (Q2(a)-2(d), 2(g), 2(h)) · customer protection (Q3(a)-3(e)) · perpetuals (Q4(a), 4(b))
  • "The Commission therefore should not condition listing on a level of cash-market transparency that the market can develop through trading, provided the proposed contract has a reliable settlement basis and satisfies applicable listing requirements at launch."
  • "The Commission should permit contracts to settle to competing reference indices that meet applicable standards," rather than "designating a single administered series."
All 7 asks
  • Manipulation and concentration concerns "are best addressed through heightened surveillance, information-sharing arrangements, and appropriate position limits or accountability during the market’s early phase, rather than through a delay."
  • "The Commission should articulate what a reliable compute settlement index looks like and let DCMs list contracts that settle to indices meeting that standard." It supports the standard set out by Douro Labs (comment 0023).
  • "The Commission should encourage the introduction of derivative products referencing both classes of compute," the GPU-hour and the LLM inference token.
  • Perpetual compute contracts should "proceed through its existing case-by-case review under Regulation 40.3 and the Commission’s 2026 policy statement on perpetual contracts," with funding from "a continuously updated, multi-contributor index over a time-weighted window."
  • For retail users, among other safeguards: "Venues should publish the rules by which the index is computed and the contract settles, and change them only with notice."

HPC is "an independent research and advocacy organization dedicated to advancing a clear, regulated path for Americans to access onchain markets, including those available on Hyperliquid." It "works to advance policy that onshores and expands the market for perpetual futures, including to new commodity types." The letter names the NYMEX futures that settle to a Silicon Data index and ICE Futures U.S. futures on Ornn’s indices. It also names Architect, Kalshi, Pyth, and MarketVector’s index license to Paragon. It cites its own earlier submissions on energy and pre-IPO perpetuals, filed with trade[XYZ].

Docket CFTC-2026-1850-0060 2026-10-20 Lida Liberopoulou (independent researcher, Threadbaire)
Comment letter, 2 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(c), 1(e)(iv)) · oversight (Q2(b), 2(g))
  • For any settlement price, publish "the calculation method, and every change to it" and "the number of providers and transactions behind each observation window."
  • Publish "a log of changes to what the index contains (a new chip generation, a provider entering or leaving), so these are not read as market moves."
All 5 asks
  • Publish "enough information for an outside party to reproduce the settlement price."
  • On the share of the market an index covers: "I suggest each settlement index state that share, even as a range."
  • "Contract terms should state whether the reference is fixed to one generation, and how a successor generation entering an index is handled."

Filed in a personal capacity. She keeps the Compute Watch, "a monthly public record of what AI chips rent for." She states: "I have no product, no index, no trading position and no commercial relationship with any exchange, index provider or compute provider." She also states: "I take no position on whether any contract should be listed." The letter compares B200 and H100 readings from the Silicon Data and Ornn indexes. It cites comments by Setara (0005), TCX (0031) and Voltry (0039).

Docket CFTC-2026-1850-0059 2026-10-20 INFEREXUS, INC. (Jeffrey Phillip Forrest, Founder and Chief Executive Officer)
Comment letter, 4 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets · oversight · customer protection · perpetuals (not numbered)
  • Position limits and surveillance thresholds "should account for the reality that a handful of enterprise buyers may represent an outsized share of open interest in the early years of this market."
  • Customer protection "turns substantially on settlement reserve adequacy." Physical delivery "provides an important customer protection benefit specific to this market."
All 5 asks
  • The Commission’s "rules of the road should accommodate fixed-expiry, version-pinned contract structures as a distinct and complementary category alongside perpetual products."
  • Asks for "early Commission guidance on how AI inference capacity is classified as a commodity under the Commodity Exchange Act."
  • Asks for staff guidance "on how existing DCM listing and clearing-partnership requirements apply to this asset class."

INFEREXUS is "a Delaware corporation that has developed a novel financial instrument," the Convertible Inference Future (CIF). Its supporting technology "is the subject of a pending U.S. provisional patent application." The CIF is a physically delivered, version-pinned contract with "a cash-equivalent fallback." It is designed for listing and clearing on existing regulated venues. INFEREXUS "does not itself operate a designated contract market or derivatives clearing organization."

Docket CFTC-2026-1850-0048 2026-10-20 Fiftyrivers (Cheng Teik Tan, Principal), Singapore
Comment letter, 6 pages, with 10 numbered recommendations · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(a)-1(c), 1(e)-1(g)) · oversight (Q2(a)-2(h)) · customer protection (Q3(a)-3(e)) · perpetuals (Q4(a), 4(b))
  • "Specify a “par” grade in the contract terms (accelerator, interconnect/cluster, region/jurisdiction, commitment term, SLA) with published differentials."
  • "Index administrators should be independent, in ownership and governance, of hyperscalers and other major capacity suppliers."
All 7 asks
  • A "disclosed minimum number of unaffiliated contributors and maximum weight per contributor group, with automatic fallback on breach." It offers "at least five unaffiliated contributors and no group above one quarter of weighted inputs" as "illustrative starting points, not empirical findings."
  • "No settlement to data the DCM and the Commission cannot access and audit." For compute, an information-sharing agreement with the index provider "should be a condition of listing."
  • "Encourage exchanges of futures for related positions (EFRPs) against grade-conforming capacity, and develop a physically delivered pilot."
  • "Permit perpetuals alongside a dated contract on the same grade and index, with an index-anchored, capped funding rate, aggregated limits and an end-of-generation path."
  • For retail users, "leverage limits on perpetuals and a period of institutional trading before retail-sized contracts are offered."

"Fiftyrivers is the Singapore-based family office of Cheng Teik Tan." It writes "as a long-term investor whose holdings include investments with exposure to compute and AI infrastructure." It states that it is "not itself an exchange, index administrator, broker or compute supplier." It has "no investment in, or commercial relationship with, any exchange, index administrator or compute provider referenced in this letter." It takes "no position on any particular contract or index now before the Commission." The letter names the NYMEX Silicon Data H100 and B200 Rental Index Futures and the ICE Futures U.S. OCPI H100 and B200 futures. It cites the IOSCO benchmark principles and Baltic Exchange freight settlement.

Docket CFTC-2026-1850-0085 2026-10-19 ICX Global
Comment letter, 8 pages, with an annex · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1(a), 1(c)-1(f)) · oversight (Q2(b)-2(d), 2(g), 2(i)) · customer protection (Q3(b), 3(c)) · perpetuals (Q4)
  • "The first generation of compute derivatives should reference observable, precisely specified products, defined by a named GPU, geography and purchase mode (on-demand, spot, reserved or committed)."
  • An input hierarchy: "(i) verified transactions; (ii) executable quotes backed by available capacity; (iii) publicly posted prices; and (iv) modeled or imputed values." "Each daily determination should disclose the share attributable to each category."
All 7 asks
  • "The Commission should require evidence that posted rates were commercially available for the specified product, quantity and observation period."
  • "Benchmarks should impose contributor caps, minimum coverage requirements for providers and observations, related-party controls and heightened surveillance during the settlement period."
  • "The Commission should require an auditor or independent control function to reproduce historical values using the underlying eligible observations and approved methodology."
  • "We do not believe a regulated contract should settle against data that no one outside the benchmark administrator can observe or verify."
  • Before a normalized index is used for settlement, "its performance factors should be independently measured, auditable, workload-specific, versioned and subject to governance."

"ICX is developing an independent, venue-agnostic reference price for compute, with the goal of establishing a benchmark framework aligned with the IOSCO Principles for Financial Benchmarks." It states that "ICX does not operate a trading venue or supply compute capacity." The letter names no index, venue or firm. It offers electricity, natural gas, oil price-reporting agencies and telecommunications bandwidth as precedents. Its annex sets out an "illustrative daily benchmark disclosure" that "does not describe an existing index."

Docket CFTC-2026-1850-0079 2026-10-19 Fullview, LLC
Comment letter, 8 pages, with a reference list · regulations.gov · received Oct 20, posted Oct 21 · topics: All four (all 23 questions, numbered)
  • "The framework should accommodate outcome-based commercial arrangements where the relevant market and regulatory requirements can be satisfied."
  • On Question 1(a): "The Commission should evaluate on-demand, spot, reserved and committed purchases separately."
All 7 asks
  • On Question 1(c): "We would not support reliance on materially significant settlement inputs that the Commission and the responsible exchange cannot adequately examine, verify or surveil."
  • On Question 2(c): "The exchange should test how the reference price changes when major contributors are removed or activity falls sharply." It recommends "contract-specific evidence rather than a universal numerical rule."
  • On Question 2(d): "Every source whose transactions or posted rates enter the reference price should be covered by an enforceable arrangement providing the exchange with necessary information."
  • On Question 2(g): "If no series satisfies the relevant requirements, it should develop adequate support or reconsider the contract design before relying on the reference for listing."
  • On Question 4(a): "A perpetual product should demonstrate its useful commercial function and costs relative to available alternatives."

The letter does not describe Fullview's business. It is submitted in the firm's name with no individual signer. It states that its recommendations "are technology neutral and disclose no proprietary supporting material." It names Silicon Data and Ornn as public benchmark publishers and summarizes each methodology. It notes that Ornn's governance text "describes an oversight committee being established and conflicts procedures under development." It states: "We do not endorse a specific series as satisfying the full requirements on the evidence cited here." It cites AWS purchasing documentation, MLPerf Inference, Federal Acquisition Regulation Subpart 37.6 and Intercom's outcome-based pricing.

Docket CFTC-2026-1850-0074 2026-10-19 DRW Holdings, LLC (Donald R. Wilson, Jr., Founder and CEO)
Comment letter, 9 pages, with five recommendations · regulations.gov · received Oct 20, posted Oct 21 · topics: Cash markets (Q1, 1(g)) · oversight (Q2(d), Core Principles 3 and 4) · customer protection (Q3(a), retail access) · perpetuals (not numbered)
  • "Confirm that cash settlement to a robustly constructed, independently administered index can satisfy DCM Core Principle 3 for compute, notwithstanding that the underlying cash market is predominantly bilateral."
  • "Articulate expectations for administrators of compute settlement indices, centered on IOSCO adherence, independence from trading and from physical exposure to the underlying, published methodology with input diversification and contributor concentration limits, fallback procedures, auditability, and periodic independent assurance."
All 7 asks
  • An administrator "should not take proprietary positions in the derivatives that reference its index, nor in the underlying commodity beyond its own internal needs." It "should not own, operate, lease, or hold inventory of compute capacity beyond its own internal needs, and should not resell capacity."
  • "Place the surveillance information-sharing obligation on the administrator, rather than requiring a DCM to contract bilaterally with every venue and capacity provider."
  • "Apply position accountability rather than hard position limits at this stage, calibrated to the economic service flow at the pricing point rather than to a deliverable-supply analogy."
  • "We recommend the Commission allow conventional listed, financially settled, fixed-expiry compute futures to proceed on the ordinary product-listing path, and treat perpetual-style compute contracts as a separate, later question."
  • On perpetuals: "accumulate a track record for the reference index across at least one chip-generation transition; and then evaluate perpetual structures against that evidence."

"DRW is a diversified principal trading firm headquartered in Chicago." It discloses that it "is an investor in and was involved in the founding of Silicon Data, an independent benchmark administrator for compute, and Compute Exchange, a spot marketplace for compute capacity." "DRW expects to be a liquidity provider in listed compute derivatives." It states that posted rates "are directly executable through API calls, while reported transaction data remains comparatively sparse." It reports that several of the largest lenders against GPU clusters are slowing new lending because they "have exhausted their internal risk capacity." It cites SemiAnalysis ClusterMAX 3.0 (323 GPU cloud providers in September 2026), Synergy Research Group, and the CME Group and Silicon Data release of May 12, 2026. It names CoreWeave, Crusoe, Core Scientific, Lambda, Nebius and Nscale. Precedents cited include crude oil, natural gas, freight, iron ore, the IOSCO principles and LIBOR.

Docket CFTC-2026-1850-0067 2026-10-19 The Digital Chamber, by its counsel Duane Morris LLP (Stephen Rutenberg, Agatha H. Liu)
Comment letter, 32 pages · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets · oversight (Q2(d)) · customer protection (Q3(a)) · perpetuals (others not numbered)
  • "There is no need for a separate or additional regulatory regime for compute derivatives."
  • Asks that "self-certification under Regulation 40.2 should remain the ordinary path for compute contracts."
All 7 asks
  • "The Commission should apply its existing Part 38 designation standards to qualified DCM applicants and act promptly on those applications."
  • Permit multiple compute derivatives, "including, where appropriate, perpetual products, fully collateralized event contracts, and binary contracts referencing compute indices."
  • "The Commission should permit the natural development of multiple settlement models under its existing framework rather than require the market to choose a single structure or treat cash settlement as the preferred endpoint."
  • "The Commission should not, however, require information-sharing arrangements with every compute provider whose transactions or posted rates may contribute to a benchmark."
  • Future delivery, fixed pricing, transferability or a long-term commitment "should not by itself cause an ordinary commercial procurement arrangement to be treated as a regulated swap."

Filed by Duane Morris LLP on behalf of The Digital Chamber, "the leading trade association dedicated to the digital asset and blockchain industry." It has "more than 250 diverse member companies" and a Compute Working Group within its Digital Power Network. The letter thanks contributors including Sudhir Jain, "Chief Compliance Officer and Head of Regulatory Affairs at Kalshi." It cites the Silicon Data, Ornn and SemiAnalysis indices, CME Group, Nodal Exchange with Compute Desk, and Kalshi. It offers electricity futures and the Nasdaq Veles California Water Index futures as precedents.

Docket CFTC-2026-1850-0058 2026-10-19 Ornn AI, Inc. (Kush Bavaria and Wayne Nelms, Founders)
Comment letter, 5 pages · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets · oversight · perpetuals (not numbered)
  • Asks the Commission to "apply the existing CEA framework in a principles-based manner." The heterogeneity of compute "should be addressed through careful contract and benchmark design rather than treated as a categorical barrier."
  • "Benchmark administrators should use a transaction-based methodology and clearly define the economic unit being measured and the transactions eligible for inclusion in a benchmark."
All 7 asks
  • Data-sufficiency thresholds, concentration measures, sensitivity testing or contributor limits "should not be prescribed without regard to the structure of the underlying market."
  • The DCM needs "reliable access to the underlying information, not necessarily a separate contractual relationship between the DCM and every contributor to a benchmark."
  • "Public benchmark transparency need not require public disclosure of transaction-level confidential commercial information." The DCM and the Commission may receive more granular information on a non-public basis.
  • Perpetual compute futures "could complement fixed-expiration contracts." The price-alignment method, calculation intervals and "protections against abnormal divergence should be transparent and subject to effective market surveillance."
  • "Transaction-based indices such as OCPI should be evaluated under the Commission’s existing standards for cash settlement."

Ornn Data LLC, a wholly owned subsidiary, "administers and publishes the Ornn Compute Price Index (“OCPI”)," built from "executed on-demand rental transactions" by GPU type. An affiliate, Ornn Compute, matches customers with operators that have GPU capacity and lets them "transfer or sublet unused reserved capacity." The letter states that longer-term or reserved arrangements "may trade at different levels." Ornn offers "verified aggregate information" to the Commission, subject to confidentiality arrangements.

Docket CFTC-2026-1850-0057 2026-10-19 Simeon Bochev (personal capacity)
Comment letter, 37 pages, with two appendices · regulations.gov · received Oct 19, posted Oct 20 · topics: All four (all 23 questions, numbered)
  • On Question 2(g): "State the conditions now, apply them to filings under Regulation 40.3 and Regulation 40.2 alike, require composition disclosure, recognize governed methodology where it emerges without designating a provider, and approve the first contract that meets them."
  • "Articulate, in guidance, the minimum attributes an underlying compute unit must specify, and call for an independent, member-governed standards body to write the specification, convened if useful with the Department of Commerce and NIST on the ARRC model."
All 7 asks
  • "Treat provider-administered posted rates as unsuitable as primary index inputs, and cap their weight." Suggested levels: "no fewer than ten" unaffiliated contributors per window, "no contributor above twenty percent of index weight," and "no less than seventy-five percent from executed arm's-length transactions."
  • "Require periodic public disclosure of index composition: notional, contributor count, concentration, transaction share, and estimated share of market notional observed." Also "an annual independent assurance report on the input population and methodology adherence."
  • "Make information-sharing arrangements with contributing venues and providers a condition precedent to listing."
  • "Measure deliverable supply as transferable capacity in the delivery window, not installed base."
  • "Do not permit retail access at this stage; if permitted, disclose index composition at the point of trade." Condition perpetual listings "on the index standards, rather than on the passage of time."

Filed "in my personal capacity" by the founder of "a stealth compute markets venture." He is also helping form "an independent, member-governed standards body for compute measurement." He was "the founding chief executive of Compute Exchange," then Vice President of Strategy at Lambda, and earlier worked on AI infrastructure at Apple. On contract transfer rights he states: "I am building a venture that would benefit if what follows were adopted." The letter assesses the Silicon Data and Ornn series against Appendix C and states: "I am not alleging misconduct by either firm." It names the NYMEX rental-index futures, the announced ICE contract and the Thunder Compute pricing index. Appendix A sets out the sequence in which commodity markets were built. Appendix B lists nineteen recommendations.

Docket CFTC-2026-1850-0056 2026-10-19 Steven Skinner, Palm Coast, Florida
Comment, no attachment · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(c), 1(e)(iv)-(v), 1(f)) · oversight (Q2(a)-2(d), 2(g)) · customer protection (Q3(a), 3(b)) · perpetuals (Q4(a), 4(b))
  • Urges "one design choice: contracts on compute should settle against verified delivery, not against posted or self-reported prices."
  • On Questions 2(a) and 2(g): a settlement reference should count only GPU-hours "recorded at delivery in a form that is time-stamped, signed by the provider, acknowledged by the buyer and tamper-evident." "Transactions without such a record should not enter the settlement calculation."
All 6 asks
  • "Posted or list rates should carry no weight in settlement." The reference should "exclude trades between affiliates, publish contributor counts and concentration for each window, and cap any single provider's share."
  • "Information-sharing arrangements with contributing providers should cover these records, not only price feeds."
  • "Retail disclosures should state plainly that the index reflects a private, concentrated market and explain how its inputs are verified."
  • "Until a compute reference has a history of verified, delivered inputs and adequate depth, I would not approve perpetual compute futures, particularly for retail participants."

Filed as "a former Series 3-licensed commodity futures broker and an inventor working on systems that govern and record automated transactions." He discloses that he is "the inventor on U.S. patent applications filed in 2025" covering, among other things, "settling contracts against verified delivery records." He states: "These comments are my own views." The comment names no index, venue or product.

Docket CFTC-2026-1850-0055 2026-10-19 Jump Trading Group (Daniel Gerhardstein, Head of Policy; Robert Baldwin, Director of Policy and Government Affairs)
Comment letter, 9 pages · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(b), 1(c), 1(e)(i), 1(e)(iv), 1(g)) · oversight (Q2(h)) · perpetuals (Q4(a), 4(b)) · swaps (footnote 6)
  • Asks the Commission to "accommodate a range of underliers and contract designs, preserve competitive access to regulated markets, and apply its existing market integrity requirements in a manner suited to this evolving commodity."
  • It states that "the Commission should accommodate multiple underliers rather than seek to establish a single canonical compute product."
All 7 asks
  • "We encourage the Commission to accommodate physical delivery alongside cash settlement, with enforceable access rights, clear grading, and realistic deliverable supply estimates."
  • "The Commission should allow DCMs to develop grades and support trading in the price differentials between them." Exchanges should develop them "without a Commission-mandated single specification."
  • On Questions 1(g) and 2(h), an estimate "should consider installed capacity of the relevant grade at defined delivery points, adjusted for availability, existing commitments, and the ability to provision that capacity during the delivery period."
  • "DCMs should also retain access to the Part 40 self-certification process for new compute contracts." The Commission "should avoid imposing a categorical requirement that each compute product undergo a separate, extended approval and public comment process."
  • Asks the Commission to "consider rulemaking to exclude otherwise countable dealing activity in centrally traded and cleared compute swaps from the de minimis calculation, subject to appropriate eligibility conditions and safeguards."

Jump describes itself as "a global proprietary trading firm founded in Chicago in 1999" that "operates a U.S.-based high-performance computing grid." It writes as "both a derivatives market participant and a substantial user of compute." It anticipates "demand for physically deliverable contracts expiring three, six, and twelve months ahead." It cites the April 2020 WTI negative settlement and delivery constraints at Cushing. The letter is copied to Chairman Selig and Commerce Secretary Howard Lutnick.

Docket CFTC-2026-1850-0053 2026-10-19 Clarke Index, Inc. (Christopher D'Andrea, Founder and CEO)
Comment letter, 7 pages, with an illustrative appendix · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(b), 1(e)(iii), 1(e)(iv), 1(f), 1(g)) · oversight (Q2(b)-2(d), 2(h))
  • "We suggest DCMs build the estimate in layers, each with stated sources." The first layer is accelerators "of the specified type, in the specified geography, in service during the month."
  • Where owner-used and committed compute "cannot be fully observed, the fourth layer should be reported as an upper bound."
All 7 asks
  • DCMs should "publish a description of the method, its layers and its source types, even where the underlying data are confidential," and "state each layer as a range."
  • DCMs should revisit the estimate "whenever a large facility comes online, slips or is canceled, in addition to any regular schedule."
  • A DCM "could track expected additions, delays and cancellations for the geography a contract references." That "could help it judge whether a move in the settlement price reflects a change in supply."
  • Measure concentration "among the firms that sell capacity at an index’s pricing point." "Subsidiaries, brands and other entities under common control should count as one seller."
  • For any supply estimate: "state the basis of each power figure," state "whether it is a rated peak or a sustained rate," and "keep a record of revisions, with the reason for each."

Clarke "estimates installed compute supply at U.S. AI data centers" from "permits, generator records, grid interconnection queues and corporate filings." It "does not collect compute prices or rental transaction data, and expresses no view on any price index." It is "a commercial research business" and "could benefit if they estimate supply as this comment suggests." It "holds no positions in compute derivatives and has no agreement with any DCM or compute price index provider." The appendix uses hypothetical figures only. The letter cites NYMEX Submission No. 26-370 and the scope of the Silicon Data indexes. It agrees with comments by ACU Markets, TCX, Hedge Quantitative Research and Architect Financial Technologies, and also cites NativX.

Docket CFTC-2026-1850-0051 2026-10-19 InfraSight Software Corporation (Timothy A. Martin, Founder and CEO)
Comment letter, 6 pages · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(c), 1(e)(iv), 1(f), 1(g)) · oversight (Q2(a), 2(b), 2(d), 2(g), 2(h))
  • "Treat delivery verification as part of the Core Principle 3 analysis." Consider "whether the contributed capacity's delivered performance is independently verified, not only whether its price is observable."
  • "Ask DCMs to state how their settlement reference addresses quality differences between providers and the transition between hardware generations."
All 5 asks
  • "Recognize performance-normalized units as a path to standardization." The letter adds: "We do not ask the Commission to prescribe a unit or a methodology."
  • "Consider delivery quality in Core Principle 4 surveillance." It states: "Price and transaction surveillance alone cannot detect a debased unit."
  • "Convene a technical roundtable" of "exchanges, index administrators, compute providers, hardware vendors and measurement experts on defining and verifying a compute unit."

"InfraSight Software Corporation has worked on normalized measurement of computing resources since 2018." It holds two patent families, including U.S. Patent Nos. 10,719,364 and 12,387,156. The signer is a named co-inventor on both. It states: "Nothing in this comment constitutes a licensing commitment with respect to any intellectual property." The letter cites SemiAnalysis's ClusterMAX 3.0 provider ratings. It also cites the March 2026 moves in Silicon Data's B200 and H100 rental indexes.

Docket CFTC-2026-1850-0050 2026-10-19 Hyperbolic Labs, Inc. (Jasper Zhang, CEO and Founder)
Comment letter, 14 pages · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(a)-1(f)) · oversight (Q2(a)-2(e), 2(g)) · customer protection (Q3(a)-3(d)) · perpetuals (Q4(a), 4(b))
  • Clarify "that a physically-settled compute reservation between commercial parties does not become a futures contract or a swap merely because it is transferable and resalable."
  • "The index should be computed from executed transactions with identified counterparties, verified delivery, and recorded prices, quantities, and times." Posted rates "should be excluded or, at most, used as a fallback with published weighting when transaction volume falls below a threshold."
All 7 asks
  • "Transactions between affiliates, transactions bundled with equity, financing, or chip supply arrangements, and transactions at prices not independently negotiated should be excluded."
  • On Question 2(g), it states that no existing series satisfies Appendix C: "none presently does." It asks for "an industry working group, under the auspices of its Innovation Task Force, to settle the benchmark specification."
  • It "does not ask the Commission to prohibit exclusive licensing." It asks the Commission to state "that a settlement price whose level and methodology are not published on reasonable terms is not publicly available within the meaning of Appendix C."
  • Welcome "multiple compute benchmarks and multiple listing exchanges," and "permit composite references that draw on more than one administrator."
  • "Hyperbolic sees no basis for restricting access to compute derivatives by participant category."

Hyperbolic runs a compute marketplace and writes "as a physical market participant." Its Hyperbolic Compute Grid is where "capacity is verified, benchmarked, transparently priced, allocated, and reallocated." It states that "its own transaction data does not presently contribute to any published compute index." It would contribute that data "to any administrator operating under a published methodology on non-exclusive terms." It "would seek approval to serve as" a physical delivery facility. It also operates an inference platform and treats token contracts as "a separate product class." The letter cites Silicon Data H100 price history, Platts, Argus and the Baltic Exchange.

Docket CFTC-2026-1850-0049 2026-10-19 De Silva Law Offices, LLC (R Tamara de Silva, Managing Partner)
Comment letter, 16 pages · regulations.gov · received Oct 19, posted Oct 20 · topics: Cash markets (Q1(a), 1(c), 1(e)-1(g)) · oversight (Q2(a), 2(b), 2(d), 2(f)-2(i)) · customer protection (Q3(a)-3(e)) · perpetuals (Q4(a), 4(b)) · footnote 6
  • "The Commission should set out its expectations for compute derivatives in supplemental guidance to Appendix C to Part 38, proposed for comment."
  • "A compute contract should settle only on an index whose administrator can give the listing exchange, and through it the Commission, the data behind each settlement value."
All 7 asks
  • "Knowingly or recklessly false submissions to a compute index would fall within Section 6(c)(1)(A) of the Act and, when knowing, Section 9(a)(2)." The Commission should "make clear that a posted rate the provider will not honor can be a false report."
  • "Barring index contributors from compute futures would exclude many natural hedgers. Exchanges should instead identify their accounts and watch their trading, and their rate changes, during the settlement window."
  • "Final settlement should average daily index values over the contract month." Spot-month limits "should rest on observable index-eligible volume."
  • "Perpetual compute futures should be listed only if their reference index meets the standards in item 2." The Commission "should also codify by rule the position it took on perpetual contracts in May 2026."
  • "The Commission should confirm when a capacity reservation is a forward contract, what an exchange for physical in compute requires, and when a compute marketplace must register."

A Chicago "financial regulatory and litigation firm founded in 2002." Its clients include designated contract markets, futures commission merchants and proprietary trading firms. It names the Silicon Data and Ornn indexes behind the NYMEX and ICE proposals, and describes Silicon Data as "backed by the trading firm DRW." The firm "does not suggest that either has acted improperly." It "takes no position on whether any current compute index meets those conditions." It cites comments by GPU Economy (0025), Compute Capital (0018) and Capital Markets & Technology Partners (0010). It also cites the 2002 to 2003 natural gas false-reporting cases.

Docket CFTC-2026-1850-0047 2026-10-18 Mercatus AI Inc. (Wenyi Huang, Founder)
Comment letter, 3 pages · regulations.gov · received Oct 19, posted Oct 19 · topics: Cash markets (Q1(c), 1(e), 1(f)) · oversight (Q2(a)-2(e), 2(g))
  • "Benchmarks should give priority to executed transactions between independent parties." The published method "should separate executed transactions from quotes, posted rates, and estimates."
  • "Contributors under common ownership or control should be counted together." A DCM should "test the effect of removing the largest contributor."
All 5 asks
  • Governance rules "should apply equally to independent administrators and to venues that calculate their own indices, including any benchmark developed by Mercatus AI."
  • "A DCM and the Commission should be able to rebuild a settlement value from its source observations, eligibility decisions, adjustments, weights, methodology version, and corrections."
  • On Question 2(g): "We ask the Commission to state the standards above and test proposed settlement references against them. Where a reference falls short, the Commission should say what evidence is missing."

"Mercatus AI is building a market for contracts on LLM inference tokens," with delivery "measured through actual model usage." It states a commercial interest and that "we do not yet have the transaction volume that a settlement benchmark would require." The letter cites the Commission's 2003 and 2004 natural gas index enforcement actions and its 2012 LIBOR finding.

Docket CFTC-2026-1850-0046 2026-10-18 Babbage LTD
Comment letter, 10 pages, with three annexes · regulations.gov · received Oct 18, posted Oct 19 · topics: Cash markets (Q1(b), 1(c), 1(e), 1(g)) · oversight (Q2(a), 2(b), 2(g), 2(h)) · customer protection (Q3(c))
  • Asks the Commission "to encourage common minimum service disclosures, qualification supported by evidence, and verifiable prices."
  • "Advertised rates used in executable-offer settlement references should be verified as available for purchase."
All 5 asks
  • "Administrators should hold audit and production rights for contributed non-public records, publish proportionate disclosures, and explain each input category's contribution and the basis for any quantity weights."
  • "Listing proponents should demonstrate suitability for the particular contract."
  • These requirements should come "without prescribing a proprietary methodology, mandating a cooling or virtualization technology, or treating every configuration difference as a separate market."

Babbage "publishes a daily B200 accelerator price index based on provider-published rates and intends to seek its use as a settlement reference." It states "a direct commercial interest in this proceeding" and describes itself as "a prospective competitor of other index administrators." It states that its series "does not currently apply the availability verification proposed here." Annexes A to C set out an evidence schema, qualification and benchmark controls, and executable-offer verification. It describes the Ornn and Silicon Data methodologies as "not independently certified here" and cites the ICE Futures U.S. notice of September 29, 2026 on planned OCPI H100 and B200 futures.

Docket CFTC-2026-1850-0054 2026-10-17 CCE
Comment letter, 5 pages · regulations.gov · received Oct 19, posted Oct 20 · topics: All four (all 23 questions, numbered)
  • Supports compute derivatives "that serve commercial hedging needs, with clear contract specifications, verifiable settlement data, credible delivery arrangements and proportionate customer protections." Asks the Commission to "evaluate each product against evidence about the underlying compute rights, available supply and settlement methodology."
  • On Question 1(a): "We recommend evaluating on-demand, spot, reserved and committed compute separately, distinguishing posted offers, executed prices and delivered usage."
All 7 asks
  • On Question 1(d): "We recommend independent audits that trace reported trades to agreements, payments and delivery records."
  • "Settlement rules should prioritize verifiable transactions and define any use of posted quotes." On Question 2(g): "Supplier selling prices, including cost-plus prices, should be distinguished from independent benchmarks."
  • On Question 1(g): "We recommend basing position limits on capacity available for the contract's grade, location and delivery period."
  • On Question 2(e): "We recommend cautious initial position limits and risk controls calibrated to demonstrated liquidity, benchmark quality and deliverable capacity. Limits should expand as evidence supports them."
  • On Question 3(e): disclose "whether a platform acts as agent, reseller, principal or benchmark contributor, together with its compensation, affiliations and conflict controls."

Signed "CCE." The letter states that these intermediary expectations "should apply consistently, including to CCE." It offers electricity as "a useful comparison for time-specific capacity." It names no index, venue or other firm.

Docket CFTC-2026-1850-0045 2026-10-17 Dartmouth Advisory Partners Inc. (Brendan Sibeth, Founder and Managing Partner)
Comment letter, 6 pages · regulations.gov · received Oct 17, posted Oct 19 · topics: Cash markets (Q1(b)-1(f)) · oversight (Q2(a)-2(e), 2(g), 2(i)) · customer protection (Q3(b), 3(c)) · perpetuals (Q4(a), 4(b))
  • "The Commission should list compute contracts only against indices whose inputs the exchange and the Commission can observe, reconstruct after the fact, and classify the same way across venues."
  • "Require every settlement value to be reproducible from retained, time-stamped inputs, with corrections appended, never overwritten."
All 7 asks
  • "Settle against an average over the contract period, because compute cannot be stored."
  • On Question 2(c): each administrator should "state its own minimum volume and contributor floor, publish both values for each fixing, and switch to the fallback when either is breached."
  • On Question 2(g): "A careful outside reader should be able to confirm each Appendix C criterion from the administrator's public material alone."
  • "Name basis, benchmark, clearing, liquidity and export-control risk in the contract terms."
  • "Encourage one public classification of compute contracts and their indices across venues."

A Toronto "governance-technology firm" that "serves institutional asset owners and asset managers." It publishes the DAP Standard, a classification standard for investable assets, and runs Bellwether, a record of what regulators publish. It states: "DAP does not operate a trading venue, administer a compute index, or trade compute derivatives." Version 2026.2 of the Standard, "published for review, not adopted," added a classification for traded compute after CME Group and Silicon Data announced their GPU rental index futures.

Docket CFTC-2026-1850-0044 2026-10-16 Voltry (Michael Durham, Chief Executive Officer)
Supplemental comment, 1 page · regulations.gov · received Oct 17, posted Oct 19 · topics: Cash markets (Q1(e)(iv))
  • On Question 1(e)(iv): "Units are not fungible without adjustment, and the adjustments are of two kinds that should not be confused." Chip, memory, interconnect, region class, service mode and term are contract terms; condition "can only be made fungible by measuring it and grading it."
  • "Appendix C to Part 38 already supplies the form: a par quality, with differentials for non-par qualities that reflect what the cash market observes."
All 3 asks
  • The specification should state the grade's limits: a condition record "does not establish title, lien priority, location, export status, unencumbered capacity or delivered work."

Supplements Voltry's October 13 letter (comment 0039) and states that it "adds no new proposal." It responds to comment 0022: "Specification handles the bundle. A grade handles the card." It names comments 0020, 0021, 0027, 0030, 0031 and 0032 and states: "We take no view on their other recommendations."

Docket CFTC-2026-1850-0043 2026-10-16 Trevor Love
Comment letter, 3 pages · regulations.gov · received Oct 16, posted Oct 19 · topics: Cash markets (Q1(e)-1(g)) · oversight (Q2(a)-2(d), 2(g)-2(i)) · customer protection (Q3(c)) · perpetuals (not numbered)
  • "Define the underlier by operational service tier, including availability, scheduling, and interruption rights."
  • "Separate firm, scheduled, and interruptible transactions in the benchmark methodology, or justify and disclose any grade adjustments used to combine them."
All 6 asks
  • "Disclose the mix, count, and weighting of posted list rates and executed transactions used in each benchmark calculation."
  • "Count affiliated entities as a single benchmark contributor and disclose contributor concentration by unaffiliated contributor or contributor group."
  • "Estimate deliverable supply from enforceable availability during the relevant window rather than installed or nameplate capacity alone."
  • "Publish the chip-generation roll rule before listing, including its trigger, overlap period, adjustments, and notice process."

Filed as "an individual interested in artificial-intelligence systems, compute infrastructure, and accountable market design," without access to "proprietary provider operations, bilateral transaction data, or hyperscale-facility records." The letter lists ten requested actions and states that hardware condition "is also part of the underlier." It cites one observation of a Vellum cloud deployment that hibernated and woke on demand, "deliberately presented as anecdotal rather than independently verified evidence."

Docket CFTC-2026-1850-0042 2026-10-16 Architect Financial Technologies, Inc. (Brett Harrison, Founder and Chief Executive Officer)
Comment letter, 28 pages, with a cross-reference to every RFC question · regulations.gov · received Oct 16, posted Oct 19 · topics: All four (all 23 questions and footnote 6, cross-referenced)
  • "The Commission should apply the DCM Core Principles to each proposed compute contract on a product-by-product basis." Asks the Commission to confirm that a dated, cash-settled compute contract may be self-certified under 17 CFR 40.2.
  • Two standards for index administrators: "An administrator should not trade against its own index" and "An administrator must not measure its own transactions." The administrator attests to both at listing and recertifies annually.
All 8 asks
  • "Cash-market opacity is a contract design consideration, not a categorical bar to listing," provided the Commission "must have assured access to the data, through the DCM, under binding contributor and information-sharing agreements."
  • Minimum listing thresholds: "At least five unaffiliated contributors on each publication day," no single contributor or venue above 25% of a leg, and contributor HHI no higher than 2,500.
  • "If no series satisfies the Appendix C criteria for a given GPU class, a DCM should not list a cash-settled contract on that class. The Commission should not lower the standard to permit a listing."
  • Spot-month limits set from an estimate of uncommitted capacity in the index universe and from transaction depth, with position accountability outside the spot month.
  • Review perpetual compute contracts under 17 CFR 40.3, and "consider delaying approval until dated futures have been listed and properly studied."
  • Confirm that bilateral capacity agreements "entered into for commercial purposes and intended for physical performance are not swaps," and consider "a short, informational staff advisory" on compute listings.

Architect writes on its own behalf and for its affiliate American Innovation Exchange, a registered DCM, and states it "has a vested interest in the outcome of this process." Its Bermuda exchange, AX, has listed dated and perpetual compute futures since February 2026 on Compute Desk indexes, and AI Exchange intends to list on the same indexes. The letter states that the Compute Desk H100 Index "satisfies these criteria in most respects today" and that AI Exchange's license with Compute Desk "will require the exclusion of any transaction that Architect or its affiliates facilitate." It gives the H100 Index's annualized volatility since October 2025 as 12.3%.

Docket CFTC-2026-1850-0041 2026-10-15 Hedge Quantitative Research LLC (Jiho Lee, Principal)
Comment letter, 8 pages, with footnoted filing citations · regulations.gov · received Oct 15, posted Oct 19 · topics: Cash markets (Q1(a), 1(c)-1(g)) · oversight (Q2(g), 2(h)) · customer protection (Q3(c)) · perpetuals (Q4)
  • Asks that "the index administrator should be asked which contributors to the settlement price are also parties to floors, backstops, guaranties or GPU-backed credit agreements, and whether any contributor's posted rate enters settlement directly."
  • The exchange's surveillance "should treat a change in a contributor's posted rate during the settlement window as a flagged event."
All 5 asks
  • "Deliverable supply for a cash-settled compute contract should be measured as uncontracted GPU-hours at the contributing venues during the settlement window, not as installed capacity." The Commission "should ask for the deliverable supply estimate, its method, and the list of venues it counts, and it should ask for the same estimate with the largest single venue removed."
  • The Commission "should ask the administrator for the index's correlation with the other published series at the settlement horizon, and for its sensitivity to its largest contributor."
  • On perpetuals: "I do not see a commercial need that a perpetual meets and a monthly contract does not." If one is listed, the safeguards are "a published funding formula with a cap, a published index update schedule so the lead-lag is visible, and surveillance of the index observation window as a settlement window."

Written by "an independent quantitative consultancy" from a screen of 7,895 EDGAR annual filers and the GPU-backed credit agreements, backstops and guaranties filed with the SEC, with method and counts "available on request." It states: "I have no financial interest in Silicon Data, CME Group or any provider named." It reports that "No buyer among the 74 disclosed a per-GPU-hour rate" and that CoreWeave's August 2026 loan agreement "defines a 'Weighted Average Hourly GPU Rate' and redacts its value." It names backstops written by NVIDIA, Google, Meta and AMD, and cites a 0.17 weekly correlation between the Silicon Data and Ornn H100 indices (SSRN 7224223).

Docket CFTC-2026-1850-0071 2026-10-14 Andrew G. Huff, Ph.D. (Risk Factor Research, LLC, Michigan)
Comment letter, 4 pages, six numbered recommendations · regulations.gov · received Oct 20, posted Oct 20 · topics: Cash markets (Q1(c), 1(e)(iv)) · oversight (Q2(b)-2(d), 2(g)) · customer protection (Q3(a)) · perpetuals (Q4(b))
  • "Require any index used to settle a compute contract to define a standard compute unit precisely (accelerator generation, memory, interconnect, region, reliability, and pricing mode) and to publish its full methodology and adjustment factors."
  • "Require transaction-based inputs wherever they exist, cap and disclose any share drawn from posted rates, separate data contributors from index administration, publish outlier and minimum-contributor rules, and require independent audit."
All 7 asks
  • On Question 1(c): "I would not permit a contract to settle to a price computed from data that the DCM and the Commission cannot observe or verify on request."
  • "Require the index administrator to publish vital signs with each settlement period: the number of contributors, the largest contributor's share of volume, the share of transaction versus quoted inputs, and every restatement with its cause."
  • "Treat index data feeds and settlement prices as security-critical systems: signed contributor submissions, tamper-evident logs, independent recomputation, and incident disclosure to the DCM and the Commission."
  • "I recommend that the Commission consult the Department of Commerce before approving physically settled compute contracts." Know-your-customer programs should "include restricted party screening comparable to that required for exports of controlled items."
  • "Defer perpetual compute futures until a fixed-date contract on the same index has an observed, published record."

Andrew Huff writes "in my individual capacity; affiliation is for identification only." He describes himself as "an epidemiologist and security engineer" and states "I am not a derivatives practitioner." He discloses "no direct financial interest in any exchange, compute provider, or index provider" and that he "was not compensated for this comment." The letter cites CDC surveillance guidelines and the NIST post-quantum signature standards.

Docket CFTC-2026-1850-0040 2026-10-14 Lee S. Dryburgh (personal capacity)
Comment letter, 5 pages, with inline summary · regulations.gov · received Oct 14, posted Oct 14 · topics: Cash markets (Q1(a)-(f)) · oversight (Q2(g))
  • For any settlement reference, published at each observation window: "the number of contributing providers and of records; the share of inputs that are posted rates versus transacted prices; the share of index weight held by the largest one, three and five contributors; and the standardization model, or an audit of it."
  • The commodity is "one hour of work on one named accelerator, with the power, cooling and network behind it that make the hour usable."
All 4 asks
  • On Question 2(g): "the series are public and timely. Whether the cash market beneath them is sufficiently liquid, and whether their computation is acceptable, cannot be judged from what is published."
  • "The reference should be measurable by people other than its sponsor."

The author of THE AI COMPUTE RACE and AI TOKENS ARE THE NEW DOLLARS (forthcoming), who holds "no position in any compute index, exchange, cloud provider or chipmaker." The letter names Silicon Data's indexes, Ornn's Compute Price Index and SemiAnalysis's GPU Pricing Index as price series, and states: "I found no independent audit of any compute rental index's inputs." It cites SEC filings by SharonAI, CoreWeave and SpaceX for committed-contract totals, and GPU Economy (comment 0025) for posted committed-term rates.

Docket CFTC-2026-1850-0039 2026-10-13 Voltry (Michael Durham, Chief Executive Officer)
Comment letter, 2 pages · regulations.gov · received Oct 13, posted Oct 14 · topics: Cash markets (Q1(c)) · oversight (Q2(a)-(d), 2(g))
  • Asks the Commission "to state, in whatever follows this request, that the 'grade, quality' clause of Appendix C applies to compute as it applies to other commodities."
  • A settlement reference or deliverable specification "that does not state the condition of the hardware it prices has not fully described the underlying."
All 4 asks
  • On Question 2(c): "a reference should disclose the quality composition of its inputs, as the share of observations at or above the reference condition."
  • Grade inputs are "the counters the hardware itself reports," with published, model-specific criteria, and disputes go "to an independent re-read with a published time limit."

Voltry "produces signed condition records for NVIDIA GPUs." It states: "We never price hardware. We hold no position in any index, contract or venue." In its reads of thousands of GPUs over the past year, "about 1 in 13 reports retired or repaired memory rows." It names NYMEX Submission 26370 and the ICE Futures U.S. specifications for the OCPI H100 and B200 futures, and states it will publish its grade standard with the method, criteria and tolerances in full.

Docket CFTC-2026-1850-0037 2026-10-13 Submitter listed as "Nico, iLands"
Comment, no attachment · regulations.gov · received Oct 13, posted Oct 13 · topics: Cash markets (Q1(a)-(d), 1(f)) · oversight (Q2(a), 2(b))
  • On "whether a compute cash market today publishes a price a DCM could honestly settle against under Appendix C and Core Principle 3": "Answer: it does not. The only public ‘price of compute’ today is posted (list) rates administered by the capacity providers themselves."
  • A settlement methodology "drawing on multiple independent sources rather than any single provider's list."
All 3 asks
  • Before a DCM lists such a contract, "the Commission should require the submission to state (i) which posted series, (ii) who administers it, (iii) whether transacted volume is captured, and (iv) what independent verification of that data exists."

The comment states: "I am an AI agent (Nico) operating on the iLands platform. I hold no position in compute or derivatives." It cites the posted rates on RunPod's and Lambda's public pricing pages as list prices with no transacted volume.

Docket CFTC-2026-1850-0036 2026-10-12 Redr Labs
Comment letter, 5 pages, with summary statistics · regulations.gov · received Oct 12, posted Oct 13 · topics: Cash markets (Q1(a), 1(e)) · oversight (Q2(b), 2(c), 2(g), 2(h)) · customer protection (Q3(c))
  • "Disclose data-quality screens. Index methodologies should state how they treat zero-variance pools, pools with too few observations, and provider-administered posted rates, and publish those rules in advance."
  • "Disclose regional and provider basis. Contract terms should state that a national or provider-wide index may differ materially from a participant's actual cost, and state the index's geographic and provider coverage."
All 5 asks
  • "Test settlement inputs for fillable depth. Consider launch success, interruption frequency or comparable evidence, so thin pools do not set a settlement price."
  • "Distinguish purchase modes. Spot, on-demand, reserved and committed prices behave differently; an index from one mode should not be presented as representative of the others."
  • "Encourage open posted-rate histories."

Signed by Nicholas Cohen, founder. The data is 90 days of AWS posted spot prices for one 8-GPU A100 instance type across 31 availability-zone pools. The letter reports that pool means ranged "from $7.99 to $29.81 per instance-hour" and that four pools "posted exactly the same price to four decimal places in every one of 376 to 383 observations." Redr Labs "may in future offer analytics services in this area" and holds no positions in compute derivatives.

Docket CFTC-2026-1850-0035 2026-10-12 Ola Ologunde
Comment letter, 6 pages · regulations.gov · received Oct 12, posted Oct 13 · topics: Cash markets · oversight · customer protection · perpetuals (not numbered)
  • "Require any index used to settle a listed compute contract to publish its specification and adjustment rules."
  • "Require per-fixing observation counts and contributor concentration, including whether contributors are large compute providers or users."
All 5 asks
  • "Encourage a common definition of delivered capacity (for example, energised critical-IT megawatts, with power and revenue measures reported alongside, not instead)."
  • "Ask venues to state plainly which risks a compute contract hedges and which it does not: residual value, delivery, renewal, lien ranking and control (export limits and remote restriction)."
  • "For perpetual or long-dated contracts, require a published rule for rolling between chip generations."

Filed in a personal capacity, from London, as an independent product designer. The evidence is a prototype for valuing GPU-backed loans, with synthetic deals labeled as such. The letter reports that "a perfect rent hedge would narrow a GPU lender's value range by about 4%." It names the NYMEX Silicon Data H100 and B200 rental-index futures and the ICE and Ornn compute futures, and notes that "neither lists the A100." It discloses no position in any compute contract, index or company named.

Docket CFTC-2026-1850-0033 2026-10-10 Alec Snelling
Comment letter, 2 pages · regulations.gov · received Oct 10, posted Oct 13 · topics: All four
  • "Build settlement indexes from verified, actual transactions, not providers' self-reported or posted rates."
  • "Make sure no single provider or venue can move the index."
All 5 asks
  • "Set position limits or accountability levels sized to real deliverable supply."
  • "Protect retail participants." The letter also urges "caution about offering highly leveraged perpetual-style contracts to retail customers."
  • "Standardize before listing broadly."

Filed as a private citizen from Fair Oaks, California, who trades event contracts on a CFTC-regulated exchange. The letter supports "allowing designated contract markets to list compute derivatives, with guardrails" and states that "the derivatives market should reflect the price of compute, not drive it."

Docket CFTC-2026-1850-0032 2026-10-07 1791 Technologies LLC
Comment letter, 4 pages · regulations.gov · received Oct 7, posted Oct 7 · topics: Cash markets (Q1(b)-(e)) · oversight (Q2(a)-(e), 2(g))
  • The DCM and Commission "should be able to reconstruct the lineage of each settlement value, identify the methodology version that governed it, and determine what market population the value actually represents."
  • "Define the underlier as a bounded economic identity: contract terms should specify the dimensions that materially determine equivalence rather than treating ‘compute’ as a unitary commodity."
All 5 asks
  • "Require degraded-state and fallback semantics: thin or concentrated data, outages, anomalous inputs, methodology failure, or discontinuation should trigger a predeclared status and fallback path rather than silent substitution."
  • "Preserve original and revised values: if a benchmark is restated, the original published value and the superseding value should remain distinguishable with reason and effective date."
  • "Surveillance should also address the benchmark transformation itself."

Signed by Stephen Weber, founder, author of the Palimpsestus Open Spec. The letter "does not recommend prohibiting compute derivatives" and "does not recommend approval or disapproval of NYMEX Submission No. 26-370," the CME H100 and B200 filing it reviews.

Docket CFTC-2026-1850-0031 2026-10-06 TCX (thecloudx.co)
Comment letter, 5 pages · regulations.gov · received Oct 6, posted Oct 7 · topics: Oversight (Core Principles 3 and 5) · term structure
  • "Require DCMs seeking to list compute derivatives to demonstrate that settlement indices rely on verified, arm's-length execution data rather than unverified supplier rate cards or self-reported surveys."
  • Quality adjustments "based on realized workload throughputs specifically actual execution yield (Tokens/Sec per watt) and live interconnect efficiency ratios (NVLink/PCIe CRC error penalties)," instead of "theoretical nameplate chip ratings or uncalibrated energy proxies."
All 4 asks
  • "Require deliverable supply calculations under Core Principle 5 to explicitly deduct encumbered, long-term committed capacity from total installed hardware stocks."
  • "Ensure regulatory standards promote open, non-proprietary verification interfaces so that data center operators, clearinghouses, and market participants can participate without lock-in to proprietary index models."

Signed by Alfred G. Francis III. The letter argues that settlement should move to "deterministic, hardware-level execution metrics (‘bare-metal telemetry’)" and proposes a "Deliverable Compute Supply (DCS) framework" that deducts encumbered capacity.

Docket CFTC-2026-1850-0030 2026-10-05 Ömer Demirel
Comment letter, 12 pages · regulations.gov · received Oct 5, posted Oct 7 · topics: Cash markets (Q1(b), 1(c), 1(f)) · oversight (Q2(a)-(d))
  • "A cost-to-move test. As a documented stress test, the DCM shows what it would cost to move the settlement price through each index input and compares that cost with the gain available to the largest aggregated position."
  • "Only arm's-length, net and complete data. Deals under common control or with circular payments are excluded, other related-party deals are disclosed and reviewed, reported prices are net of all credits and rebates, and reporters submit every covered deal."
All 5 asks
  • "Random audits against independent evidence. An auditor with access to each reporter's full transaction records checks a random sample each period, and penalties are sized to outweigh the gain from manipulation."
  • "Concentration limits and published data quality. No single reporter can dominate a print, and every print shows how many deals, reporters and verified deals stand behind it."
  • "Surveillance that links reporters to positions. The DCM can see whether the firms supplying index data also hold positions that settle on it."

Filed in a personal capacity, from Switzerland. The letter addresses indexes "built from executed transactions, invoices or billing records" and discloses no position in compute derivatives and no commercial relationship with any compute exchange, index provider or capacity provider.

Docket CFTC-2026-1850-0029 2026-10-04 Submitter listed as "Grok, Bot"
Comment, no attachment · regulations.gov · received Oct 4, posted Oct 5 · topics: All four
  • "Treat short-tenor principal forwards as their own category. Do not fold them into provider-administered reservations."
  • "Require two-oracle settlement."
All 5 asks
  • "Each source should disclose the share of executed transactions versus posted rates, contributor count, and the largest contributor's weight in every published value."
  • "A transaction should enter the settlement input only if the capacity passed independent checks of hardware identity, benchmarked performance, and delivered uptime, and hosts that fail should be removed."
  • "Sequence perpetuals after short-dated fixed-date contracts and principal forwards have a settlement record."

The comment is unsigned. It addresses short-tenor GPU forwards in which the seller "stands as principal, takes the buyer's price risk, and must deliver the capacity," and cites the extended review of the CME H100 and B200 compute futures filing.

Docket CFTC-2026-1850-0028 2026-10-04 FastGPU
Comment letter, 7 pages · regulations.gov · received Oct 4, posted Oct 5 · topics: Cash markets · pricing methodologies
  • "We respectfully suggest that any settlement reference publish, for each input, at least the offer type, the exact hardware variant, the minimum quantity, the billing basis, the region and the time of observation."
  • On Question 2(b), protections "that are cheap to specify: count each provider once; use a median or a trimmed statistic rather than a minimum; require evidence that capacity was available at the posted price; and publish every constituent observation with its timestamp, so that a change to a posted rate during an observation window is visible to everyone at the time it happens."
All 3 asks
  • "We do not offer our series as a settlement reference."

FastGPU is a public price-comparison service for rented GPU compute. It has collected posted prices since July 31, 2026 and releases them under CC BY 4.0. It discloses that it joins provider referral programs, sells paid data access and offers a service that starts GPU instances at listed providers.

Docket CFTC-2026-1850-0027 2026-10-03 Persistence Analytics Group LLC (second comment)
Comment, no attachment · regulations.gov · received Oct 3, posted Oct 5 · topics: Cash markets · oversight (not numbered)
  • Evidence supporting a compute benchmark "should be evaluated not only at initial listing, but through a defined process for material-change revalidation."
  • "Where practical, benchmark governance should distinguish the evidence state of contributing observations and identify material dependencies on data that cannot be independently observed or verified."
All 4 asks
  • "Potential revalidation triggers could include material changes in hardware generation or substitutes; provider or contributor concentration; geographic composition; transaction or reservation structures; the mix of executed transactions versus posted rates; the ability to observe or verify material inputs; and capacity availability or deliverability."
  • Disclosures should separate "price risk" from "benchmark-assumption risk": the risk that "the relationship between the benchmark and the participant's actual economic compute exposure changes."

Signed by Neil P. Osnato. Describes the firm as "an independent advisory and analytics firm focused on Infrastructure Assumption Verification and Decision Assurance" and states that it "takes no position on whether any particular compute derivatives contract should be approved or prohibited." Its first comment is 0013, below.

Docket CFTC-2026-1850-0026 2026-10-02 NativX, Inc.
Comment letter, 12 pages · regulations.gov · received Oct 2, posted Oct 5 · topics: All four
  • "Recognize an energy-normalized unit of qualifying compute delivery as a viable denomination for a broad compute benchmark."
  • "Permit completed bilateral sales to contribute alongside venue executions when reporting obligations, verification controls and supervisory access are adequate."
All 4 asks
  • "Assess listing readiness against disclosed evidence appropriate to the proposed contract: qualifying volume, independent participation, concentration, commercial hedge performance and behavior during disruption."
  • "Require clear identification of the administrator, calculator, distributor and oversight body, together with enforceable access to underlying records and transparent treatment of stale or unavailable prices."

NativX administers COIL, a benchmark priced in U.S. dollars per Normalized Compute Unit, and operates the constituent-token spot market that feeds it. It states that ICE and NativX have announced plans for COIL-based futures, and that it has recently launched with no executed volume to report.

Docket CFTC-2026-1850-0025 2026-10-02 GPU Economy
Comment letter, 12 pages · regulations.gov · received Oct 2, posted Oct 5 · topics: Cash markets · pricing methodologies
  • "Publish every input of every settlement value with its source, read time and value, so the contract market, the Commission and the public can recompute it."
  • "Never blend posted rates with marketplace prices in one series"
All 5 asks
  • "Use a median or a trimmed estimator, require a minimum number of independent providers, and publish the largest provider's share and the concentration index with each value."
  • "Decide each period's panel by a published rule before the period starts, never revise it, and state its sensitivity: the largest shift one member can cause."
  • "Consider whether panel members should attest that a posted rate could be booked at the time it was read."

GPU Economy publishes posted GPU rental rates read hourly from 71 providers and a Cloud GPU Price Index, the median posted on-demand H100 SXM rate. It discloses a settlement license offered since October 1, 2026, which no one has signed and which has no fee set, referral programs with five providers (three of which post rates in the index), and possible fees on reserved-capacity requests it passes on. It holds no positions in compute or compute derivatives.

Docket CFTC-2026-1850-0023 2026-09-29 Douro Labs LLC (Pyth Network)
Comment letter, 9 pages · regulations.gov · received Sep 29, posted Sep 29 · topics: All four
  • "The Commission should therefore not condition listing on the maturation or standardization of the compute cash market."
  • The Commission "should confirm that an index computed from price inputs submitted directly by multiple independent contributors through a published, outlier-resistant aggregation methodology can satisfy Appendix C's requirements for a “reliable, acceptable, publicly available and timely” settlement price."
All 5 asks
  • "Permit DCMs to satisfy Core Principle 4 through an index-administrator arrangement."
  • "We recommend against fixed transaction-count thresholds."
  • "Permit perpetual compute contracts."

Douro Labs is "the core contributor to the Pyth Network" and operates Pyth Pro, a median-based reference-price service built from first-party publisher contributions. States that it "does not operate a compute venue, does not sell compute capacity and does not trade compute," and that it "is prepared to support a compute reference index on this basis." Cites the CME and Silicon Data H100 and B200 rental-index futures filing and the ICE and Ornn announcement, and takes "no position on any compute index or contract now before the Commission."

Docket CFTC-2026-1850-0022 2026-09-29 Dr Evelyse Carvalho Ribas (UK)
Comment letter, 7 pages · regulations.gov · received Sep 29, posted Sep 29 · topics: Cash markets · oversight · customer protection · perpetuals
  • The fungibility question "is better posed as “at what level is the unit defined, and who defines it” than as “what grade adjustment is required”."
  • On Question 2(g), the governance a compute index would need, including "an administrator that is independent of the contributors and does not itself supply compute capacity" and "a stated hierarchy of inputs that prefers observed transaction data over posted or administered rates, and that discloses the proportion of each in every published value."
All 5 asks
  • "Legal feasibility be treated as a condition to be established provider by provider and jurisdiction by jurisdiction, rather than as an undertaking a designated contract market can give in the abstract."
  • On perpetuals, ask "first what properties a reference index must have for perpetual mechanics to function as intended, and only then whether a compute index can have them."
  • Retail disclosure "should convey that the relevant risk includes discontinuous changes in the availability of the underlying arising from administrative action, and not only price volatility."

An independent legal and tax adviser, a Registered Foreign Lawyer in the UK and qualified in Portugal and Brazil. States that she holds no position, acts for no one and offers no data. Offers electricity markets as a comparator and the EU Benchmarks Regulation (2016/1011) as a comparative instrument, and recommends neither.

Docket CFTC-2026-1850-0038 2026-09-28 Samsung Next Fund LLC (David Lee, Authorized Officer)
Comment letter, 1 page · regulations.gov · received Oct 6, posted Oct 13 · topics: Cash markets · oversight (not numbered)
  • Supports "the Commission's efforts to better understand the developing market for compute and to consider whether and how appropriately regulated derivatives markets could provide useful tools for market participants."
  • "Proactive guidance and regulatory supervision within the United States can assist in setting credible global benchmarks for market integrity and price discovery."
All 3 asks
  • "Any benchmark used in connection with compute derivatives should be transparent, appropriately representative of the relevant market, and designed to promote market integrity and mitigate the risk of manipulation."

Samsung's venture investment arm, writing "solely on behalf of Samsung Next" as "a technology investor." It states that "compute is not a homogeneous resource, and pricing may vary based on hardware, configuration, availability, location, contractual terms, and other factors." It names no index, venue or product.

Docket CFTC-2026-1850-0020 2026-09-28 Vandermolen Power Limited (UK)
Comment letter, 14 pages · regulations.gov · received Sep 28, posted Sep 28 · topics: All four (all 23 questions, mapped)
  • Central recommendation: "verifiability before fungibility."
  • "Begin with narrowly defined, fixed-date contracts and clearly specified hardware or workload profiles; broaden only when transaction data and conversion evidence support it."
All 7 asks
  • "Require benchmark administrators and DCMs to disclose input-data coverage, contributor concentration, methodology, conflicts, exclusions, restatements and surveillance access."
  • For physical contracts, "require a versioned record of capacity, configuration, location, service attributes, encumbrances, delivery telemetry and retirement or consumption."
  • "Separate capacity registration, benchmarking, certification, registry operation, trading and clearing so that no producer can unilaterally create, price and validate its own deliverable supply."
  • "Use confidential regulatory reporting for bilateral transactions and capacity commitments where public disclosure would expose commercial terms."
  • "Defer broad retail access and perpetual compute futures until fixed-date markets, reference prices and surveillance arrangements have demonstrated resilience across hardware transitions and periods of stressed capacity."

States a commercial interest: it is developing a proposed "Digital Compute Unit (DCU) framework" and "intends to provide commercial services related to DCU." Ranks evidence in five tiers, with posted or advertised rates as "context only unless the administrator demonstrates that rates are actionable and representative." Lists Ornn’s OCPI (ICE), the Silicon Data rental-index futures filed by NYMEX, ICE with NATIVX, and Nodal Exchange with Compute Desk, and endorses none.

Docket CFTC-2026-1850-0021 2026-09-25 Hivemind Capital Partners, New York
Comment letter, 8 pages · regulations.gov · posted Sep 28 · topics: Cash markets · oversight · term structure · settlement and national security
  • "Advance DCM/SEF Listings for Cash-Settled Rolling GPU Benchmarks: Provide clear guidance affirming that transparent, volume-weighted median benchmark methodologies meet CEA Core Principle 3 standards."
  • "Formally Recognize Compute Basis Mechanics: Endorse exchange contract architectures that accommodate hardware, reliability, and regional variations through standardized basis differentials."
All 3 asks
  • "Clarify National Security Boundaries: Formally affirm the legal distinction between cash-settled financial hedging (CFTC exclusive jurisdiction) and physical capacity provisioning (BIS/CFIUS compliance at delivery)."

Calls compute "a $500B+ bilateral OTC market" already. Proposes settlement indexes "derived exclusively from programmatic, auditable API billing records and cleared bilateral trade prints, explicitly excluding non-binding, advertised list prices," with no provider above 20% of index weight, and tenors out to 12 months.

Docket CFTC-2026-1850-0018 2026-09-25 Compute Capital (USA), Inc.
Comment letter, 6 pages, plus a 12-page staff briefing · regulations.gov · received Sep 25, posted Sep 25); briefing CFTC-2026-1850-0019 (received Sep 25, posted Sep 28 · topics: Cash markets · oversight · customer protection · perpetuals (numbered)
  • Recognize that "a compute future listed in isolation from a documented, reportable OTC book will not produce the robust market the Chairman described."
  • "Evaluate DCM filings against whether the settlement series is a transaction print with governance the Commission can inspect, not a posted offer the supplier administers."
All 5 asks
  • Encourage, "and where the statute already allows require," side-by-side OTC infrastructure: ISDA documentation, named Commodity Reference Prices, calculation-agent standards and separate credit confirmations.
  • "Treat auction or dealer-poll determination of a tradable GPU-hour as a legitimate supplement when the tape is thin."
  • "Do not treat a perpetual listed future as the answer to long-dated commercial risk."

Argues that listed futures "inherit liquidity from the OTC market they sit next to. They do not invent it." Its briefing names the underliers: the Silicon Data H100 and B200 rental indexes for the CME contracts and Ornn’s OCPI for ICE, and says an OTC confirmation names one reference price, "never an average."

Docket CFTC-2026-1850-0024 2026-09-24 OneChronos, with Delta Strategy Group (meeting with CFTC staff)
CFTC staff meeting summary, 1 page · regulations.gov · posted Sep 29 · topics: Cash markets · pricing methodologies
  • The summary records only the topic: "Discussed observations regarding compute markets generally, including with respect to surrounding pricing methodologies."

Meeting of September 24, 2026, between CFTC staff and OneChronos, with its policy advisers Delta Strategy Group. An August remark from OneChronos appears in the statements section below.

Docket CFTC-2026-1850-0016 2026-09-24 VeloxVFX LLC, Bountiful, Utah
Comment letter, 13 pages · regulations.gov · received Sep 24, posted Sep 25 · topics: All four (all 23 questions, numbered)
  • Takes no position on any contract: it "does not recommend approval or rejection of a particular compute derivative, index, provider, venue, or perpetual design."
  • Keep source, provenance, benchmark-input eligibility, validation, execution and settlement separately attributable: "Observable information is not automatically qualified settlement information."
All 4 asks
  • "A continuing numerical output should not conceal contributor exit, increased concentration, changed methodology, stale observations, source loss, or other changed conditions."
  • Where a price series has not been shown fit for settlement, "the qualification should remain unresolved. The existence of a numerical series should not itself supply the missing evidentiary basis."

An information-governance comment. It states that it holds no compute-market data and answers each question within that limit.

Docket CFTC-2026-1850-0013 2026-09-22 Persistence Analytics Group LLC
Comment, no attachment · regulations.gov · received Sep 22, posted Sep 23 · topics: Cash markets · oversight (not numbered)
  • "Distinguish representation from evidenced availability": represented capacity should not count as deliverable without evidence of its hardware, location, energization, reservation status and dependencies.
  • Define "a defined state" of the underlier as well as the commodity itself.
All 4 asks
  • Contract terms or settlement methods should "identify material-change triggers requiring revalidation."
  • Settlement references should "clearly identify eligible compute, evidence supporting inclusion, resource state at the observation time, freshness requirements, material exclusions, and circumstances requiring revalidation or removal from the reference set."

Warns that mixing on-demand, reserved and nominal capacity "may produce a price series without establishing economic equivalence."

Docket CFTC-2026-1850-0011 2026-09-15 AI Compute Markets Pty Limited, trading as ACU Markets (Brandon Combes, Founder), Queensland, Australia
Formal comment letter, 14 pages, 13 numbered recommendations · regulations.gov · received Sep 16, posted Sep 21 · topics: All four, answered question by question
  • Publish compute-specific guidance under Appendix C "setting out what a compute settlement reference price must demonstrate", before first-of-kind contracts are listed.
  • "Provider-administered posted rates are not admissible as a primary settlement input, and where used at all are weight-capped and disclosed, with executed-transaction and live-market-quote primacy in the input hierarchy."
All 4 asks
  • Per-cell contributor quorum and concentration limits "enforced fail-closed, with a null and reason code on breach"; "deterministic replayability" of every published value by a third party.
  • First-of-kind contracts by Commission approval under 17 CFR 40.3 rather than self-certification; defer perpetual compute futures; a comparability path for non-US administrators; consult BIS and OFAC before listing.

An index provider; discloses that it "would stand to benefit if the Commission established criteria for compute settlement reference prices". Its central claim is that "the sellers set the settlement price": posted rates are "a publication, not a transaction" and the firms that administer them are the natural short side. Answers Q2(g) "No, not today, and not from any provider, ourselves included."

Docket CFTC-2026-1850-0010 2026-09-15 Capital Markets & Technology Partners (John J. Rapa)
Comment letter, 20-page attachment · regulations.gov · received Sep 15, posted Sep 16 · topics: Cash markets (Q1) · index methodology and oversight (Q2) · perpetual futures (Q4)
  • A central reporting authority for bilateral cash-market transactions, with "current and historical price data, publicly available"; "the independence of the reporting authority from the entities that it measures will be key, going forward".
  • "Transparency and oversight of Compute Futures index providers, their index calculation methodologies and transparency of settlement pricing."
All 4 asks
  • DCMs should have "robust systems, processes and procedures to identify, detect and capture Compute Futures index transactions posted by index providers and surveil them for irregularities".
  • Perpetual contracts "will function more like swaps products and their structures should be more closely evaluated by the Commission".

Concludes that "the present underlying market is not ready to support listed derivatives", on concentration grounds: ten operators holding two thirds of one GPU generation, cited to a third-party report. Describes the announced exchange products and their index administrator. Carries a no-AI disclosure.

Docket CFTC-2026-1850-0008 2026-09-11 Steven Singleton
Comment, no attachment · regulations.gov · received Sep 11, posted Sep 14 · topics: Oversight (Q2(b), 2(e), 2(g)) · customer protection (Q3(b)) · perpetual futures (Q4(b))
  • The Commission should commit, "in a follow-up notice, to heightened review of self-certified compute filings until the open questions in Section II.2 are answered".
  • "Condition self-certification eligibility on public disclosure of the number and market share of rate-contributing providers feeding any settlement index."
All 4 asks
  • Tie "any retail-facing compute contract to a specific, dated disclosure requirement".
  • Ask whether the payment mechanism for a perpetual contract "would rely on the same data inputs Question 2(b) already flags as provider-administered".

States: "None of this is a case for leaving compute derivatives unlisted indefinitely." The concern it names is sequencing.

Docket CFTC-2026-1850-0014 2026-09-10 Balthasar Issa, London (personal capacity)
Comment letter, 9 pages · regulations.gov · received Sep 22, posted Sep 23 · topics: All four, answered question by question
  • Define "a precisely and narrowly defined hardware generation, configuration, and location as the reference underlier", with tenors short enough to avoid a hardware-generation transition or a contract that "transparently rolls and re-defines the underlying".
  • "Require both minimum contributor counts and a cap on a single contributor’s share of index volume", and "ensure that quotes during observation windows are genuinely executable."
All 4 asks
  • "Credible, transaction-referenced, audited price-reporting infrastructure needs to be established first"; derivatives "should only start to list once that infrastructure exists and has an operating track record".
  • Exchanges should consider "power-compute spreads, perhaps something like a ‘compute spark spread’".

Argues that two features of compute are durable: the hardware "depreciates on a functional basis on a roughly annual cycle", and a compute-hour "is not a homogeneous unit". Treats list-price markets and bilateral reserved capacity "almost as two different commodities". Sees perpetual futures as better suited to hardware turnover, with the same reference-price standards as a prerequisite.

Docket CFTC-2026-1850-0007 2026-09-07 Li Li (independent researcher, personal capacity)
Comment letter, 7 pages, "From Price Hedge to Credit Signal: Risk Considerations When Compute Derivatives Enter AI Infrastructure Finance" · regulations.gov · received Sep 7, posted Sep 8 · topics: Cash markets (Q1(e), 1(f)) · oversight (Q2(e)) · customer protection (Q3(c))
  • Contract specifications and risk disclosures should distinguish the reference-price exposure covered, the differences between the index and common commercial compute contracts, that "cash settlement does not ensure access to physical capacity", and that "an effective price hedge does not ensure adequate project cash flow or debt-service capacity".
  • Risk materials for commercial hedgers should explain "the potential timing mismatch between derivative margin obligations and cash flows from the underlying compute business".
All 4 asks
  • Product materials should state that listing "does not constitute a Commission determination that the relevant index is suitable for loan pricing, collateral valuation, or credit assessment".
  • Exchanges should publish "the historical relationship between the futures reference price and major categories of commercial compute contracts"; the Commission should monitor whether futures prices enter financing and valuation frameworks and produce procyclical effects.

Supports listing. The argument is that a hedge transfers price risk only: "the hedgeability of compute should not be equated with the bankability of the underlying project." No data, no index named. Carries an AI-assistance disclosure.

Docket CFTC-2026-1850-0006 2026-09-04 Animica Labs (Alienbeing LLC, DBA Animica; Alexander Lehman, Founder)
Comment letter, 5 pages, with three attachments: a posted-rate census (13,030 rows), a computed summary and a reproduction script · regulations.gov · posted Sep 4 · topics: Cash markets (Q1(b), 1(c), 1(e)) · oversight (Q2(b), 2(d), 2(g))
  • Do not treat cash-market opacity "as an inherent property of compute. It is a property of a settlement architecture."
  • "A contract should not settle to a price the Commission cannot observe or verify"; this "counsels a sourcing requirement, not abstention from listing".
All 3 asks
  • "Make observability a listing condition rather than a hoped-for disclosure": independently verifiable settlement, a published methodology fixed in advance, "counterparty-diversity floors, not volume floors", and a stated delivered unit with attestation of delivery independent of the payment record.

Data is a 17-day census of machine-priced inference endpoints paid over the x402 protocol. The filer states the census covers the API layer, "not evidence about hourly accelerator pricing", and gives its own scale as 226 settlements for $3.12.

Docket CFTC-2026-1850-0005 2026-09-01 Setara Financial Corp (H. Jack Bouroudjian, CEO)
Formal comment letter, 3 pages, "Via Electronic Submission" · regulations.gov (first posted on LinkedIn as page images) · received Sep 1, posted Sep 4 · topics: All four
  • Permit and facilitate compute derivatives on regulated U.S. venues; "encourage competition among venues and methodologies".
  • Do not delay "until a perfect benchmark exists".
All 4 asks
  • Basis "should be measurable, transparent and economically manageable at the outset of a trade"; a hedger’s exposure is to "H100, H200 or B200 capacity in a particular geography".
  • Support perpetual compute futures where the structure fits, with convergence, margining, funding and settlement safeguards.

Their second letter. An open letter posted on LinkedIn on August 20, before the docket opened, asked for "an independent reference layer that can sit beneath competing venues". The filed letter replaces that with competition among methodologies.

Docket CFTC-2026-1850-0004 2026-08-24 Anonymous
Short comment, no attachment · regulations.gov · filed · topics: Oversight
  • "Clear provisioning on the index calculation methodology, transparency with respect to the underlying market data collection process and source."
  • "Clear separation of index providers business functions and the interests of its investors, of whom many are trading firms."
All 3 asks
  • "A clear designation of what and how a unit in this commodity class is measured and standardized across hardware architectures."
Docket CFTC-2026-1850-0003 2026-08-24 Anonymous
Comment with attachment, "feedback-observability" · regulations.gov · filed · topics: Cash markets · oversight · customer protection (Q1(f), 2(d), 2(e), 3(c))
  • Surveillance should distinguish "when a derivatives price is primarily measuring scarcity from when that financial signal is also materially participating in the production, allocation, or reduction of scarcity".
  • Observe concentration across "physical capacity + benchmark observations + reservation behavior" together rather than within each layer alone.
All 3 asks
  • "Successful financial hedging should therefore not necessarily be treated as equivalent to successful physical procurement."

States that it takes no position for or against listing, and that "large-language-model assistance was used to organize and draft this comment".

Docket CFTC-2026-1850-0002 2026-08-21 Michael Ravnitzky, Silver Spring, Maryland
Comment letter, 7 pages · regulations.gov · posted Aug 24 · topics: All four
  • The Commission "should refrain from the listing of compute derivatives until a standardized, independently governed benchmark is in place and mandatory, verifiable reporting from power-dependent compute providers is established".
  • An index "must adjust for the operational factors that determine compute’s economic value; simple posted-rate averaging is structurally inadequate": hardware age and efficiency, data egress costs, regional power constraints.
All 3 asks
  • "Until these risks are better understood, perpetual compute futures should not be listed."

Notes that "compute", "compute capacity" and "compute services" are used interchangeably in the RFC and asks the Commission to say which it means.

CCIR publishes compute price data and research. Docket items, including comment letters and CFTC staff meeting summaries, are checked against regulations.gov on the date at the top of this page. Letters posted outside the docket appear when the full text is public. The Commission posts comments as received, without review, and does not remove personal or business information.

03 Statements to the press and at meetings

Remarks spoken at Commission meetings or given to the press, by people who have not filed a letter. They are outside the docket. Each row carries the remark as reported and a link to the report.

DateWhoWhereStatementSource
2026-08-20 Don Wilson, founder and CEO, DRW CFTC Innovation Advisory Committee, inaugural meeting, Washington “It is a mistake to delay the launch of these futures by subjecting them to a lengthy comment period.” Also: "Risk management instruments in the compute space are essential to reducing the cost of capital." GARP, Aug 28
2026-08-20 Raghu Yarlagadda, CEO, FalconX CFTC Innovation Advisory Committee “The CFTC has a remarkable opportunity to define compute as an asset class.” John Lothian News, Aug 28
2026-08-20 Tushar Jain, co-founder, Multicoin Capital CFTC Innovation Advisory Committee “We are seeing a lot of new entrepreneurial ideas on how to structure compute derivatives. They don’t look a lot like traditional commodities.” Asked for room to test designs at small scale before committing capital. GARP, Aug 28
2026-08-20 Terry Duffy, CEO, CME Group CFTC Innovation Advisory Committee “Let’s call that a coincidence.” On the sequence of the 60-day window, CME’s planned October 5 listing, and a Cantor Fitzgerald announcement on Kalshi contracts the same day. BeInCrypto via Yahoo Finance, Aug 20
2026-08-12 Kelly Littlepage, founder, OneChronos To Axios, before the request issued “Compute fails every measure of being a commodity.” Axios, Aug 12

The Commission's own account of the meeting is in the Chairman's remarks of August 20. Legal explainers that summarize the request without taking a position are not listed.

04 The 23 questions in the request for comment

The Commission's text, unchanged, from 91 FR 54263 to 54264. Open a topic to read its questions.

Topic 1 Compute cash markets: size, liquidity, and other considerations 91 FR 54263 · 7 questions
  1. 1(a) How does observed price behavior in compute markets compare to price behavior in cash markets underlying derivatives that the Commission has customarily regulated? In responding, please distinguish between on-demand, spot, reserved, committed purchase modes, and state for each the volume transacted, the number of distinct counterparties transacting, and whether any transaction price is published. Are there particular commodity markets that the Commission should consider as being especially relevant or similar to the compute cash market?
  2. 1(b) What data sources, analyses, calculations, variables, or other factors should be used to determine the market size, liquidity, transaction volume, types of participants, and supplier concentration of compute markets? Please distinguish between publicly available data sources and the data derived from non-public, bilateral agreements. How should the Commission consider the fact that, in the Commission’s preliminary understanding, non-public, bilateral agreements carry the majority of economic value but tend to be undisclosed and negotiated privately?
  3. 1(c) What proportion of compute transactions occur at publicly disclosed prices, and what proportion does not? What data applicable to this question is available by voluntary disclosure, as opposed to obligations under statutory, regulatory, or contractual obligations? Would it be appropriate to permit trading in a derivative contract settling to a price computed from data that the Commission may not be able to observe, verify, or surveil, in whole or in part?
  4. 1(d) Have any audits, studies, or independent verifications of the transaction data referenced in question 1(c) above been conducted, and if so, what did they conclude?
  5. 1(e) How do the characteristics of the compute cash markets differ from those of the cash markets underlying derivatives customarily regulated by the Commission? Please address the following characteristics: (i) whether the underlying commodity is storable; (ii) whether a publicly observable transaction record exists, and what proportion of the total transaction volume it captures; (iii) the number of producers of the commodity and the share of commodity production attributable to the largest producers; (iv) the extent to which units of the commodity are fungible across producers without adjustment, and if not, what quality or grade adjustments are necessary to foster fungibility; and (v) whether any price reporting agency or enforced standardized methodology exists.
  6. 1(f) Please describe any potential effects on the cash market for compute that may arise in connection with the listing or trading of compute derivatives. In particular, would the existence of a listed futures contract settling to a published compute index change provider incentives with respect to the publication of posted rates, the pricing or structuring of bilateral reservations, the disclosure of utilization and committed capacity data, or the allocation of capacity amongst purchasers? How should the Commission consider whether the parties best positioned to influence the reference price are the same parties that supply capacity or contribute transactions or posted rates from which price is computed? Is this different from other derivative contracts and their commodity underliers?
  7. 1(g) Regarding DCM Core Principle 5, what would be an appropriate deliverable supply estimate methodology to evaluate the necessity and appropriateness of position limits or position accountability levels?
Topic 2 Market oversight and susceptibility to manipulation 91 FR 54263–54264 · 9 questions
  1. 2(a) Core Principle 3 requires a DCM to list only contracts not readily susceptible to manipulation. What features would a compute derivatives contract that cash settles to an index calculated over predominantly bilateral and privately priced cash market transactions be required to demonstrate to satisfy that standard, consistent with the Appendix C Guidance?
  2. 2(b) Certain published compute price series are constructed in whole or in part from posted or listed rates that the compute capacity providers themselves administer, with the remainder of transactions executed on venues that a small number of participants operate or dominate. Are there protections or requirements that would prevent a compute capacity provider from manipulating a cash settlement index by adjusting a posted rate, directing capacity onto or away from a venue whose transactions the index calculation methodology treats as input data, or by executing or declining to execute transactions during the observation window? Please describe any such protections or requirements which the Commission should consider.
  3. 2(c) What volume, transaction-frequency, and contributor concentration data typically characterize the population from which a compute reference price may be calculated? What thresholds would be appropriate for a compute settlement reference price given the idiosyncrasies of the cash markets for compute?
  4. 2(d) Core Principle 4 requires a DCM to have the capacity and responsibility to prevent manipulation, price distortion, and disruption of the delivery or cash-settlement process. What surveillance capabilities would be necessary to satisfy Core Principle 4 for compute derivatives, and are those capabilities presently feasible from a technological, operational, and legal perspective? Should a DCM be expected or required to maintain an information-sharing arrangement with each compute venue and each compute capacity provider whose transactions or posted rates enter a settlement reference price against which a compute derivative settles on the DCM?
  5. 2(e) What, if any, recalibration of market safeguards, risk controls, and liquidity protections should a DCM implement for compute derivatives to ensure price formation remains representative of genuine supply and demand, and to prevent thin liquidity conditions from resulting in disproportionate or runaway price movements that could influence benchmark markets?
  6. 2(f) Are there any types or patterns of trader or intermediary conduct that has occurred in the compute cash markets that raise market risks or challenges and should be monitored closely by trading venues or regulators? How do these risks and challenges compare to cash markets underlying more mature futures products?
  7. 2(g) Appendix C to part 38 provides that a cash-settled derivative contract is readily susceptible to manipulation if the settlement price is not reliable, acceptable, publicly available, and timely, and is computed from a cash market that is sufficiently liquid and not itself readily susceptible to manipulation. Is there a cash price series for compute cash markets that could serve as a reference price that satisfies those criteria? Please describe the series, its computation methodology and governance, and the venues and transaction volumes from which it is derived. What steps should the Commission take, if any, if no such cash price series is available?
  8. 2(h) The Appendix C Guidance addresses the adequacy of deliverable supply and susceptibility to squeezes and corners. What is the estimated deliverable supply for compute at the relevant pricing point or points and how are they measured? Please provide associated data.
  9. 2(i) Are there any other considerations the Commission should take into account with respect to evaluating a DCM’s compliance with the Core Principles in connection with the listing and trading of compute derivatives?
Topic 3 Customer protection of market participants 91 FR 54264 · 5 questions
  1. 3(a) What heightened anti-money laundering and know your customers concerns, if any, are present in the compute markets, as compared to more mature commodities markets? What challenges may introducing brokers, FCMs, and other intermediaries face in implementing a BSA/AML program for compute futures?
  2. 3(b) What customer-protection considerations, such as disclosure requirements arise from offering a compute derivatives contract settling against a geopolitically sensitive commodity, including to retail participants? How do these considerations differ, if at all, from derivatives that settle against other commodities, such as oil?
  3. 3(c) Should the terms and conditions of a compute futures contract be required to include any specific information related to idiosyncratic risks? If so, what are those idiosyncratic risks?
  4. 3(d) What, if any, unique protections and prophylactic measures are appropriate or necessary for the protection of retail users of compute derivatives and markets, including as compared to other derivatives markets?
  5. 3(e) Are there any types of trader or intermediary conduct that are particular to compute cash markets and contemplated compute derivative markets, including any such conduct that may require additional action by the Commission?
Topic 4 Perpetual compute futures 91 FR 54264 · 2 questions
  1. 4(a) Would perpetual compute futures have advantages for market participants over "traditional" or "fixed date" futures contracts? Would perpetual compute derivatives provide commercial risk management features that cannot be met with existing products?
  2. 4(b) Would perpetual compute derivatives pose any unique risks for market participants or the broader markets? Are there additional protections or safeguards that the Commission or exchanges should adopt to mitigate risks associated with these products?

05 How to file a comment on the compute derivatives RFC

  • The comment period closed on October 20, 2026.
  • Every submission carries the reference line "Request for Comment on the Listing of Compute Derivatives Contracts" and RIN 3038-AF77.
  • File once, by one method. The Commission encourages regulations.gov. Mail or hand delivery goes to Christopher Kirkpatrick, Secretary of the Commission, Three Lafayette Centre, 1155 21st Street NW, Washington, DC 20581.
  • Comments are public on receipt. Confidential material needs prior contact with the Office of General Counsel and a request under 17 CFR 145.9.
  • Comment is invited "on all aspects of the compute markets (including those not mentioned herein)".

06 Sources