Related compute markets
Kalshi Compute Markets: Event Contracts and Futures Plans
Kalshi’s public API lists binary event contracts on a B200 rental-price index, reported as “active” when read on Oct 23, 2026; whether they can be traded now is not established here. Kalshi’s announcement calls its GPU forward curves a pricing benchmark derived from its own market data and says they are not tradeable assets; this site classes them as a derived data product. A comment letter from Kalshi entities to the CFTC is dated October 20, and the company’s roadmap lists compute futures that are subject to regulatory approval. Those are four different kinds of record. None of them is one of the four futures tracked on this site, none shows a futures approval, and none is a GPU rental price.
Updated
Sources & update history
- Maintained by
- Compute Futures Data
- Page updated
- · edit of the page’s own text
- Scope
- An editorial profile, outside the four-contract data set; it adds no contract and shows no market data.
Four kinds of record, kept apart
A single headline can carry all four at once. They differ in what they are, who produced them and what they show, so each gets its own status here, and none inherits another’s.
-
Event contracts · observed
API reports active · observed Oct 23, 2026 UTC
An event contract: each strike market resolves to Yes or No, with a $1 settlement value.
Not a futures contract, a rental price, or the same exposure as a tracked CME or ICE contract.
-
Forward curves · data product
Data product · not tradable per Kalshi
A derived data product, described by its publisher as not itself tradable.
Not an executable forward contract, a current cloud rental quote or a settlement benchmark approved for CME or ICE.
-
Comment letter · consultation
Letter dated Oct 20, 2026
A reply to the CFTC’s category-wide request for comment on compute derivatives.
Not a product-specific relisting application, a CFTC approval or permission to trade a new futures product. The letter date is not a receipt or posting date, which were not captured.
-
Futures · planned
Planned · subject to regulatory approval
A proposal on a company roadmap.
Not a launched product, a product-specific application with a known status, or any existing event-market ticker.
Schematic · illustrative, not data
Three different numbers
A rental-price index, an event contract and a derived curve answer different questions and use different units. None of them is converted into another on this site.
1 · Rental-price index
A price level
Unit: USD per GPU-hour
A provider’s measurement of what renting a GPU costs. The tracked CME and ICE futures settle on the average of a named index over the contract month.
It is a level in dollars, not a yes/no question and not a forecast.
2 · Event contract
A price for a yes/no outcome
Unit: dollars between $0 and $1 per contract
A binary question about an index, such as whether a month’s average ends above a stated threshold. It settles at $1 if Yes and $0 if No; its trading price is the market’s price for that outcome.
Not a futures contract, and not a GPU rental price.
3 · Derived forward curve
A data product built from many such prices
Unit: none set by a settlement rule
Kalshi describes its GPU forward curves as derived from the prices of many threshold markets, and as not itself tradable. This page draws no curve and shows no values.
Not an executable forward contract, a current rental quote or a settlement index.
The same distinctions are used on Benchmarks and in the beginner guide. The dated documents appear on the Compute Futures Timeline in their own lane.
Event contracts observed in public records
Kalshi’s API publishes records for two B200 series. Each names Ornn as its settlement source, and each links the same generic terms and certification documents. The series are different questions asked at different frequencies:
-
B200 Weekly · series KXB200WS
A weekly series of binary threshold questions about a B200 rental-index value. Its settlement source is named in the series record as Ornn.
Series record observed · Oct 23, 2026 UTC
-
B200 Monthly · series KXB200MS
A monthly series of binary threshold questions. The October 2026 event asks whether the month’s arithmetic mean of hourly B200 rental-index values, as reported by Ornn, is above each of 19 stated thresholds.
API reports active · observed Oct 23, 2026 UTC
The contract template says the contract is an Event Contract with a threshold-based outcome and a $1 settlement value, and the October B200 Monthly records say a Yes outcome needs the month’s arithmetic mean of hourly values reported by Ornn to be above the stated threshold. The template is generic: its certification cover letter is dated November 26, 2025, and nothing in it is specific to GPUs.
What a bounded public-record sample showed
Five unauthenticated requests to documented public endpoints were made while preparing this page, summarised in four rows. Each row says when, what came back, how much of the record it covered and what it does not establish. A retrieval is not market history, and it is not shown as an event on the timeline. Prices, volumes and open interest in these records are not published here.
-
· 2026-10-23 01:14 UTC
Two series, B200 Weekly (KXB200WS) and B200 Monthly (KXB200MS), each naming Ornn as its settlement source and linking the same generic terms and certification documents.
- Method
- Two unauthenticated GET requests to documented series endpoints.
- Scope
- Two series records, requested once each.
- Not established
- Does not establish that the named source’s series, configuration or methodology is the one behind any tracked CME or ICE contract: a shared provider name does not prove the same exposure.
-
· 2026-10-23 01:14 UTC
Five binary records for a later event (April 2027), each reported active, with a continuation cursor.
- Method
- One GET for the first five open records of the monthly series.
- Scope
- An incomplete page of a single later event.
- Not established
- Does not establish anything about the whole series, its other months or its activity.
- Sources
- K13
-
· 2026-10-23 01:15 UTC
Nineteen binary threshold records, each reported by the API with status “active”.
- Method
- One GET for all markets of the event KXB200MS-26OCT (empty continuation cursor).
- Scope
- One event, in full. The market page for it exists (K08).
- Not established
- Does not establish that every Kalshi compute product is active, that an account can place an order now, that matching and settlement are operating at any instant, or any regulatory approval.
-
· 2026-10-23 01:16 UTC
Three distinct venue-reported trade identifiers, dated Sep 16, 2026 (21:51 UTC, 5:51 pm EDT).
- Method
- One GET for three public trade records of one strike market of the October event.
- Scope
- A three-record sample for one strike market.
- Not established
- Does not establish a first-ever trade date, a trade on Oct 23, an independent audit of the venue’s reporting, or present liquidity.
- Sources
- K15
How the observations are labelled
“API reports active” says what the venue’s record said when read. “Historical venue-reported trades observed” says an inspected three-record sample was dated September 16. Neither is shown as a “live” or “verified” badge, and neither says anything about an individual reader’s access.
Forward curves: a derived data product
On Kalshi announced GPU compute forward curves. In its description the curves are derived from the prices of many threshold markets, they are not themselves tradable, and the tradable part is the set of underlying markets on its exchange.
What it is not. Not an announcement of a futures contract, and not evidence that any market was active on that date or of when the first one opened. Kalshi’s October research paper says its GPU event markets date from March 2026; no exact March day is established here, so none is stated. The announcement is entered on the timeline.
Sources: K01, K02, and for the March statement K06. This page draws no curve and shows no curve values.
The October 20 comment letter
A 13-page letter from Kalshi entities, dated October 20, 2026, responds to the CFTC’s category-wide request for comment on compute derivatives (comment CFTC-2026-1850-0090, RIN 3038-AF77). Its Sections II and III discuss contract standards and perpetual futures.
What it is not. Not a product-specific relisting application, a CFTC approval or permission to trade a new futures product. The letter date is not a receipt or posting date, which were not captured. The consultation it answers is the same category-wide request for comment shown on the regulatory status page and the timeline; its published deadline was October 20, and a deadline records no outcome.
Dates that must not be merged
- Letter date
- · stated on the first page of the letter.
- News report
- · an Axios report found through search; its body could not be retrieved, so nothing here is taken from it (K09).
- Received · posted
- Not captured. The official record refused automated access, so the CFTC’s receipt and posting dates are unknown here.
- Text read
- (UTC day) · in a publicly hosted copy, not the government original.
- Comment deadline
- · the request for comment’s own published date, a separate fact from the letter’s date.
Where the letter text comes from
The official comment page (K03) and its attachment (K04) answered automated requests with HTTP 403; the restriction was not bypassed. The 13 pages were read through a publicly hosted copy (K05). Whether that copy is byte-identical to the government attachment is unverified, and no digest of an original is held. Official search metadata corroborates the comment identifier CFTC-2026-1850-0090. Until an original copy is obtained, anything drawn from the letter carries this limit.
Planned futures
Kalshi’s October 2026 research paper says its GPU event markets date from March 2026 and places compute perpetual and dated futures on a roadmap subject to regulatory approval.
-
Compute perpetual futures
Planned · subject to regulatory approval
A staged roadmap item in Kalshi’s October research paper, described as subject to regulatory approval. The comment letter discusses perpetual futures in general (Section III).
Not a launched product, a product-specific application with a known status, or any existing event-market ticker.
-
Compute dated futures
Planned · subject to regulatory approval
A staged roadmap item in the same paper, likewise described as subject to regulatory approval.
Not a launched product, or a contract with a published specification or a filing status established here.
What it is not. Not a CFTC decision. No exact March day or publication day is established. Whether a separately identifiable filing exists for either product, and its entity, mechanism, status and date, is an open question below, not something the comment letter answers. Sources: K06, K05.
Next to the four tracked futures
The site’s tracked set stays four cash-settled futures, sized in GPU-hours, whose final settlement is an average of a named index over the contract month: GPU1 (NYMEX), GPU2 (NYMEX), HPR (ICE Futures U.S.), and BKL (ICE Futures U.S.). Their rows, counts, status dimensions and the CME-versus-ICE comparison are unchanged by this page.
- Different instrument. A Kalshi event contract pays $1 or $0 on a stated outcome; a tracked future settles to an average index level multiplied by a GPU-hour quantity. Binary contracts are not added to the futures table.
- Different evidence. The futures rows rest on the frozen data edition and its dated check days. This page rests on its own ledger, with its own observation instants, and does not move any of those dates.
- A shared provider name is not a shared index. Ornn is named by Kalshi’s B200 series and, for ICE’s contracts, as an index administrator on the Benchmarks page. The exact series, configuration and methodology version behind each are not mapped to one another here, so no equivalence and no numerical comparison is made.
What you can and cannot conclude
Each pair is a conversion that sounds natural and is not supported by the records.
| If you see | You can say | You cannot say |
|---|---|---|
| The public API reports a Kalshi compute market as “active”. | The venue’s record, read on the day shown, listed the market with that status. | Does not mean the CFTC approved the market, that every Kalshi compute product is active, or that an order can be placed now. |
| A Kalshi comment letter dated October 20 answers the CFTC’s request for comment. | Kalshi entities addressed the category-wide consultation, and the letter says what its own text says. | Does not mean Kalshi filed a product-specific relisting application or that the CFTC approved anything, and does not establish when the CFTC received or posted it. |
| A Kalshi certification document dated November 26, 2025. | A generic index-value contract template was notified to the CFTC under Regulation 40.2 on that cover date. | Does not make it a GPU-specific approval, and its date is not a GPU listing date. |
| Three public trade records for one October 2026 strike market, dated September 16. | The venue reported at least those three trades on that date. | Does not establish a first-ever trade date, a trade today, an audited record or present liquidity. |
| The price of a Kalshi event contract. | It is the market’s price for a $1 payout if the stated outcome occurs. | Does not make it a GPU rental price or a forward price for GPU-hours. |
| Kalshi’s B200 series and ICE’s contracts both name Ornn. | The same index provider is named in both sets of documents. | Does not show that they use the same series, configuration or methodology version, or that the exposures are equal. |
| A source that answered “403 Forbidden” to an automated request. | It could not be read in this research, and the page says so. | Does not mean the source says nothing, that a filing does not exist, or that its public copy is identical to it. |
Still unresolved
- What does the official comment attachment say, and when did the CFTC receive and post it? The page, its attachment and the receipt and posting metadata refused automated access. The letter is read from a public copy whose identity with the original is unverified.
- Is there a separately identifiable filing for compute perpetual or dated futures? The comment letter answers none of the product-specific questions: the legal entity, filing mechanism, product, status and date.
- Can the markets actually be accessed and traded now? An API “active” status and a historical trade sample are not a record of current access or liquidity. A read-only public record check would be enough; no account or trade is needed.
- Which exact Ornn series, methodology and version does each Kalshi product use, and how does that compare with ICE’s? Without that mapping, no benchmark equivalence or numerical comparison across venues is made.
- May market quotes, volumes or charts be republished? The site’s market-data policy keeps them off, and public API access is not a redistribution grant.
Found a primary source that answers one of these? Send it through the corrections policy.
Sources
Sources use their own numbers, K01–K17, which are neither the data snapshot’s S-numbers nor the timeline’s TH-numbers. Each one says how it was obtained, including where access was refused or only a copy could be read, and what it does and does not establish. The saved responses are private; each is held with its retrieval time, size and SHA-256 so the reading can be checked.
-
K01 Kalshi announcement of GPU compute forward curves (opens in a new tab)
Kalshi · document dated
- How it was obtained
- Read. Read in the editorial research and re-checked on Oct 23, 2026 for its date and for the sentence that separates the curves from the tradable underlying markets.
- What it establishes
- Establishes what Kalshi announced and how it describes the curves. It does not show when any underlying market first opened, that any market was active on the announcement date, or any approval.
-
K02 Kalshi explainer on how a GPU compute forward curve is derived (opens in a new tab)
Kalshi · document dated
- How it was obtained
- Read. Read in the editorial research; not re-retrieved for this edition. Marketing superlatives in it are not adopted.
- What it establishes
- Describes threshold markets and the derivation of a curve. It is the company’s own description, not an independent finding.
-
K03 Comment CFTC-2026-1850-0090 on regulations.gov (opens in a new tab)
U.S. Commodity Futures Trading Commission (docket record)
- How it was obtained
- Official metadata only · page refused automated access. The comment identifier and attachment title were visible in the official search metadata. The record’s own page returned HTTP 403 to automated requests, including on Oct 23, 2026, and was not bypassed.
- What it establishes
- Corroborates that a comment with this identifier exists. Receipt and posting dates were not captured.
- Used by
- act-20261020-comment-letter
-
K04 Official attachment of comment CFTC-2026-1850-0090 (PDF) (opens in a new tab)
U.S. Commodity Futures Trading Commission (docket record)
- How it was obtained
- Requested and refused (HTTP 403) · not read. Requested on Oct 23, 2026 and refused with HTTP 403; access restrictions were not bypassed. No original bytes and no government-origin digest are held.
- What it establishes
- Not read. Whether the copy read as K05 is byte-identical to this attachment is unverified.
-
Kalshi entities, via a copy hosted by a third-party newsletter · document dated
- How it was obtained
- Read in a public copy · original not obtained. The 13-page text was read through web retrieval from a publicly indexed copy linked from the newsletter article above. The page is linked, not the copy’s own address, which is a temporary object URL. This is a reading of a copy, not an archived original; no PDF digest is claimed.
- What it establishes
- The first page states October 20, 2026, RIN 3038-AF77 and the three Kalshi entities; Sections II and III discuss contract standards and perpetual futures. The letter date is not a receipt or posting date. It is a response to a category-wide request for comment, not a product-specific application.
-
K06 Kalshi research paper on AI infrastructure markets (19 pages) (opens in a new tab)
Kalshi Research · document dated
- How it was obtained
- Read. Full text read in the editorial research and one figure (PDF p. 3) inspected; not re-retrieved for this edition. The exact publication day is not shown on the cover.
- What it establishes
- Establishes the company’s staged roadmap, including that GPU event markets date from March 2026 and that compute perpetual and dated futures are subject to regulatory approval. It is not a CFTC decision. No exact March day is stated or inferred.
-
K07 Kalshi API documentation: get series (opens in a new tab)
Kalshi
- How it was obtained
- Read. Read in the editorial research.
- What it establishes
- Documents the public metadata endpoint used for the observations. It is not a grant to redistribute market data.
- Used by
- prd-b200-weekly, obs-series-metadata
-
K08 Kalshi market page: B200 Monthly, October 2026 (opens in a new tab)
Kalshi
- How it was obtained
- Read. Read in the editorial research. Quotes from the page are not reproduced.
- What it establishes
- Shows that the page exists. It does not show that an account can place an order or that matching and settlement are operating at any instant.
- Used by
- prd-b200-monthly, obs-october-event
-
K09 Axios report on Kalshi compute contracts and the CFTC (Oct 22, 2026) (opens in a new tab)
Axios · document dated
- How it was obtained
- Search result only · body not retrieved. Found through search; the full article could not be retrieved, so only its existence and headline framing are relied on.
- What it establishes
- Reported news context only. Its framing is not this site’s classification of any product, and nothing on this page is taken from its body.
- Used by
- act-20261020-comment-letter
-
K10 CCIR directory of CFTC compute-derivatives documents (opens in a new tab)
CCIR
- How it was obtained
- Read. Used only to corroborate the comment identifier and its scope. Its summaries, collection counts and participant list are not imported.
- What it establishes
- A discovery aid, not an authority for the letter’s conclusions.
- Used by
- act-20261020-comment-letter
-
K11 Kalshi API: series KXB200WS (B200 Weekly) (opens in a new tab)
Kalshi
- How it was obtained
- Public record retrieved · saved privately with a digest. Unauthenticated GET to a documented public endpoint on Oct 23, 2026. The response is held privately with its digest.
- Retrieval record
- Oct 23, 2026 · 01:14:09 UTC · 824 bytes · SHA-256 1c7ae523033cbb58…
- What it establishes
- Series metadata only: title, frequency, a named settlement source (Ornn) and links to generic terms and certification documents.
- Used by
- prd-b200-weekly, obs-series-metadata
-
K12 Kalshi API: series KXB200MS (B200 Monthly) (opens in a new tab)
Kalshi
- How it was obtained
- Public record retrieved · saved privately with a digest. Unauthenticated GET to a documented public endpoint on Oct 23, 2026. The response is held privately with its digest.
- Retrieval record
- Oct 23, 2026 · 01:14:09 UTC · 839 bytes · SHA-256 a2ced2b38bf803ed…
- What it establishes
- Series metadata only, as for K11.
- Used by
- prd-b200-monthly, obs-series-metadata
-
K13 Kalshi API: first page of open markets in series KXB200MS (opens in a new tab)
Kalshi
- How it was obtained
- Public record retrieved · saved privately with a digest. Unauthenticated GET limited to five records on Oct 23, 2026. A continuation cursor was returned, so this is an incomplete sample.
- Retrieval record
- Oct 23, 2026 · 01:14:55 UTC · 9,298 bytes · SHA-256 77d4a4e563a0b492…
- What it establishes
- Five records for a single later event (April 2027) were returned. No inference about the whole series, its other months or its activity is drawn from them.
-
K14 Kalshi API: markets of event KXB200MS-26OCT (B200 Monthly, October 2026) (opens in a new tab)
Kalshi
- How it was obtained
- Public record retrieved · saved privately with a digest. Unauthenticated GET on Oct 23, 2026. The continuation cursor was empty, so all records of this one event were returned.
- Retrieval record
- Oct 23, 2026 · 01:15:43 UTC · 35,257 bytes · SHA-256 fe8b3b737152a384…
- What it establishes
- Nineteen binary threshold records for a single event, each reported with status “active”. Nineteen strikes are not nineteen providers or nineteen futures, and a reported status is not an approval.
- Used by
- prd-b200-monthly, obs-october-event
-
K15 Kalshi API: public trade records for one October 2026 strike market (opens in a new tab)
Kalshi
- How it was obtained
- Public record retrieved · saved privately with a digest. Unauthenticated GET limited to three records on Oct 23, 2026. Three distinct venue-reported trade identifiers were returned, all dated Sep 16, 2026 (21:51 UTC, 5:51 pm EDT).
- Retrieval record
- Oct 23, 2026 · 01:16:16 UTC · 964 bytes · SHA-256 f77c8f9a96c5a9c7…
- What it establishes
- The execution timestamp is the venue’s report, not independently audited. A three-record sample does not establish a first trade, a trade on Oct 23 or present liquidity. Prices and quantities are not published here.
- Used by
- prd-b200-monthly, obs-trade-sample
-
K16 Kalshi contract terms: INDEXVALUE (opens in a new tab)
Kalshi
- How it was obtained
- Public record retrieved · saved privately with a digest. Linked by the series records; retrieved on Oct 23, 2026 and its text extracted. No visual inspection of the downloaded pages is claimed.
- Retrieval record
- Oct 23, 2026 · 01:14:55 UTC · 29,913 bytes · SHA-256 cc6e0724308d5956…
- What it establishes
- A generic template: it identifies an Event Contract, a threshold-based outcome and a $1 settlement value. Market-specific rules must be read with it.
- Used by
- prd-b200-weekly, prd-b200-monthly
-
K17 Kalshi product certification: INDEXVALUE (Regulation 40.2 notification) (opens in a new tab)
KalshiEX LLC, submitted to the CFTC
- How it was obtained
- Public record retrieved · saved privately with a digest. Linked by the series records; retrieved on Oct 23, 2026 and its text extracted. No visual inspection of the downloaded pages is claimed.
- Retrieval record
- Oct 23, 2026 · 01:14:55 UTC · 267,251 bytes · SHA-256 56bc4c50af5a3bda…
- What it establishes
- A generic index-value template whose cover letter is dated November 26, 2025 (its signature block carries a different date). It is not an October 2026 GPU-specific approval, and that date is not a GPU listing date.
- Used by
- prd-b200-weekly, prd-b200-monthly
About this page
- Edition. Related-markets ledger cfd-related-markets-2026-10-23, version 1.0.0, prepared . Public records and documents were read on (UTC day). It is a bounded research sample, not a census of Kalshi’s markets and not a real-time record.
- Separate from the data edition. The four-contract data edition, its check dates and its facts are not changed by this page. Rebuilding the site does not renew any check date.
- No market data. This site shows no prices, settlement prices, volume or open interest, for any venue. Public access to a venue’s API is not a licence to republish its data, so none is copied here.
- Independence. Not affiliated with Kalshi, Ornn, CME Group or ICE. Not investment advice, and not an offer to trade or a way to open an account.
Found an error? See the corrections policy. How to read dates and evidence: methodology.