Binance、Coinbase、Kraken 与 OKX WebSocket 订单状态控制对比

已核验事实

• Binance publishes User Data Stream documentation for account and order events.（来源：binance-user-data-stream）
• Coinbase publishes Exchange WebSocket channel documentation for streaming exchange data.（来源：coinbase-websocket-channels）
• Kraken publishes WebSocket v2 add_order documentation for order entry over WebSocket.（来源：kraken-ws-add-order）
• Kraken publishes WebSocket v2 cancel_order documentation for cancellation over WebSocket.（来源：kraken-ws-cancel-order）
• OKX publishes API guide material that includes a WebSocket order channel for order updates.（来源：okx-api-guide）
• A cross-venue implementation must separate acknowledgement, final fill state, cancel failure and reconnect backfill rather than treating one event name as final truth.（来源：binance-user-data-stream、coinbase-websocket-channels、kraken-ws-add-order、kraken-ws-cancel-order、okx-api-guide）

来源地图

• Binance Developers：《User Data Stream》 https://developers.binance.com/docs/binance-spot-api-docs/user-data-stream（binance-user-data-stream，primary=true）
• Coinbase Developer Documentation：《Exchange WebSocket Channels》 https://docs.cdp.coinbase.com/exchange/websocket-feed/channels（coinbase-websocket-channels，primary=true）
• Kraken Developers：《WebSocket v2 Add Order》 https://docs.kraken.com/api/docs/websocket-v2/add_order/（kraken-ws-add-order，primary=true）
• Kraken Developers：《WebSocket v2 Cancel Order》 https://docs.kraken.com/api/docs/websocket-v2/cancel_order/（kraken-ws-cancel-order，primary=true）
• OKX Technical Support：《OKX API guide WebSocket order channel》 https://www.okx.com/docs-v5/en/#order-book-trading-trade-ws-order-channel（okx-api-guide，primary=true）

决策表

如何阅读这些证据

Authentication boundary

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：private order streams require account-level authentication and permission review。这个边界重要，因为公开来源只能证明某个交易所、监管机构或基础设施方发布了控制、方法或政策表面，不能证明私人账户状态、风控引擎未来行为，也不能证明真实事故中的支持可用性。因此用户动作必须具体：grant the least privilege needed and keep keys outside article or browser evidence。

NexuAlpha 读者行动前应记录来源 URL、访问时间、产品表面、司法辖区、账户类型和受影响资产。仍未解决的未知项是：venue-specific key flags and private risk checks。这个未知项应保留在清单中，而不是被改写成营销式确定结论。实际操作中，应把 Binance Developers、Coinbase Developer Documentation、Kraken Developers、Kraken Developers、OKX Technical Support 仅作为公开文档证据；只有账户本地日志、交易 ID、平台公告或官方支持答复能支持进一步移动余额、授予权限、更改托管或信任自动化。

Subscription scope

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：order channels may expose different account, product or instrument slices。因此用户动作必须具体：write down exactly which symbols, account types and channels are subscribed。

仍未解决的未知项是：complete venue-side channel coverage。

Acknowledgement semantics

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：an accepted WebSocket request is not the same as a durable filled order。因此用户动作必须具体：separate request acknowledgement from order lifecycle events。

仍未解决的未知项是：latency between acknowledgement and durable state。

Cancel handling

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：cancel methods can fail or race with fills during fast markets。因此用户动作必须具体：define cancel-replace and idempotent retry rules before live trading。

仍未解决的未知项是：venue-specific partial-fill edge cases。

Reconnect evidence

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：stream gaps can happen during network loss, session expiry or maintenance。因此用户动作必须具体：pair WebSocket streams with REST backfill and sequence checks。

仍未解决的未知项是：exact gap-recovery windows。

Audit trail

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：logs should preserve IDs, timestamps and source channel without secrets。因此用户动作必须具体：store correlation IDs and hashed request references only。

仍未解决的未知项是：private account logs and balances。

Stop rule

关于 Binance Coinbase Kraken OKX WebSocket order state controls，已核验边界很窄：stop automation when acknowledgement, final state or reconnect evidence disagrees。因此用户动作必须具体：freeze new orders until reconciliation succeeds。

仍未解决的未知项是：risk-engine behavior not visible in public docs。

仍需明确的未知项

• venue-specific key flags and private risk checks
• complete venue-side channel coverage
• latency between acknowledgement and durable state
• venue-specific partial-fill edge cases
• exact gap-recovery windows
• private account logs and balances
• risk-engine behavior not visible in public docs

实用结论

WebSocket 订单状态控制应被当作对账表面来比较，而不是当作可互换的实时交易管道。Binance 文档说明 User Data Stream 订单更新，Coinbase 文档说明 Exchange WebSocket channels，Kraken 文档说明 WebSocket v2 add_order 与 cancel_order 方法，OKX 文档在 API guide 中提供 WebSocket order channel。实用结论是：把自动化接入任何平台前，应先映射认证、订阅范围、确认语义、撤单失败处理、重连行为、账户权限和 REST 回补。 保守做法是把公开证据当作地图，而不是当作许可。下一步永远是更窄的核验任务：证明路由、证明范围、证明账户本地状态，并把所有无证据主张留在决策之外。