出典確認済みリサーチ: Binance VS Coinbase STP

Decision Matrix

Source Map

• 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)

Control Notes

1. Mode selection

Mode selection is the point where public documentation must become an operating rule. In this package, it means self-trade behavior depends on the documented mode or type. The practical action is to record the exact STP mode or SelfTradeType before order submission. The unresolved edge is whether account defaults changed after the integration was written, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Prevented record

Prevented record is the point where public documentation must become an operating rule. In this package, it means a prevented match or restated execution report is not the same as a trade fill. The practical action is to store prevented match id, execution report id and order id without balances. The unresolved edge is whether all related orders are visible to the same API key, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. Order-state source

Order-state source is the point where public documentation must become an operating rule. In this package, it means final order state requires a venue-specific confirmation path. The practical action is to reconcile REST or FIX state after each prevention event. The unresolved edge is whether a partial cancellation arrived before the local state machine saw it, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Group boundary

Group boundary is the point where public documentation must become an operating rule. In this package, it means STP can involve same-account or grouped-account behavior depending on venue rules. The practical action is to document account, profile or group scope without credentials. The unresolved edge is whether subaccount grouping has been changed privately, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Automation recovery

Automation recovery is the point where public documentation must become an operating rule. In this package, it means a bot must not infer final inventory from a prevention event alone. The practical action is to pause strategy resumption until final state is queried. The unresolved edge is whether stale strategy state survives a disconnect, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

6. Evidence hygiene

Evidence hygiene is the point where public documentation must become an operating rule. In this package, it means debug records can leak account metadata even without secrets. The practical action is to retain source URL, mode, event id, order id and stop rule only. The unresolved edge is whether screenshots reveal balances, positions or private strategy timing, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

• 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

Practical Takeaway

Binance and Coinbase both document self-trade controls, but they expose different evidence surfaces. Binance Spot documentation defines STP modes, prevented matches, tradeGroupId behavior and prevented quantity fields. Coinbase Exchange Drop Copy documentation defines execution reports, restatement events and SelfTradeType values, while the REST order endpoint remains a separate account-specific confirmation surface. The useful comparison is not which venue is safer; it is whether a desk can prove the STP mode, prevented or restated order record, final order state and non-secret evidence trail before automation resumes. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.