Metadata only — market data is not displayed on this site

Independent · Not investment advice

Methodology

How to read this site

Every fact on this site is a dated record with its own state and, where recorded, its source references and their limitations. This page explains what those labels mean and what the current edition does — and does not — establish.

New to compute futures? Start with Compute Futures Explained, a plain-English guide that uses the same labels.

Updated

Sources & update history
Page updated
· targeted ICE source check; baseline values and other checks are unchanged
Also changed
· edit of the page’s own text
CME source follow-up
· targeted CME source check; baseline values and other checks are unchanged
Contract data baseline
· the data panels on this page follow it · How dates work
Baseline scope
Four contracts (GPU1, GPU2, HPR, BKL); metadata only, no market data. Each fact keeps its own verification date; a page update is not a re-review of market facts.

Scope

The site tracks four exchange futures on GPU rental-price indexes: GPU1 and GPU2 filed by NYMEX (CME Group), and HPR and BKL with published specifications on ICE Futures U.S. (Intercontinental Exchange). It records metadata and evidence — status, terms, settlement series, platform-support records — in dated editions. The current edition is dated Oct 8, 2026 and was updated Oct 8, 2026 at 4:15 am EDT; each fact keeps its own check date.

It does not show live market data, take orders, provide accounts or give investment advice. Nothing on the site updates automatically between editions.

The counts below describe that frozen data set and nothing else. Editorial pages, such as the timeline and the Kalshi compute markets profile, keep their own versioned ledgers, sources and dates beside it. They do not change a count, a fact or a check date here, and a record in them is not a fact in this set.

Size of the current snapshot
In this snapshotCount
Contracts4
Recorded facts (contracts, benchmarks, access records, events)190
Evidence references254
Sources20
Open questions13

Three status dimensions, kept apart

A contract’s status is not one label. The site records three facts separately and never derives one from another:

  • Regulatory status — what a regulator’s record says, such as the CFTC’s “Approval Pending” for GPU1 and GPU2.
  • Listing and launch — whether the exchange has published terms, a calendar or a launch date. CME lists the launch date as TBD; ICE publishes specifications and expiry calendars.
  • Trading evidence — whether a production trade has been verified. None has, for any contract; that is an evidence assessment, not a claim that no trading occurred.

Organizations are also kept apart: NYMEX is a legal exchange within CME Group, and ICE Futures U.S. is a legal exchange within Intercontinental Exchange. A group is not the exchange, an execution platform is not a broker, and a clearing venue code is not a mapped legal clearing entity. See Regulatory status and Market access roles.

Knowledge and publication states

Each fact has a knowledge state — how much the checked sources establish — and a publication policy — what the site does with it.

Knowledge states and how many of the 190 facts are in each
StateMeaningFacts
Confirmed — shown as “Verified” with a dateAn accepted value or assessment in this snapshot, with its recorded evidence basis and verification date. It may be stated directly by a source, or be an explicitly labelled site classification or assessment based on the sources.144
Not confirmedSources were checked but did not establish the value. The field stays empty; it is not zero, absent or a negative finding.44
Under clarificationSources, or sections of one source, disagree. The value is withheld and the conflicting statements are shown.2
Not found in checked sourcesThe checked sources do not contain the field. This describes the checked scope, not whether the information exists.0
Not published by the sourceThe issuer has not published the value. It is not inferred from elsewhere.0
Not applicableThe field does not apply to this contract or record.0
Publication policies
PolicyMeaningFacts
PublishThe value is shown, with its evidence.144
Show as unknownThe field is shown with an explicit “Not confirmed” label and the sources that were checked.44
WithholdA value exists in some form but is not safe to normalize, so it is not shown or used in comparisons. Withheld is not zero.2

Unknown is never zero

An empty, unconfirmed or withheld field is shown as such. It is never filled with zero, copied from another contract, or turned into a negative statement such as “not approved” or “no trading”.

Confirmed is not the same as quoted

The knowledge state says whether a value was accepted for this snapshot; the evidence basis says how. Of the 144 confirmed facts, 134 are stated directly in a primary source and 10 are the site’s own classifications or assessments based on the sources. Those carry a “site classification” or “site assessment” label in their evidence: the listing classifications (“Specifications published” for ICE; “postponed”, shown as “Launch date TBD”, for CME), the classification of CME’s terms as filed proposed terms, and the trading-evidence assessments.

A confirmed assessment can itself be negative about the evidence. Each contract’s trading-evidence assessment is confirmed with the value “not confirmed”: the site has accepted that no production trade was verified in the sources checked. That is not evidence of a trade, and not a statement that no trading occurred.

On the page, chips summarize the state: Verified Oct 5, 2026 or Site classification · verified Oct 5, 2026 appears only inside evidence panels, Not confirmed marks unknowns and Under clarification marks conflicts or withheld values.

Dates, times and their scopes

Different dates answer different questions and are labelled separately in every evidence panel and in each page’s own line. Five kinds are kept apart:

  • Edition times are exact instants, stored in UTC and shown in US Eastern time (America/New_York), with EDT or EST as it applies to that instant. This data edition was prepared Oct 8, 2026 at 4:15 am EDT: the instant its content was frozen, not the time the site went live. The edition date is the Eastern calendar date of that instant, so it can differ from the UTC date by a day.
  • Page dates describe a page’s own text, not its data. “Published” and “Last edited” appear only where they can be attested, and a missing date means none is claimed. A page built from the data says “Page last changed” only when the data edition changed something that page presents; otherwise it says it did not change. A new edition does not make an unchanged page “updated”, and a rebuild or a monitor observation never does.
  • Check dates — source checked, fact checked and fact verified — are UTC calendar days, recorded to the day with no clock time. They are not converted to Eastern time. A UTC check day can be one day later than the Eastern edition date without being in the future.
  • Source dates — document, expiry, first-trading, deadline and effective dates — are calendar dates as the source states them. They are never converted between timezones, and a date-only deadline gives no closing hour.
  • Trading schedules keep the exchange’s own clock: Central time (America/Chicago, CT) for CME’s filed hours and the Eastern time (ET) stated on ICE’s product pages. No live market-open clock is shown.
Page last changed / Last edited
Two different statements. “Page last changed” is the recorded instant of a data edition or dated source follow-up that changed what the page presents. A source follow-up does not advance the data edition or unrelated fact checks. “Last edited” is the day a page’s own wording last changed. When a page has more than one of these, it states the latest by Eastern calendar day (on the same day, the exact instant) and names the others; a date-only value and an instant are compared only after both are placed on the Eastern calendar, never by UTC day. A navigation or footer link is not an edit. The same value appears in the page’s structured data, and none of this changes the data edition or any fact’s own check dates.
Edition date
The Eastern date of this edition: Oct 8, 2026. “Upcoming at snapshot” compares source dates with this date, never with today’s date.
Source document date
A date the document itself carries, such as a letter date. Shown only where recorded; many live web pages have none.
Report, receipt and posting dates
For editorial records about a filing: the date of a news report, the date a regulator received a submission and the date it posted it are three further dates, each separate from the document’s own. When one is not captured it is shown as not captured, never filled in from another.
Observation instant
The moment a public record was read, such as a venue’s API response. It says when the record said what it said. It is not an event date, it is not shown on the timeline, and a venue-reported status at that moment is not a regulatory status.
Source checked (UTC day)
The day the source copy behind the recorded facts was retrieved and read. It does not verify every field in that source.
Fact checked (UTC day)
The day of the source evidence a particular field was checked against, whatever the outcome.
Fact verified (UTC day)
Only for confirmed facts: the day of the evidence the accepted value rests on. Unknown facts have no verification date.
Effective date
When the fact took effect according to its source, where stated — otherwise “Not known”.
This edition
Only on facts re-reviewed for an edition: that edition, when the review finished and when the saved source copy it used was retrieved, both shown in Eastern time. Re-reading a saved copy does not move the fact’s check date.
Attachment read
An exact Eastern-time instant recorded on a source attachment such as a PDF. It says when the attachment was read, not when it was published, and it never moves a fact’s check date.
Notice date
A date a source’s landing page prints as its notice date, recorded as a labelled page date. It is not a document date and not a revision time of the attachment.

Partial refresh

This edition re-reviewed no fact from saved source copies, and no source was retrieved again for it. All facts keep their earlier check dates; the edition date is not a verification date. The Oct 6, 2026 edition re-reviewed 15 facts and 5 source records (S4, S13, S17, S18, S20); those reviews are carried over unchanged and stay marked with that edition.

This edition also records one source attachment: Revised advisory 26-274, PDF attachment (S3-A1, part of source S3). It was read at Oct 7, 2026 at 12:45 am EDT; it is cited by 6 facts alongside the landing-page reference, as the same notice rather than an independent confirmation. The landing page labels a notice date of Sep 25, 2026 (Notice Date, landing-page label). The attachment’s own revision time is not confirmed. Reading it did not change any fact’s value, state or check date.

Automated monitoring

A separate source monitor, which is not part of this dataset and never edits it, compares stored snapshots of selected public pages with their latest versions on a daily or weekly schedule and queues differences for review. Its reach is limited and defined: it reads only the parts of each page it is set up to extract, its checks of exchange filing and notice lists cover titles only, and some sources, among them CME’s revised clearing advisory and its attachment, are not monitored automatically because their terms bar automated access. A detected change is a prompt to look, not a verification.

The monitor does not re-verify facts, move any check, verification or effective date, change a data edition or update this site. Those change only through a recorded review and a new data edition. A monitor observation is never shown as the date of a fact or of a page.

Source-specific exceptions

  • Trading Technologies’ update dates its CME Compute Futures section October 2, 2026. That section date is recorded as the announcement date; the update as a whole has no recorded document date, and none is inferred.
  • ICE’s generated specification PDFs display a date that can change each time the PDF is generated. It is not treated as a publication or rule effective date.
  • CME’s revised clearing advisory 26-274 lists the trade date and initial contracts as TBD. Its landing page labels a Notice Date of Sep 25, 2026; that is a page label, not a date printed in the PDF. Both pages of the PDF attachment were read on Oct 7, 2026 at 12:45 am EDT; no separate PDF revision timestamp is confirmed, and no actual launch date is stated.
  • Build times and page-generation times are never shown as verification dates.

Evidence, locators and source families

Every evidence panel lists, for each displayed fact, each recorded source reference on its own: title, link, locator, role, upstream relation, check date, document date where recorded, and the source’s limitation. Sources are not grouped under one link. A fact with no recorded reference says so instead.

From source to displayed fact

Five-step diagram of how a source becomes a displayed fact, via claim, evidence and date records
How a source document becomes a value on a page, as described on this page. It explains existing editorial rules; it is not a schedule of checks, and nothing is re-checked automatically. Open the full-size image (PNG).
Text of the image

How evidence becomes a displayed fact — The editorial path behind every value on this site (edition counts)

Five steps

  • 1. Source: A regulator, exchange, index-provider or platform document, linked live. More on source

    • 20 sources in the registry

    • Source checked: a UTC day

  • 2. Field claim: One fact for one field of a contract, benchmark, access record or event. More on field claim

    • 190 recorded facts

  • 3. Evidence reference: Each reference records its source, locator and role. More on evidence reference

    • 254 references: 150 with a fact-level locator, 104 source-level

    • Supports this fact (184)

    • Checked context — does not confirm a value (69)

    • Corroborates this fact — not the governing source (1)

    • 11 facts have no reference and say so

  • 4. Dates and knowledge state: Fact checked and fact verified are UTC days; source dates stay as published. More on dates and knowledge state

    • Confirmed: 144

    • Not confirmed: 44

    • Under clarification: 2

  • 5. Displayed fact: The value with its evidence panel, or a state label instead of a value. More on displayed fact

    • Verification dates appear inside evidence panels, never as a page-wide badge

    • Not confirmed

    • Under clarification

  • Unknown is never filled with zero, copied from another contract or turned into a negative.

  • A monitor flags source changes; it does not re-verify facts.

Counts from the Oct 8, 2026 edition. · computefuturesdata.com

Reference roles

The edition holds 254 evidence references. Each is shown in one of these roles:

  • Supports this fact (184 references) — the source states the value or, for a labelled site classification or assessment, provides the evidence it rests on. It does not mean the source uses the site’s wording.
  • Checked context — does not confirm a value (69 references) — the source was checked for the field but did not establish it. A recorded position on such a reference says where the field was looked for; it does not establish an unknown value.
  • Corroborates this fact — not the governing source (1 reference) — a checked position that states the same value as the governing source. One rule uses this today: the CFTC comment deadline rests on the CFTC Innovation tracker (S5); footnote 3 of the NYMEX review-extension letter (S4) corroborates it, while S4 remains the supporting source for the review-extension dates themselves.

Upstream relations before this display rule: 185 “supports” and 69 “checked context”. Each panel shows the upstream relation next to the displayed role.

Locators

A locator points to the position of a fact in a source, such as a PDF page and section (150 references). A source-level locator describes the source as a whole and carries the note “Fact-specific position not recorded in this snapshot” (104 references). 11 facts have no source reference at all; they show that plainly instead of a borrowed link.

Source families

Some documents are versions of one publication. ICE HPR product page and generated PDF (S6 and S12) count as one family. ICE BKL product page and generated PDF (S7 and S13) count as one family. Each document keeps its own link and locator, but a family is never presented as two independent confirmations.

Coverage and limits

  • Partly reviewed lists. ICE Futures U.S.’s rule-filing and notice lists are dynamic. Only the first page of the exchange’s rule-filing and notice lists was reviewed (as shown on Oct 5, 2026). The ICE regulatory status is therefore “not established in the sources checked” — not a finding that no filing or approval exists.
  • Live links, no archive. Complete copies of the source documents are not archived or republished with the data. Links and locators point to the live public documents, which can change after their check dates. For evidence re-reviewed in an edition, the retrieval time and a digest of the saved copy are recorded. A source attachment that was read once (such as the CME advisory PDF) is recorded with its read time and page locators but no digest, because its bytes were not saved.
  • How facts were reviewed. Facts were checked source by source with agent-assisted review. No dedicated human sign-off is recorded for this snapshot.
  • Editorial records outside this data set. The Kalshi profile and the timeline rest on their own typed ledgers (records, actions, observations and sources), validated at build time but not part of the frozen data edition or the source registry below. Each source there says how it was obtained, including a refusal (HTTP 403) or a reading of a public copy rather than the original.
  • What validation proves. The build checks the data for internal consistency and publication rules before any page is produced. That is not proof of tradability, legal status or redistribution rights.
  • A monitor flags changes; it does not re-verify. A separate source monitor compares selected public pages with stored snapshots on a schedule and queues differences for review (see “Automated monitoring” under Dates and times). Time-sensitive facts can still go out of date after their check dates, and some sources, such as CME’s revised advisory, are not monitored automatically.

Open questions (13)

  1. Q01ICE’s current product-level regulatory status and regulatory pathway were not established in the sources checked. ICE’s Sep 29, 2026 notice says HPR and BKL will be listed pending completion of the CFTC’s request-for-comment period and that no listing date or timeline has been set; it gives no product-level CFTC status. The expiry calendar’s first trading date (FTD) is a calendar field and does not confirm a launch or a trade. Only the first page of ICE’s rule-filing and notice lists was reviewed, so the absence of a filing or approval cannot be claimed.
  2. Q02No production trade has been verified for any of the four contracts in this edition. Announced dates and calendar fields are not treated as trades, and no volume or open interest is shown. ICE says reference data including hypothetical daily settlement prices is available from Oct 5, 2026 for system development; those values are not trades or production settlements and are not shown. This is an evidence assessment, not a statement that no trading occurred.
  3. Q03ICE’s specification quotes the price in US dollars per contract in one section and gives a minimum fluctuation of 0.001 US dollars per GPU-hour in another. It points to a table in “Resolution 1 to this Chapter 34”, but ICE Futures U.S.’s rulebook chapter list, as checked on Oct 5, 2026, names Chapter 34 “OKX Futures”, so the intended resolution is unresolved. The normalized quote unit, trade-type tick rules and tick value are withheld until the exchange rule or an ICE clarification states them.
  4. Q04ICE contract size is a calendar-period number of GPU-hours. The calendar, timezone and daylight-saving convention for counting those hours are not confirmed, so no monthly quantity is calculated.
  5. Q05At the Oct 5, 2026 check, HPR’s explicit trading-hours text conflicted with a city-time table lower on the same product page. ICE’s page was later updated and the table now shows the same hours (a source follow-up of Oct 23, 2026; the BKL page shows the same table). No normalized session schedule or market-open indicator is shown, because the calendar, holiday and daylight-saving conventions behind the hours are not confirmed in the sources checked.
  6. Q06No exchange or broker margin amount, multiplier or account scope has been confirmed. Reference tables are not converted into customer margin.
  7. Q07The revised CME advisory 26-274 lists the trade date and initial contracts as TBD. Both pages of its PDF attachment were read on October 7, 2026. The advisory’s landing page labels its Notice date September 25, 2026 (recorded from a screenshot of that page); a separate PDF revision timestamp has not been confirmed. The attachment gives no actual launch date, so the launch date stays TBD.
  8. Q08No broker or FCM has a verified product-level record for these contracts, and no account or US jurisdiction scope is established. Not finding public evidence does not mean a provider cannot offer access.
  9. Q09Trading Technologies announced day-one support tied to the original exchange date. Whether that support is deployed now that the launch date is TBD is not confirmed.
  10. Q10The exact benchmark configuration and the methodology version used for settlement are not confirmed for any of the four series.
  11. Q11No market-data display licence is recorded for this site, so price, settlement, volume, open-interest and index-history components are off. This does not mean the market has no data.
  12. Q12CME’s product-specific final payment rule is not confirmed. On ICE’s expiry calendar, FSD is a calendar field and is not treated as the final payment date. No payment date is calculated.
  13. Q13The public pages do not expose a verifiable specification version. This dataset archives no copies of the source documents; retrieval digests are recorded only for the evidence re-reviewed in this edition.

Market data boundary

No site-specific market-data grant is recorded, so prices, settlement prices, volume, open interest and index histories are not displayed, stored or offered for download. A public specification link is not a licence to redistribute data.

  • Price Not displayed
  • Settlement price Not displayed
  • Volume Not displayed
  • Open interest Not displayed

Not displaying market data does not mean the market has no data, or that permission was refused.

Source registry

All 20 sources in the edition. The registry locator describes what part of each source was reviewed; fact-specific positions appear in the evidence panels. Source checks are UTC days: Oct 5, 2026.

  1. S1 CFTC GPU1 product record 62544 (opens in a new tab)

    CFTC · Regulator record

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Organization / Product Name / Status / Date
    Retrieval
    Linked live; no archived copy

    Limitation
    Does not establish a production execution.

  2. S2 CFTC GPU2 product record 62545 (opens in a new tab)

    CFTC · Regulator record

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Organization / Product Name / Status / Date
    Retrieval
    Linked live; no archived copy
  3. S3 CME revised clearing advisory 26-274 (opens in a new tab)

    CME Group · Exchange notice or announcement

    Document date
    No document date recorded
    Landing-page notice date
    — Notice Date as labelled on the landing page; not a document date and not an attachment revision time
    Source checked (UTC day)
    Registry locator (source-level)
    Document title and revised-notice body
    Retrieval
    Linked live; no archived copy

    Attachment S3-A1 · Revised advisory 26-274, PDF attachment (opens in a new tab) (PDF, 2 pages)

    Read (ET)
    · text read and both pages inspected
    Revision time
    Not confirmed
    PDF page 1
    Identifies NYMEX advisory 26-274 and GPU1/GPU2; Listing Date row “Trade Date TBD”; Initial Contracts row “TBD”
    PDF page 2
    Qualifier “Pending All Relevant CFTC Regulatory Review Periods”

    Attachment limitation
    Read once on the observation date; the original PDF bytes were not saved, so no digest is recorded. The PDF carries no separately confirmed revision timestamp, and it states no actual launch date.

    Limitation
    The landing page states the date as TBD. Its revised two-page PDF attachment (S3-A1) was read on 2026-10-07: Listing Date “Trade Date TBD”, Initial Contracts “TBD”, and a pending-CFTC-review qualifier. The landing page labels its Notice date 2026-09-25; that is a page label, not a date printed in the PDF, and no separate PDF revision timestamp is confirmed. No copy or digest of the PDF is archived in this dataset.

  4. S4 CFTC NYMEX review-extension letter (opens in a new tab)

    CFTC · Regulator record

    Document date
    Source checked (UTC day)
    Registry locator (source-level)
    PDF page 1: concluding paragraph and footnotes
    Retrieval
    Linked live; no archived copy

    Limitation
    Deadline is not an approval decision or launch date. Footnote 3 cites the CFTC request for comment (91 FR 54259, August 21, 2026), comment period closing October 20, 2026; that Federal Register document itself was not retrieved.

    This edition · Reviewed for the Oct 6, 2026 edition on Oct 5, 2026 at 11:39 pm EDT, using the saved copy of S4 (retrieved Oct 5, 2026 at 5:28 pm EDT). No new retrieval. Not repeated for the Oct 8, 2026 edition.

  5. S5 CFTC Innovation tracker (opens in a new tab)

    CFTC · Regulator record

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Innovation Tracker, row 08/19/2026
    Retrieval
    Linked live; no archived copy

    Limitation
    Category-wide consultation, not contract-level approval.

  6. S6 ICE HPR official product page (opens in a new tab)

    ICE Futures U.S. · Exchange specification

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Market Specifications headings
    Retrieval
    Linked live; no archived copy

    Limitation
    Quote denominator differs between quotation and fluctuation sections. At the Oct 5, 2026 check a lower city-time table conflicted with the explicit session text; ICE’s page has since been updated and now agrees (source follow-up, Oct 23, 2026).

    Same reference family as S12 — not an independent confirmation.

  7. S7 ICE BKL official product page (opens in a new tab)

    ICE Futures U.S. · Exchange specification

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Market Specifications headings
    Retrieval
    Linked live; no archived copy

    Limitation
    Quote denominator differs between quotation and fluctuation sections.

    Same reference family as S13 — not an independent confirmation.

  8. S8 NYMEX Submission 26-370 (opens in a new tab)

    NYMEX, filed with CFTC · Exchange filing

    Document date
    Source checked (UTC day)
    Registry locator (source-level)
    PDF pp. 2–3 product table; pp. 5–6 Chapters 1045/1047
    Retrieval
    Linked live; no archived copy

    Limitation
    Filed terms are proposed terms while approval is pending. Initial schedule is not a verified current listing.

  9. S9 CME Compute futures overview (opens in a new tab)

    CME Group · Exchange specification

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Getting started with Compute futures
    Retrieval
    Linked live; no archived copy

    Limitation
    Overview is corroboration; specific rules/filings govern.

  10. S10 ICE and Ornn product-program announcement (opens in a new tab)

    ICE · Exchange notice or announcement

    Document date
    Source checked (UTC day)
    Registry locator (source-level)
    May 19 announcement: benchmark and regulatory caveat
    Retrieval
    Linked live; no archived copy

    Limitation
    Historical announcement does not establish current product-level regulatory state.

  11. S11 TT support update: CME Compute Futures (opens in a new tab)

    Trading Technologies · Execution-platform update

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    CME Compute Futures, October 2, 2026; TT Support Status
    Retrieval
    Linked live; no archived copy

    Limitation
    Day-one support promise tied to an old exchange date; not proof of deployed integration or broker-account access.

  12. S12 ICE HPR generated specification PDF (opens in a new tab)

    ICE Futures U.S. · Exchange specification

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    PDF pp. 1–2 field labels
    Retrieval
    Linked live; no archived copy

    Limitation
    PDF displayed date 2026-10-05 is not treated as a rule effective date; shares source family with S6.

    Same reference family as S6 — not an independent confirmation.

  13. S13 ICE BKL generated specification PDF (opens in a new tab)

    ICE Futures U.S. · Exchange specification

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    PDF pp. 1–2 field labels
    Retrieval
    Linked live; no archived copy

    Limitation
    PDF displayed date varies by generation (2026-10-04 at the original snapshot check; 2026-10-05 in the 2026-10-05 21:28 UTC retrieval). It is a generation date, not a publication or rule effective date; shares source family with S7.

    This edition · Reviewed for the Oct 6, 2026 edition on Oct 5, 2026 at 11:39 pm EDT, using the saved copy of S13 (retrieved Oct 5, 2026 at 5:28 pm EDT). No new retrieval. Not repeated for the Oct 8, 2026 edition.

    Same reference family as S7 — not an independent confirmation.

  14. S14 ICE HPR expiry calendar (opens in a new tab)

    ICE Futures U.S. · Exchange calendar

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Expiry Details table, Nov26–Dec27 rows
    Retrieval
    Linked live; no archived copy

    Limitation
    FTD is an exchange calendar field, not evidence of an actual execution. FSD is not automatically final payment date.

  15. S15 ICE BKL expiry calendar (opens in a new tab)

    ICE Futures U.S. · Exchange calendar

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Expiry Details table, Nov26–Dec27 rows
    Retrieval
    Linked live; no archived copy

    Limitation
    Same calendar/actual-execution distinction as S14.

  16. S16 ICE HPR reference margin table (opens in a new tab)

    ICE · Exchange reference table

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Effective Date / Logical Code / Units
    Retrieval
    Linked live; no archived copy

    Limitation
    Retrieved table labels units as MWh. No amount is imported or converted to customer margin.

  17. S17 ICE Futures U.S. Regulation (opens in a new tab)

    ICE Futures U.S. · Exchange regulation page

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Regulation introduction; Rulebook and Rule Filings sections
    Retrieval
    Linked live; no archived copy

    Limitation
    Static HTML exposed only the Energy Forms tab. A headless-browser render (2026-10-05 21:30 UTC) showed the first page of Rule Filings (100 titles, Mar 2 – Oct 5, 2026; titles only) and the Rulebook chapter list. No title on that page mentions compute, Ornn, OCPI or GPU, and the chapter list names Chapter 34 “OKX Futures”. Later pages and generic filings were not opened, so this is not an exhaustive filing search.

    This edition · Reviewed for the Oct 6, 2026 edition on Oct 5, 2026 at 11:44 pm EDT, using the saved copy of S17 (retrieved Oct 5, 2026 at 5:30 pm EDT). No new retrieval. Not repeated for the Oct 8, 2026 edition.

  18. S18 ICE Futures U.S. Notices (opens in a new tab)

    ICE Futures U.S. · Exchange notice or announcement

    Document date
    No document date recorded
    Source checked (UTC day)
    Registry locator (source-level)
    Exchange Notices section
    Retrieval
    Linked live; no archived copy

    Limitation
    Static HTML lacked the notice list. A headless-browser render (2026-10-05 21:30 UTC) showed page 1 of Exchange Notices (100 rows, Feb 4 – Oct 5, 2026), including one compute notice (S20). Later pages and Member and Disciplinary notices were not reviewed, so the absence of another notice cannot be claimed.

    This edition · Reviewed for the Oct 6, 2026 edition on Oct 5, 2026 at 11:44 pm EDT, using the saved copy of S18 (retrieved Oct 5, 2026 at 5:30 pm EDT). No new retrieval. Not repeated for the Oct 8, 2026 edition.

  19. S19 CME original October launch announcement (opens in a new tab)

    CME Group · Exchange notice or announcement

    Document date
    Source checked (UTC day)
    Registry locator (source-level)
    Opening paragraph and product description
    Retrieval
    Linked live; no archived copy

    Limitation
    Historical proposed date is superseded for current launch use.

  20. S20 ICE Futures U.S. Exchange Notice: compute index reference data (Sep 29, 2026) (opens in a new tab)

    ICE Futures U.S. · Exchange notice or announcement

    Document date
    Source checked (UTC day)
    Registry locator (source-level)
    PDF p. 1, paragraphs 2–3
    Retrieval
    Linked live; no archived copy

    Limitation
    States the exchange’s position as of Sep 29, 2026. It sets no listing date, gives no CFTC product-level status for HPR or BKL, and does not show whether a later announcement exists. The reference data it describes, including hypothetical daily settlement prices, is not trading or production settlement and is not imported.

    This edition · Reviewed for the Oct 6, 2026 edition on Oct 5, 2026 at 11:39 pm EDT, using the saved copy of S20 (retrieved Oct 5, 2026 at 5:31 pm EDT). No new retrieval. Not repeated for the Oct 8, 2026 edition.

Corrections and editorial policy

How facts are separated from explanation, and what a useful correction contains, are set out in the editorial policy and its corrections policy. The About page describes the publication’s purpose and independence.