平台对比

Binance cancelReplace 与 OKX 订单状态最终性控制对比

4 分钟

已验证事实边界

1. Binance says orderRateLimitExceededMode applies when the order rate limit is exceeded. 2. Binance says orderRateLimitExceededMode allows cancelReplace to cancel orders but does not allow placing new orders. 3. Binance lists REST POST /api/v3/order/cancelReplace and WebSocket order.cancelReplace as affected endpoints. 4. OKX says failed affected post-only placement now pushes only state canceled, without state live first. 5. OKX says regular limit, market, ioc and fok order types remain unchanged by the push-behavior adjustment.

收起完整分析

决策矩阵

文章表格:可横向滑动,或聚焦表格区域后使用方向键。

CheckWhat it meansPractical actionUnknown to keep explicit
Acknowledgementthe exchange has received or accepted an order messageseparate transport acknowledgement from final order stategateway latency and private matching details
Final statethe last usable order state after validation, book entry, fill or cancellationwait for the explicit state update before reconcilingprivate account event timing
Post-only exceptionan order type that can cancel when it would cross the booktreat live-then-canceled sequences as a special casefuture matching-engine rules
Amend resultthe source field that explains a successful or failed amendmentrecord amend result and source before retryingvenue-specific reject reason depth
Cancel resultconfirmation that an order is canceled rather than merely requestedwait for canceled state before reusing exposurenetwork or session failure timing
Rate-limit modehow requests behave when order-rate limits are hitdesign retry budgets around documented limitsprivate account tier or subaccount limits
WebSocket channelthe feed that carries order-state updatessubscribe and reconcile before trusting UI-only stateconnection drop handling
REST fallbackthe secondary route for order checks or repairuse only with idempotent identifiers and logsvenue incident behavior
Evidence packetnon-secret request id, order id, timestamp and official URLstore operational evidence without API secretssensitive account values
Stop rulewhen the article cannot support actionstop if accepted, live, filled and canceled states are conflatedfuture API changes

来源地图

  • Binance Support:Binance Spot API Service Upgrade (2024-06-06)(binance-cancelreplace)
  • Binance Developers:Binance Spot API documentation(binance-spot-doc)
  • OKX Europe:OKX WebSocket Orders Channel Push Behavior Adjustment Announcement(okx-websocket-orders)
  • OKX Technical Support:OKX API guide(okx-api-guide)

控制说明

1. Acknowledgement

这一项要求读者把公开来源转换成操作规则。这里的含义是:the exchange has received or accepted an order message。可执行动作是:separate transport acknowledgement from final order state。仍然未知的是:gateway latency and private matching details。因此本文不会把未知部分包装成安全承诺、收益承诺、官方背书、审批保证、可用性保证或注册诱导。

2. Final state

这里的含义是:the last usable order state after validation, book entry, fill or cancellation。可执行动作是:wait for the explicit state update before reconciling。仍然未知的是:private account event timing。

3. Post-only exception

这里的含义是:an order type that can cancel when it would cross the book。可执行动作是:treat live-then-canceled sequences as a special case。仍然未知的是:future matching-engine rules。

4. Amend result

这里的含义是:the source field that explains a successful or failed amendment。可执行动作是:record amend result and source before retrying。仍然未知的是:venue-specific reject reason depth。

5. Cancel result

这里的含义是:confirmation that an order is canceled rather than merely requested。可执行动作是:wait for canceled state before reusing exposure。仍然未知的是:network or session failure timing。

6. Rate-limit mode

这里的含义是:how requests behave when order-rate limits are hit。可执行动作是:design retry budgets around documented limits。仍然未知的是:private account tier or subaccount limits。

7. WebSocket channel

这里的含义是:the feed that carries order-state updates。可执行动作是:subscribe and reconcile before trusting UI-only state。仍然未知的是:connection drop handling。

8. REST fallback

这里的含义是:the secondary route for order checks or repair。可执行动作是:use only with idempotent identifiers and logs。仍然未知的是:venue incident behavior。

9. Evidence packet

这里的含义是:non-secret request id, order id, timestamp and official URL。可执行动作是:store operational evidence without API secrets。仍然未知的是:sensitive account values。

10. Stop rule

这里的含义是:when the article cannot support action。可执行动作是:stop if accepted, live, filled and canceled states are conflated。仍然未知的是:future API changes。

实用结论

本文最有价值的地方是克制。Binance 与 OKX 暴露的是不同的 API 订单修复问题。Binance Spot API 升级说明,orderRateLimitExceededMode 会在订单速率限制超出时允许 cancelReplace 撤单,但不允许继续下新订单,涉及 REST POST /api/v3/order/cancelReplace 与 WebSocket order.cancelReplace。OKX 的 WebSocket 更新则收窄 post-only 与 RPI 工作流中的状态解释:失败下单可只显示 canceled,成功入簿后才延迟推送 state live。决策重点不是哪个平台绝对更安全,而是交易机器人是否能区分修复撤单、新订单准入、入簿确认和最终状态。 用户应获得一个更清楚的核验路径,而不是一个看似肯定、实则无法由公开证据承担的承诺。

来源与证据

04
  1. Binance SupportBinance Spot API Service Upgrade (2024-06-06)
  2. Binance DevelopersBinance Spot API documentation · developers.binance.com
  3. OKX EuropeOKX WebSocket Orders Channel Push Behavior Adjustment Announcement · okx.com
  4. OKX Technical SupportOKX API guide · okx.com
选择下一步研究路径