Coinbase WebSocket level2 batch 频道准备清单
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Coinbase Exchange WebSocket documentation describes the feed overview and connection surface. 2. Coinbase channel documentation is the source for channel-specific subscriptions and payload expectations. 3. Coinbase REST authentication documentation defines signed authenticated request material for private REST checks. 4. Coinbase order lookup is a separate authenticated surface for account-specific order-state confirmation. 5. A channel message alone is not a complete account audit after message gaps or disconnects. 6. A readiness checklist should separate channel purpose, ordering signal, connection behavior, REST confirmation and non-secret logging.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Channel purpose | level2-style channels answer order-book questions rather than all account questions | write down which decision each channel supports | whether a market-data channel is being mistaken for account truth |
| Ordering signal | sequence and payload order determine local book trust | treat any gap as a reconciliation trigger | whether local backpressure created an undetected gap |
| Heartbeat and close | connection liveness does not prove complete data | log close code, reconnect time and resubscription success | whether a network device silently dropped messages |
| Snapshot rule | a fresh snapshot may be needed before local state is reused | define when to rebuild state before automation resumes | whether old inventory assumptions remain in memory |
| Private confirmation | REST checks are needed for account-specific order conclusions | confirm final order state after feed anomalies | whether REST rate limits delay recovery |
| Evidence hygiene | WebSocket and REST logs can expose credentials or balances | store channel, sequence, timestamp, non-secret id and source URL only | whether debug screenshots reveal strategy timing |
来源地图
- Coinbase Developer Documentation：Exchange WebSocket feed overview（coinbase-ws-overview）
- Coinbase Developer Documentation：Exchange WebSocket feed channels（coinbase-ws-channels）
- Coinbase Developer Documentation：Exchange REST API authentication（coinbase-rest-auth）
- Coinbase Developer Documentation：Get single order（coinbase-get-order）
控制说明
1. Channel purpose
这一项要求读者把公开来源翻译成操作规则。这里的含义是：level2-style channels answer order-book questions rather than all account questions。可执行动作是：write down which decision each channel supports。仍然未知的是：whether a market-data channel is being mistaken for account truth。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Ordering signal
这里的含义是：sequence and payload order determine local book trust。可执行动作是：treat any gap as a reconciliation trigger。仍然未知的是：whether local backpressure created an undetected gap。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Heartbeat and close
这里的含义是：connection liveness does not prove complete data。可执行动作是：log close code, reconnect time and resubscription success。仍然未知的是：whether a network device silently dropped messages。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Snapshot rule
这里的含义是：a fresh snapshot may be needed before local state is reused。可执行动作是：define when to rebuild state before automation resumes。仍然未知的是：whether old inventory assumptions remain in memory。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Private confirmation
这里的含义是：REST checks are needed for account-specific order conclusions。可执行动作是：confirm final order state after feed anomalies。仍然未知的是：whether REST rate limits delay recovery。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
6. Evidence hygiene
这里的含义是：WebSocket and REST logs can expose credentials or balances。可执行动作是：store channel, sequence, timestamp, non-secret id and source URL only。仍然未知的是：whether debug screenshots reveal strategy timing。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether a market-data channel is being mistaken for account truth
- whether local backpressure created an undetected gap
- whether a network device silently dropped messages
- whether old inventory assumptions remain in memory
- whether REST rate limits delay recovery
- whether debug screenshots reveal strategy timing
实用结论
Coinbase WebSocket 准备度应按具体频道建立证据计划。Coinbase 文档把 Exchange WebSocket overview 与 channel documentation 分开，而 channel 页面是 level2 与 level2_batch 期望的来源。因此集成应记录为什么选择该频道、如何监控 message order 与 heartbeat、何时需要 snapshot 或 REST confirmation，以及哪些证据可以保留而不暴露 key、余额或策略时序。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相關專題與工具:交易所 API 與行情資料核查