Metadata only — market data is not displayed on this site

Independent · Not investment advice

Market access

Market access

This snapshot records two product-specific platform-support announcements, from Trading Technologies (TT), for GPU1 and GPU2. An announcement is not access: current enablement, account eligibility and jurisdiction are not confirmed, and this snapshot has no broker or FCM record for any tracked contract.

Fact checks are dated to the UTC day · Market data is not displayed

Updated

Sources & update history
Page updated
· targeted CME source check; baseline values and other checks are unchanged
Contract data baseline
· prepared · 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.
This page in the baseline
This page changed in the Oct 8, 2026 edition.
2 records

Documented platform support

One record per provider and contract. Each field has its own evidence, including the fields that remain unknown.

Platform-support records by provider and contract, with the scope fields that remain unconfirmed
Provider · role Contract Support stateCurrent enablementAccount scopeJurisdiction
Trading Technologies (TT)Execution platform — not a broker or FCMSupport announced GPU1New York Mercantile Exchange Announced in a section dated Oct 2, 2026. The update itself has no recorded publication date. Deployment is not verified.Verified Oct 5 · S11Not confirmedNo deployment evidenceChecked Oct 5 · S3 · S11Not confirmedNo account eligibility statedChecked Oct 5 · S11Not confirmedUS customer access not inferredChecked Oct 5 · S11
Trading Technologies (TT)Execution platform — not a broker or FCMSupport announced GPU2New York Mercantile Exchange Announced in a section dated Oct 2, 2026. The update itself has no recorded publication date. Deployment is not verified.Verified Oct 5 · S11Not confirmedNo deployment evidenceChecked Oct 5 · S3 · S11Not confirmedNo account eligibility statedChecked Oct 5 · S11Not confirmedUS customer access not inferredChecked Oct 5 · S11

Superseded schedule — not a current date

The announcements promised support from the date of the original exchange schedule. GPU1 and GPU2: CME’s revised advisory lists the launch date as TBD. Any date tied to the original schedule is historical.

Coverage

Contracts without an access record

Product-level access is not established by this snapshot for the contracts below. The gap is in this dataset’s coverage; it is not a finding that the contracts are unsupported.

  • HPR · ICE Futures U.S.

    No record in this snapshot

    No access record for HPR is present in this snapshot. That describes this dataset’s coverage; it is not evidence that no platform or broker supports HPR.

  • BKL · ICE Futures U.S.

    No record in this snapshot

    No access record for BKL is present in this snapshot. That describes this dataset’s coverage; it is not evidence that no platform or broker supports BKL.

No broker or FCM has a verified product-level record for any of the four contracts (0 broker records). Not finding public evidence does not mean a provider cannot offer access.

Roles

Who does what

Trading a future involves several organizations with different roles. The names below are the roles recorded in this snapshot; each is sourced on the contract pages.

Market roles, what each means, and the organizations recorded for each role
RoleWhat it meansRecorded in this snapshot
Legal exchange The regulated market whose rules govern the contract.
  • New York Mercantile Exchange — GPU1, GPU2
  • ICE Futures U.S. — HPR, BKL
Exchange operator group The corporate group the exchange belongs to. Not the same legal entity as the exchange.
Execution platform Trading software or venue technology used to send orders. Support on a platform is not an account or a clearing relationship.
  • CME Globex — GPU1, GPU2
  • Trading Technologies — GPU1, GPU2 · Support announced; enablement not confirmed.
Clearing submission channel A route for submitting trades for clearing, such as off-exchange block trades.
Clearing house The central counterparty that clears the contract.
Clearing venue code A code an exchange publishes for where a contract clears. It identifies a venue, not necessarily a named legal clearing house.
  • ICEU — HPR, BKL · Published clearing venue code; the legal clearing entity is not mapped in this snapshot.
Broker / FCM The firm that holds your futures account and gives you access to the exchange and clearing. No record for any tracked contract
Before you trade

Questions to ask your provider

  1. Which exact contract? Name the symbol and the legal exchange — for example GPU1 on NYMEX is a different product from HPR on ICE Futures U.S., even though both reference the H100.
  2. Is it enabled now, and since when? Ask for the current enablement status and its effective date, not an announcement date.
  3. Is my account eligible? Account type, permissions and any product approval your firm requires.
  4. Is my jurisdiction covered? Where you are and where your account is held can both matter.
  5. Who clears it? Which futures commission merchant carries the position, and on what margin terms.

This site does not offer trading, accounts or referrals, and does not rank providers. Contract pages list each product’s terms; the methodology explains coverage limits.

Evidence for this page

Each block lists the facts behind one displayed value and every source reference recorded for them. “Source-level locator” means no fact-specific position was recorded in this snapshot. How to read evidence

Evidence · TT GPU1 support announcement

Support state

Verified Oct 5, 2026

Announced (source section dated Oct 2, 2026). Deployment not verified.

Fact checked (UTC day)
Fact verified (UTC day)
Effective

Evidence · TT GPU1 current enablement

Current enablement

Not confirmed

Not confirmed

Fact checked (UTC day)
Fact verified (UTC day)
No verification date
Effective
Not known

Trading 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.

  • S11 TT support update: CME Compute Futures

    Checked context — does not confirm a value

    Publisher
    Trading Technologies
    Source-level locator
    CME Compute Futures, October 2, 2026; TT Support StatusFact-specific position not recorded in this snapshot
    Upstream relation
    checked context
    Source checked (UTC day)

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

  • S3 CME revised clearing advisory 26-274

    Checked context — does not confirm a value

    Publisher
    CME Group
    Source-level locator
    Document title and revised-notice bodyFact-specific position not recorded in this snapshot
    Upstream relation
    checked context
    Source checked (UTC day)
    Landing-page notice date
    Notice Date as labelled on the landing page. Not a document date and not a revision time of the attachment.

    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.

Evidence · TT GPU1 account scope

Account scope

Not confirmed

Not confirmed

Fact checked (UTC day)
Fact verified (UTC day)
No verification date
Effective
Not known

No 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.

Evidence · TT GPU1 jurisdiction

Jurisdiction

Not confirmed

Not confirmed

Fact checked (UTC day)
Fact verified (UTC day)
No verification date
Effective
Not known

No 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.

Evidence · TT GPU1 promised date (historical)

Promised trade date

Verified Oct 5, 2026

Oct 5, 2026 — tied to the superseded exchange schedule

Fact checked (UTC day)
Fact verified (UTC day)
Effective
Not known

Evidence · TT GPU2 support announcement

Support state

Verified Oct 5, 2026

Announced (source section dated Oct 2, 2026). Deployment not verified.

Fact checked (UTC day)
Fact verified (UTC day)
Effective

Evidence · TT GPU2 current enablement

Current enablement

Not confirmed

Not confirmed

Fact checked (UTC day)
Fact verified (UTC day)
No verification date
Effective
Not known

Trading 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.

  • S11 TT support update: CME Compute Futures

    Checked context — does not confirm a value

    Publisher
    Trading Technologies
    Source-level locator
    CME Compute Futures, October 2, 2026; TT Support StatusFact-specific position not recorded in this snapshot
    Upstream relation
    checked context
    Source checked (UTC day)

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

  • S3 CME revised clearing advisory 26-274

    Checked context — does not confirm a value

    Publisher
    CME Group
    Source-level locator
    Document title and revised-notice bodyFact-specific position not recorded in this snapshot
    Upstream relation
    checked context
    Source checked (UTC day)
    Landing-page notice date
    Notice Date as labelled on the landing page. Not a document date and not a revision time of the attachment.

    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.

Evidence · TT GPU2 account scope

Account scope

Not confirmed

Not confirmed

Fact checked (UTC day)
Fact verified (UTC day)
No verification date
Effective
Not known

No 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.

Evidence · TT GPU2 jurisdiction

Jurisdiction

Not confirmed

Not confirmed

Fact checked (UTC day)
Fact verified (UTC day)
No verification date
Effective
Not known

No 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.

Evidence · TT GPU2 promised date (historical)

Promised trade date

Verified Oct 5, 2026

Oct 5, 2026 — tied to the superseded exchange schedule

Fact checked (UTC day)
Fact verified (UTC day)
Effective
Not known

Evidence · GPU1 and GPU2 current launch date

GPU1 launch date state

Verified Oct 5, 2026

TBD

Source follow-up (UTC day)
· Relevant source body re-read; value unchanged. Original edition check below is preserved.
Fact checked (UTC day)
Fact verified (UTC day)
Effective
Not known

The 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.

  • S3 CME revised clearing advisory 26-274

    Supports this fact

    Publisher
    CME Group
    Locator
    Retrieved document title
    Upstream relation
    supports
    Source checked (UTC day)
    Landing-page notice date
    Notice Date as labelled on the landing page. Not a document date and not a revision time of the attachment.

    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.

  • S3 CME revised clearing advisory 26-274

    Supports this fact

    Locator
    PDF p. 1, Listing Date row (“Trade Date TBD”) and Initial Contracts row (“TBD”)
    Upstream relation
    supports
    Attachment read (ET)
    · Text read and both pages inspected. This does not change the fact’s check date.
    Attachment revision time
    Not confirmed

    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 and source details: the first S3 reference above.

    Attachment of S3, the same notice as its landing page — not an independent confirmation.

GPU2 launch date state

Verified Oct 5, 2026

TBD

Source follow-up (UTC day)
· Relevant source body re-read; value unchanged. Original edition check below is preserved.
Fact checked (UTC day)
Fact verified (UTC day)
Effective
Not known