Exchange Updates

Kaynak doğrulamalı araştırma: OKX

6 dk

Gövde metni doğrulanmış İngilizce kaynak dilinde gösteriliyor. Çeviri kaynak incelemesinden sonra eklenecek.

Direct answer

OKX announced IOSTUSD and STRKUSD X-Perps for September 17, 2026, with IOST scheduled at 08:00 UTC and STRK at 08:15 UTC. Listing time does not by itself prove that a product is available in every region or appropriate for a user. Before trading, users should verify account jurisdiction, live instrument status, contract specification, index source, funding method, leverage ceiling, liquidation rules, order-book depth and the difference between the underlying token and the derivative position.

Analizi kapat

Verified source facts

1. OKX scheduled IOSTUSD X-Perps for 08:00 UTC on September 17, 2026. 2. OKX scheduled STRKUSD X-Perps for 08:15 UTC on September 17, 2026. 3. The announcement warns that product availability may vary by region. 4. A perpetual derivative is a separate instrument from holding the underlying token.

Comparison at a glance

Makale tablosu: yatay kaydırın veya tablo alanına odaklanıp ok tuşlarını kullanın.

Decision layerWhat to inspectMinimum safe action
Jurisdictionaccount regionverify eligibility
InstrumentIOSTUSD or STRKUSD X-Perpmatch symbol
Launch time08:00 or 08:15 UTCcheck live state
Contractderivative not spot tokenread specification
Indexreference price sourcesinspect methodology
Fundingperiodic transfer methodmodel cost
Leverageaccount limituse conservative size
Margineligible collateralconfirm haircut
Liquidityorder-book depthuse limit order
Stop rulespecification or region uncleardo not trade

1. Official-product check: Jurisdiction

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, jurisdiction concerns account region. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify eligibility. 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 access denial. That unknown must remain visible rather than being converted into a prediction.

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

2. Official-product check: Instrument

Here, instrument concerns IOSTUSD or STRKUSD X-Perp. Retain the dated first-party wording, identify the eligible entity and product screen, and then match symbol.

The documentation can describe those controls, but it cannot resolve wrong market.

Finally, make instrument reversible where possible: match symbol. Retain non-secret evidence and reconcile the result with the rule for IOSTUSD or STRKUSD X-Perp. This section evaluates operational mechanics; because wrong market remains unresolved, it does not predict the underlying market or recommend taking the exposure.

3. Official-product check: Launch time

Here, launch time concerns 08:00 or 08:15 UTC. Retain the dated first-party wording, identify the eligible entity and product screen, and then check live state.

The documentation can describe those controls, but it cannot resolve premature order.

Finally, make launch time reversible where possible: check live state. Retain non-secret evidence and reconcile the result with the rule for 08:00 or 08:15 UTC. This section evaluates operational mechanics; because premature order remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Contract

Here, contract concerns derivative not spot token. Retain the dated first-party wording, identify the eligible entity and product screen, and then read specification.

The documentation can describe those controls, but it cannot resolve ownership confusion.

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

5. Official-product check: Index

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

The documentation can describe those controls, but it cannot resolve basis risk.

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

6. Official-product check: Funding

Here, funding concerns periodic transfer method. Retain the dated first-party wording, identify the eligible entity and product screen, and then model cost.

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

Finally, make funding reversible where possible: model cost. Retain non-secret evidence and reconcile the result with the rule for periodic transfer method. This section evaluates operational mechanics; because rate spike remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Leverage

Here, leverage concerns account limit. Retain the dated first-party wording, identify the eligible entity and product screen, and then use conservative size.

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

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

8. Official-product check: Margin

Here, margin concerns eligible collateral. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm haircut.

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

Finally, make margin reversible where possible: confirm haircut. Retain non-secret evidence and reconcile the result with the rule for eligible collateral. This section evaluates operational mechanics; because shortfall remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Liquidity

Here, liquidity concerns order-book depth. Retain the dated first-party wording, identify the eligible entity and product screen, and then use limit order.

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

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

10. Official-product check: Stop rule

Here, stop rule concerns specification or region unclear. Retain the dated first-party wording, identify the eligible entity and product screen, and then do not trade.

The documentation can describe those controls, but it cannot resolve support confirmation.

Finally, make stop rule reversible where possible: do not trade. Retain non-secret evidence and reconcile the result with the rule for specification or region unclear. This section evaluates operational mechanics; because support confirmation remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when jurisdiction becomes decisive

Consider a reader whose main constraint is account region. The correct response is not to infer a universal platform or product winner. It is to verify eligibility, 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 IOSTUSD or STRKUSD X-Perp. It is to match symbol, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when launch time becomes decisive

Consider a reader whose main constraint is 08:00 or 08:15 UTC. It is to check live state, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when contract becomes decisive

Consider a reader whose main constraint is derivative not spot token. It is to read specification, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when index becomes decisive

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

Scenario 6: when funding becomes decisive

Consider a reader whose main constraint is periodic transfer method. It is to model cost, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

  • IOSTUSD and STRKUSD X-Perps listing — OKX
  • Latest announcements — OKX
  • Perpetual futures guide — OKX Learn

Kaynaklar

03
  1. OKXIOSTUSD and STRKUSD X-Perps listing · okx.com
  2. OKXLatest announcements · okx.com
  3. OKX LearnPerpetual futures guide · okx.com
Sonraki araştırma yolunu seçin