OKX PENDLEUSD X-Perp Launch: Contract and Risk Checklist

Verified source facts

1. OKX published the PENDLEUSD X-Perp announcement on September 15, 2026. 2. The announcement says PENDLEUSD UM X-Perp trading opened at 08:00 UTC that day. 3. OKX says users must check product availability in their region through the app. 4. OKX perpetual documentation describes mark price, funding and leverage as distinct contract controls.

Comparison at a glance

1. Official-product check: Availability

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

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

2. Official-product check: Symbol

Here, symbol concerns exact contract identity. Retain the dated first-party wording, identify the eligible entity and product screen, and then match live page.

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

Finally, make symbol reversible where possible: match live page. Retain non-secret evidence and reconcile the result with the rule for exact contract identity. This section evaluates operational mechanics; because lookalike 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 UTC. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm status after open.

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

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

4. Official-product check: Contract value

Here, contract value concerns notional per unit. Retain the dated first-party wording, identify the eligible entity and product screen, and then calculate exposure.

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

Finally, make contract value reversible where possible: calculate exposure. Retain non-secret evidence and reconcile the result with the rule for notional per unit. This section evaluates operational mechanics; because unit mistake remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Index

Here, index concerns constituents and fallback. 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 thin source.

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

6. Official-product check: Mark price

Here, mark price concerns liquidation reference. Retain the dated first-party wording, identify the eligible entity and product screen, and then monitor basis.

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

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

7. Official-product check: Funding

Here, funding concerns interval and cap. Retain the dated first-party wording, identify the eligible entity and product screen, and then model carry.

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

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

8. Official-product check: Tier

Here, tier concerns margin by position size. Retain the dated first-party wording, identify the eligible entity and product screen, and then stress next tier.

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

Finally, make tier reversible where possible: stress next tier. Retain non-secret evidence and reconcile the result with the rule for margin by position size. This section evaluates operational mechanics; because threshold crossing remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Orders

Here, orders concerns tick, lot and price limit. Retain the dated first-party wording, identify the eligible entity and product screen, and then test small order.

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

Finally, make orders reversible where possible: test small order. Retain non-secret evidence and reconcile the result with the rule for tick, lot and price limit. This section evaluates operational mechanics; because rejection remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Stop rule

Here, stop rule concerns unmatched specification. 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 unmatched specification. 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 availability becomes decisive

Consider a reader whose main constraint is account and region. The correct response is not to infer a universal platform or product winner. It is to verify in 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 symbol becomes decisive

Consider a reader whose main constraint is exact contract identity. It is to match live page, 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 UTC. It is to confirm status after open, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when contract value becomes decisive

Consider a reader whose main constraint is notional per unit. It is to calculate exposure, 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 constituents and fallback. It is to inspect methodology, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when mark price becomes decisive

Consider a reader whose main constraint is liquidation reference. It is to monitor basis, retain the evidence, and define a stop condition before funds or permissions are committed.

Sources and editorial method

• OKX to list PENDLEUSD X-Perp — OKX
• Announcements — OKX
• OKX Perpetual Futures Guide — OKX