Kaynak doğrulamalı araştırma: Coinbase Kraken FIX Sequence

Decision Matrix

Source Map

• Coinbase Developer Documentation: INTX FIX API Overview (coinbase-intx-fix-overview)
• Coinbase Developer Documentation: Exchange FIX Drop Copy 5.0 (coinbase-exchange-drop-copy)
• Kraken API Center: Logon - FIX API (kraken-fix-logon)
• Kraken API Center: Cancel on Disconnect (kraken-cancel-all-after)

Control Notes

1. Session reset

Session reset is the decision point where public documentation must become an operating rule. In this package, it means sequence reset is a session-level recovery action, not a portfolio state guarantee. The practical action is to record who may set ResetSeqNumFlag and when the reset is allowed. The unresolved edge is whether downstream systems retained every missing execution report, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Drop-copy backfill

Drop-copy backfill is the decision point where public documentation must become an operating rule. In this package, it means execution reports can provide evidence across order-entry surfaces tied to an API key. The practical action is to run drop-copy or REST backfill before declaring orders reconciled. The unresolved edge is orders routed through entities or keys outside the monitored scope, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Disconnect timer

Disconnect timer is the decision point where public documentation must become an operating rule. In this package, it means cancel-on-disconnect controls depend on venue-specific timer behavior. The practical action is to refresh, deactivate and test the timer in a non-production incident drill. The unresolved edge is whether a network split prevented the venue from seeing the disconnect, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Order terminal state

Order terminal state is the decision point where public documentation must become an operating rule. In this package, it means cancel intent and cancel acknowledgement are not the same as final order state. The practical action is to query fills, cancels and rejects after reconnection. The unresolved edge is fills racing during the disconnect window, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Evidence hygiene

Evidence hygiene is the decision point where public documentation must become an operating rule. In this package, it means FIX logs can contain sensitive identifiers and account-level state. The practical action is to store non-secret session labels, timestamps and state transitions only. The unresolved edge is internal retention and redaction policy, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Manual pause

Manual pause is the decision point where public documentation must become an operating rule. In this package, it means automation should stop when local and venue state disagree. The practical action is to pause new order entry until sequence, order and fill state reconcile. The unresolved edge is who can override the pause during a market incident, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• whether downstream systems retained every missing execution report
• orders routed through entities or keys outside the monitored scope
• whether a network split prevented the venue from seeing the disconnect
• fills racing during the disconnect window
• internal retention and redaction policy
• who can override the pause during a market incident

Practical Takeaway

Coinbase and Kraken FIX controls solve different failure modes, so a venue runbook should not treat sequence reset, drop-copy recovery and cancel-on-disconnect as the same safety action. Coinbase International Exchange FIX documentation describes sequence-number resets and FIX session endpoints, Coinbase Exchange drop copy describes execution-report recovery across orders associated with an API key, and Kraken FIX logon documentation exposes a CancelOrdersOnDisconnect field while Kraken WebSocket documentation separately describes cancelAllOrdersAfter. The decision outcome is to document sequence reset authority, disconnect timer behavior, final execution-report backfill, and a manual pause rule before a trader or bot assumes it is flat. 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, callback, policy framework, settlement route or liquidity position will work under every future condition.