FIX Drop Copy 序列重置披露雷达
已验证事实边界
1. Coinbase Exchange FIX Drop Copy documentation says drop copy receives execution reports for orders placed through FIX sessions or REST API associated with an API key. 2. Coinbase Exchange Drop Copy documentation describes a single-connection limit per API key and a weekly FIX5 reset schedule. 3. Coinbase International Exchange FIX overview says every connection establishes a new session and new sequence numbers, and resend requests are not supported. 4. Coinbase Exchange upcoming-changes documentation shows execution-report fields can change through scheduled documentation updates. 5. Coinbase REST order lookup documentation allows order queries using exchange-assigned or client-assigned identifiers with required permissions. 6. The safe radar separates drop-copy coverage, reset calendar, change notices, REST lookup fallback, client-order-ID lineage and local gap recovery.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Session scope | drop copy coverage depends on the API key and session relationship described by the venue | record which keys, sessions and products are included before using the feed | whether a sub-account or separate key is outside the drop-copy stream |
| Reset calendar | scheduled resets and logon resets can break naive sequence assumptions | write the reset calendar into the reconciliation runbook | how the desk proves no execution report was missed around reset |
| Connection limit | single-connection limits create failover design constraints | assign ownership for the active drop-copy connection | what happens if monitoring and production compete for the same key |
| Execution-report coverage | drop copy is useful only if the desk understands which order routes it covers | compare FIX, REST and application routes against the documented coverage | whether manual actions or other portfolios appear in the same stream |
| Change notice | execution-report fields can change through documented venue updates | subscribe the parser owner to venue change notices and schema tests | which optional fields are safe to ignore after a change |
| Fallback lookup | REST order lookup can support reconciliation but is not the same as a live feed | define when to query by order ID or client order ID after a gap | how permission scope or outages limit the fallback |
来源地图
- Coinbase Developer Documentation：Exchange FIX Drop Copy 5.0（coinbase-exchange-drop-copy）
- Coinbase Developer Documentation：INTX FIX API Overview（coinbase-intx-fix-overview）
- Coinbase Developer Documentation：Exchange Upcoming Changes（coinbase-exchange-upcoming-changes）
- Coinbase Developer Documentation：Get single order（coinbase-get-single-order）
控制说明
1. Session scope
这一项要求读者先把公开来源翻译成操作规则。这里的含义是：drop copy coverage depends on the API key and session relationship described by the venue。可执行动作是：record which keys, sessions and products are included before using the feed。仍然未知的是：whether a sub-account or separate key is outside the drop-copy stream。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、恢复保证、结算保证、可用性保证、价格暗示或平台排名。
2. Reset calendar
这里的含义是：scheduled resets and logon resets can break naive sequence assumptions。可执行动作是：write the reset calendar into the reconciliation runbook。仍然未知的是：how the desk proves no execution report was missed around reset。
操作测试也必须很窄。这就是本节保留边界的原因。
3. Connection limit
这里的含义是：single-connection limits create failover design constraints。可执行动作是：assign ownership for the active drop-copy connection。仍然未知的是：what happens if monitoring and production compete for the same key。
操作测试也必须很窄。这就是本节保留边界的原因。
4. Execution-report coverage
这里的含义是：drop copy is useful only if the desk understands which order routes it covers。可执行动作是：compare FIX, REST and application routes against the documented coverage。仍然未知的是：whether manual actions or other portfolios appear in the same stream。
操作测试也必须很窄。这就是本节保留边界的原因。
5. Change notice
这里的含义是：execution-report fields can change through documented venue updates。可执行动作是：subscribe the parser owner to venue change notices and schema tests。仍然未知的是：which optional fields are safe to ignore after a change。
操作测试也必须很窄。这就是本节保留边界的原因。
6. Fallback lookup
这里的含义是：REST order lookup can support reconciliation but is not the same as a live feed。可执行动作是：define when to query by order ID or client order ID after a gap。仍然未知的是：how permission scope or outages limit the fallback。
操作测试也必须很窄。这就是本节保留边界的原因。
仍需明确的未知项
- whether a sub-account or separate key is outside the drop-copy stream
- how the desk proves no execution report was missed around reset
- what happens if monitoring and production compete for the same key
- whether manual actions or other portfolios appear in the same stream
- which optional fields are safe to ignore after a change
- how permission scope or outages limit the fallback
实用结论
FIX drop copy 与 sequence reset 文档是对账控制信号，而不是交易台账完整的保证。Coinbase Exchange 表示 FIX Drop Copy 会为关联 FIX session 或 REST API key 下的订单提供 execution reports；Coinbase International Exchange 则说明每次连接会建立新的 session 和 sequence-number set，并有每周 reset 与 logon 时 reset 的选项。雷达结论是：在把 drop copy 当作唯一审计轨迹前，应映射 session scope、reset calendar、single-connection limit、execution-report coverage、client-order-ID handling、REST order lookup 与 gap recovery。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、回调、政策框架、结算路径或流动性头寸在任何未来条件下都能成功的承诺。