Recherche vérifiée par sources: Binance / OKX

Verified source facts

1. Binance announced gradual introduction of its Spot Price Range Execution Rule from April 14, 2026. 2. Binance says taker order portions outside the dynamic execution range expire rather than execute at those prices. 3. OKX documents dynamically calculated upper and lower price limits and rejection or adjustment behavior when orders breach them. 4. OKX's June 29, 2026 update says spot market orders can be partially filled within the price limit and the outside-range remainder cancelled.

Comparison at a glance

1. Control test: Reference price

A trading-control disclosure is meaningful only when converted into a testable rule. For reference price, inspect index, quote or market state. Use a sandbox, non-production context, or the smallest reversible test available, then identify the live reference. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, undisclosed parameters is therefore an explicit audit gap.

The reference price row should end with a concrete monitoring rule tied to index, quote or market state. Make the operator identify the live reference, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; undisclosed parameters remains a separate production risk until observed.

2. Control test: Dynamic range

For dynamic range, inspect upper and lower execution boundary. Use a sandbox, non-production context, or the smallest reversible test available, then do not hard-code a stale percentage.

In this dimension, real-time range is therefore an explicit audit gap.

The dynamic range row should end with a concrete monitoring rule tied to upper and lower execution boundary. Make the operator do not hard-code a stale percentage, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; real-time range remains a separate production risk until observed.

3. Control test: Order scope

For order scope, inspect which taker and market orders are covered. Use a sandbox, non-production context, or the smallest reversible test available, then test each order type separately.

In this dimension, regional interface differences is therefore an explicit audit gap.

The order scope row should end with a concrete monitoring rule tied to which taker and market orders are covered. Make the operator test each order type separately, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; regional interface differences remains a separate production risk until observed.

4. Control test: Outside-range outcome

For outside-range outcome, inspect expiry, rejection or cancellation. Use a sandbox, non-production context, or the smallest reversible test available, then handle each status explicitly.

In this dimension, engine edge cases is therefore an explicit audit gap.

The outside-range outcome row should end with a concrete monitoring rule tied to expiry, rejection or cancellation. Make the operator handle each status explicitly, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; engine edge cases remains a separate production risk until observed.

5. Control test: Partial fill

For partial fill, inspect executed quantity within the boundary. Use a sandbox, non-production context, or the smallest reversible test available, then reconcile fills before retrying.

In this dimension, fill sequence is therefore an explicit audit gap.

The partial fill row should end with a concrete monitoring rule tied to executed quantity within the boundary. Make the operator reconcile fills before retrying, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; fill sequence remains a separate production risk until observed.

6. Control test: Remaining quantity

For remaining quantity, inspect cancelled or expired residue. Use a sandbox, non-production context, or the smallest reversible test available, then calculate residual from authoritative order state.

In this dimension, delayed updates is therefore an explicit audit gap.

The remaining quantity row should end with a concrete monitoring rule tied to cancelled or expired residue. Make the operator calculate residual from authoritative order state, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; delayed updates remains a separate production risk until observed.

7. Control test: API signal

For api signal, inspect status, error and amended price. Use a sandbox, non-production context, or the smallest reversible test available, then persist raw response and order ID.

In this dimension, WAF ambiguity is therefore an explicit audit gap.

The api signal row should end with a concrete monitoring rule tied to status, error and amended price. Make the operator persist raw response and order ID, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; WAF ambiguity remains a separate production risk until observed.

8. Control test: New listing

For new listing, inspect unstable index or special phase. Use a sandbox, non-production context, or the smallest reversible test available, then use smaller size and current rules.

In this dimension, opening volatility is therefore an explicit audit gap.

The new listing row should end with a concrete monitoring rule tied to unstable index or special phase. Make the operator use smaller size and current rules, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; opening volatility remains a separate production risk until observed.

9. Control test: User protection

For user protection, inspect reduced abnormal-price execution. Use a sandbox, non-production context, or the smallest reversible test available, then treat it as a guardrail, not a guarantee.

In this dimension, loss prevention is therefore an explicit audit gap.

The user protection row should end with a concrete monitoring rule tied to reduced abnormal-price execution. Make the operator treat it as a guardrail, not a guarantee, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; loss prevention remains a separate production risk until observed.

10. Control test: Automation

For automation, inspect idempotent retry and circuit breaker. Use a sandbox, non-production context, or the smallest reversible test available, then query state before resubmission.

In this dimension, network timeout outcome is therefore an explicit audit gap.

The automation row should end with a concrete monitoring rule tied to idempotent retry and circuit breaker. Make the operator query state before resubmission, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; network timeout outcome remains a separate production risk until observed.

Decision scenarios

Scenario 1: when reference price becomes decisive

Consider a reader whose main constraint is index, quote or market state. The correct response is not to infer a universal platform or product winner. It is to identify the live reference, 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 dynamic range becomes decisive

Consider a reader whose main constraint is upper and lower execution boundary. It is to do not hard-code a stale percentage, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when order scope becomes decisive

Consider a reader whose main constraint is which taker and market orders are covered. It is to test each order type separately, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when outside-range outcome becomes decisive

Consider a reader whose main constraint is expiry, rejection or cancellation. It is to handle each status explicitly, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when partial fill becomes decisive

Consider a reader whose main constraint is executed quantity within the boundary. It is to reconcile fills before retrying, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when remaining quantity becomes decisive

Consider a reader whose main constraint is cancelled or expired residue. It is to calculate residual from authoritative order state, retain the evidence, and define a stop condition before funds or permissions are committed.