出典確認済みリサーチ: OKX

Verified source facts

1. OKX says ORCLUSD UM X-Perp trading opened at 09:00 UTC on September 11, 2026. 2. OKX says the product update covers web, app and API interfaces. 3. The announcement tells users to check regional product availability and warns about leveraged-trading risk. 4. A perpetual derivative provides contract exposure and does not by itself confer Oracle shareholder rights.

Comparison at a glance

1. Official-product check: Eligibility

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, eligibility concerns region and account entity. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify inside the app. A launch headline cannot prove access, suitability, liquidity, or the result for a particular account.

Separate the product's stated mechanics from promotional framing. Identify the funding source, matching or pricing rule, settlement trigger, fee formula, loss boundary, and suspension policy. The documentation can describe those controls, but it cannot resolve future restrictions. That unknown must remain visible rather than being converted into a prediction.

Finally, make eligibility reversible where possible: verify inside the app. Retain non-secret evidence and reconcile the result with the rule for region and account entity. This section evaluates operational mechanics; because future restrictions remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Instrument

Here, instrument concerns equity-linked derivative. Retain the dated first-party wording, identify the eligible entity and product screen, and then read the contract specification.

The documentation can describe those controls, but it cannot resolve legal classification.

Finally, make instrument reversible where possible: read the contract specification. Retain non-secret evidence and reconcile the result with the rule for equity-linked derivative. This section evaluates operational mechanics; because legal classification remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Index

Here, index concerns reference price and fallback. Retain the dated first-party wording, identify the eligible entity and product screen, and then retain current methodology.

The documentation can describe those controls, but it cannot resolve stress behavior.

Finally, make index reversible where possible: retain current methodology. Retain non-secret evidence and reconcile the result with the rule for reference price and fallback. This section evaluates operational mechanics; because stress behavior remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Trading hours

Here, trading hours concerns session and maintenance windows. Retain the dated first-party wording, identify the eligible entity and product screen, and then map to underlying-market hours.

The documentation can describe those controls, but it cannot resolve holiday schedule.

Finally, make trading hours reversible where possible: map to underlying-market hours. Retain non-secret evidence and reconcile the result with the rule for session and maintenance windows. This section evaluates operational mechanics; because holiday schedule remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Funding

Here, funding concerns interval and calculation. Retain the dated first-party wording, identify the eligible entity and product screen, and then model both payment directions.

The documentation can describe those controls, but it cannot resolve future rate.

Finally, make funding reversible where possible: model both payment directions. Retain non-secret evidence and reconcile the result with the rule for interval and calculation. This section evaluates operational mechanics; because future rate remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Leverage

Here, leverage concerns margin and liquidation. Retain the dated first-party wording, identify the eligible entity and product screen, and then use minimum necessary exposure.

The documentation can describe those controls, but it cannot resolve future volatility.

Finally, make leverage reversible where possible: use minimum necessary exposure. Retain non-secret evidence and reconcile the result with the rule for margin and liquidation. This section evaluates operational mechanics; because future volatility remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Settlement

Here, settlement concerns USD unit and collateral. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify conversion dependency.

The documentation can describe those controls, but it cannot resolve collateral depeg.

Finally, make settlement reversible where possible: verify conversion dependency. Retain non-secret evidence and reconcile the result with the rule for USD unit and collateral. This section evaluates operational mechanics; because collateral depeg remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Corporate actions

Here, corporate actions concerns splits and distributions. Retain the dated first-party wording, identify the eligible entity and product screen, and then read adjustment notices.

The documentation can describe those controls, but it cannot resolve future issuer event.

Finally, make corporate actions reversible where possible: read adjustment notices. Retain non-secret evidence and reconcile the result with the rule for splits and distributions. This section evaluates operational mechanics; because future issuer event remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Liquidity

Here, liquidity concerns book depth and slippage. Retain the dated first-party wording, identify the eligible entity and product screen, and then test with a small order.

The documentation can describe those controls, but it cannot resolve stress-time depth.

Finally, make liquidity reversible where possible: test with a small order. Retain non-secret evidence and reconcile the result with the rule for book depth and slippage. This section evaluates operational mechanics; because stress-time depth remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Exit

Here, exit concerns suspension or delisting path. Retain the dated first-party wording, identify the eligible entity and product screen, and then define a forced-exit plan.

The documentation can describe those controls, but it cannot resolve future venue decision.

Finally, make exit reversible where possible: define a forced-exit plan. Retain non-secret evidence and reconcile the result with the rule for suspension or delisting path. This section evaluates operational mechanics; because future venue decision remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when eligibility becomes decisive

Consider a reader whose main constraint is region and account entity. The correct response is not to infer a universal platform or product winner. It is to verify inside the app, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when instrument becomes decisive

Consider a reader whose main constraint is equity-linked derivative. It is to read the contract specification, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when index becomes decisive

Consider a reader whose main constraint is reference price and fallback. It is to retain current methodology, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when trading hours becomes decisive

Consider a reader whose main constraint is session and maintenance windows. It is to map to underlying-market hours, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when funding becomes decisive

Consider a reader whose main constraint is interval and calculation. It is to model both payment directions, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when leverage becomes decisive

Consider a reader whose main constraint is margin and liquidation. It is to use minimum necessary exposure, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• OKX to list ORCLUSD Equity X-Perp — OKX Help Center
• ORCLUSD contract page — OKX
• Perpetual swap overview — OKX API Docs