Binance 与 Coinbase 自成交防护和订单状态控制对比

决策矩阵

来源地图

• Binance Developer Docs：Self Trade Prevention FAQ（binance-stp-faq）
• Binance Developer Docs：Spot REST API trading endpoints（binance-trade-rest）
• Coinbase Developer Documentation：Exchange FIX Drop Copy 5.0（coinbase-drop-copy）
• Coinbase Developer Documentation：Get single order（coinbase-get-order）

控制说明

1. Mode selection

这一项要求读者把公开来源翻译成操作规则。这里的含义是：self-trade behavior depends on the documented mode or type。可执行动作是：record the exact STP mode or SelfTradeType before order submission。仍然未知的是：whether account defaults changed after the integration was written。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。

2. Prevented record

这里的含义是：a prevented match or restated execution report is not the same as a trade fill。可执行动作是：store prevented match id, execution report id and order id without balances。仍然未知的是：whether all related orders are visible to the same API key。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

3. Order-state source

这里的含义是：final order state requires a venue-specific confirmation path。可执行动作是：reconcile REST or FIX state after each prevention event。仍然未知的是：whether a partial cancellation arrived before the local state machine saw it。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

4. Group boundary

这里的含义是：STP can involve same-account or grouped-account behavior depending on venue rules。可执行动作是：document account, profile or group scope without credentials。仍然未知的是：whether subaccount grouping has been changed privately。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

5. Automation recovery

这里的含义是：a bot must not infer final inventory from a prevention event alone。可执行动作是：pause strategy resumption until final state is queried。仍然未知的是：whether stale strategy state survives a disconnect。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

6. Evidence hygiene

这里的含义是：debug records can leak account metadata even without secrets。可执行动作是：retain source URL, mode, event id, order id and stop rule only。仍然未知的是：whether screenshots reveal balances, positions or private strategy timing。

操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。

仍需明确的未知项

• whether account defaults changed after the integration was written
• whether all related orders are visible to the same API key
• whether a partial cancellation arrived before the local state machine saw it
• whether subaccount grouping has been changed privately
• whether stale strategy state survives a disconnect
• whether screenshots reveal balances, positions or private strategy timing

实用结论

Binance 与 Coinbase 都记录了自成交控制，但可核验的证据表面不同。Binance Spot 文档定义 STP modes、prevented matches、tradeGroupId 行为和 prevented quantity 字段。Coinbase Exchange Drop Copy 文档定义 execution reports、restatement events 和 SelfTradeType 值，而 REST order endpoint 仍是账户级最终状态确认表面。实用对比不是哪个平台更安全，而是交易台能否在自动化恢复前证明 STP mode、prevented 或 restated order record、最终订单状态和不含秘密的证据链。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。