Recherche vérifiée par sources: OKX

Verified source facts

1. OKX published the FLOCK perpetual listing on September 12, 2026 with a stated opening time of 10:00 UTC. 2. The announcement lists FLOCK/USDT index exposure, USDT settlement, face value 100 and leverage from 0.01x to 20x. 3. OKX states a four-hour funding interval that can change to hourly when the funding-rate cap or floor is reached. 4. The official page warns that the product and terms may not apply to every customer and directs users to verify availability in the account.

Comparison at a glance

1. Official-product check: Listing time

A venue announcement becomes useful only after its rule is translated into a testable account decision. Here, listing time concerns official UTC opening. Retain the dated first-party wording, identify the eligible entity and product screen, and then record the timestamp and account status. 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 later schedule changes. That unknown must remain visible rather than being converted into a prediction.

Finally, make listing time reversible where possible: record the timestamp and account status. Retain non-secret evidence and reconcile the result with the rule for official UTC opening. This section evaluates operational mechanics; because later schedule changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

2. Official-product check: Eligibility

Here, eligibility concerns entity and regional access. Retain the dated first-party wording, identify the eligible entity and product screen, and then verify inside the authenticated account.

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

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

3. Official-product check: Underlying index

Here, underlying index concerns FLOCK/USDT reference. Retain the dated first-party wording, identify the eligible entity and product screen, and then inspect current index constituents.

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

Finally, make underlying index reversible where possible: inspect current index constituents. Retain non-secret evidence and reconcile the result with the rule for FLOCK/USDT reference. This section evaluates operational mechanics; because constituent changes remains unresolved, it does not predict the underlying market or recommend taking the exposure.

4. Official-product check: Settlement

Here, settlement concerns USDT-margined profit and loss. Retain the dated first-party wording, identify the eligible entity and product screen, and then map collateral and conversion risk.

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

Finally, make settlement reversible where possible: map collateral and conversion risk. Retain non-secret evidence and reconcile the result with the rule for USDT-margined profit and loss. This section evaluates operational mechanics; because future collateral rules remains unresolved, it does not predict the underlying market or recommend taking the exposure.

5. Official-product check: Face value

Here, face value concerns contract quantity convention. Retain the dated first-party wording, identify the eligible entity and product screen, and then translate quantity into notional exposure.

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

Finally, make face value reversible where possible: translate quantity into notional exposure. Retain non-secret evidence and reconcile the result with the rule for contract quantity convention. This section evaluates operational mechanics; because interface rounding remains unresolved, it does not predict the underlying market or recommend taking the exposure.

6. Official-product check: Leverage

Here, leverage concerns available range and tier limits. Retain the dated first-party wording, identify the eligible entity and product screen, and then use a self-imposed lower maximum.

The documentation can describe those controls, but it cannot resolve account-specific cap.

Finally, make leverage reversible where possible: use a self-imposed lower maximum. Retain non-secret evidence and reconcile the result with the rule for available range and tier limits. This section evaluates operational mechanics; because account-specific cap remains unresolved, it does not predict the underlying market or recommend taking the exposure.

7. Official-product check: Funding

Here, funding concerns rate formula and settlement interval. Retain the dated first-party wording, identify the eligible entity and product screen, and then check current rate and next timestamp.

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

Finally, make funding reversible where possible: check current rate and next timestamp. Retain non-secret evidence and reconcile the result with the rule for rate formula and settlement interval. This section evaluates operational mechanics; because future funding remains unresolved, it does not predict the underlying market or recommend taking the exposure.

8. Official-product check: Margin mode

Here, margin mode concerns isolated, cross or portfolio behavior. Retain the dated first-party wording, identify the eligible entity and product screen, and then confirm active mode before ordering.

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

Finally, make margin mode reversible where possible: confirm active mode before ordering. Retain non-secret evidence and reconcile the result with the rule for isolated, cross or portfolio behavior. This section evaluates operational mechanics; because portfolio correlations remains unresolved, it does not predict the underlying market or recommend taking the exposure.

9. Official-product check: Liquidation

Here, liquidation concerns mark-price and maintenance margin trigger. Retain the dated first-party wording, identify the eligible entity and product screen, and then calculate a conservative buffer.

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

Finally, make liquidation reversible where possible: calculate a conservative buffer. Retain non-secret evidence and reconcile the result with the rule for mark-price and maintenance margin trigger. This section evaluates operational mechanics; because gap behavior remains unresolved, it does not predict the underlying market or recommend taking the exposure.

10. Official-product check: Records

Here, records concerns orders, fills, funding and settlement. Retain the dated first-party wording, identify the eligible entity and product screen, and then export evidence after each test.

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

Finally, make records reversible where possible: export evidence after each test. Retain non-secret evidence and reconcile the result with the rule for orders, fills, funding and settlement. This section evaluates operational mechanics; because retention period remains unresolved, it does not predict the underlying market or recommend taking the exposure.

Decision scenarios

Scenario 1: when listing time becomes decisive

Consider a reader whose main constraint is official UTC opening. The correct response is not to infer a universal platform or product winner. It is to record the timestamp and account status, 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 eligibility becomes decisive

Consider a reader whose main constraint is entity and regional access. It is to verify inside the authenticated account, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when underlying index becomes decisive

Consider a reader whose main constraint is FLOCK/USDT reference. It is to inspect current index constituents, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when settlement becomes decisive

Consider a reader whose main constraint is USDT-margined profit and loss. It is to map collateral and conversion risk, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when face value becomes decisive

Consider a reader whose main constraint is contract quantity convention. It is to translate quantity into notional exposure, 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 available range and tier limits. It is to use a self-imposed lower maximum, retain the evidence, and define a stop condition before funds or permissions are committed.