Coinbase 与 Kraken WebSocket 认证：连接存活控制清单

决策矩阵

来源地图

• Coinbase Developer Documentation：Advanced Trade WebSocket Overview（coinbase-ws-overview）
• Coinbase Developer Documentation：Advanced Trade WebSocket Authentication（coinbase-ws-auth）
• Kraken API Center：Spot WebSocket v2 Documentation（kraken-ws-v2）
• Kraken API Center：Get Websockets Token（kraken-ws-token）

控制说明

1. Session object

这一项要求读者把公开来源翻译成操作规则。这里的含义是：a WebSocket URL, authenticated subscription and user data stream are different objects even when they share one connection。可执行动作是：name the channel, authentication method and private-data purpose before subscribing。仍然未知的是：whether the private account has the same permission and product access。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。

2. Token freshness

这里的含义是：authentication can depend on signed payloads or token issuance rather than a static connection string。可执行动作是：record token source, expiry assumption and refresh condition without storing secrets。仍然未知的是：clock drift, token revocation, account policy changes and future endpoint behavior。

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

3. Liveness evidence

这里的含义是：an open socket is not the same as a current market or order-state view。可执行动作是：capture heartbeat, sequence or reconnect evidence before acting on stream state。仍然未知的是：missed messages, silent stale streams, proxy drops and partial channel recovery。

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

4. Reconnect policy

这里的含义是：production readiness depends on what happens after disconnect, not only on the first subscription。可执行动作是：write reconnect backoff, resubscribe, replay and final REST reconciliation rules。仍然未知的是：whether the exchange exposes every lost private event for replay。

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

5. Stop condition

这里的含义是：WebSocket data should not trigger irreversible trading if authentication, sequence or freshness is unclear。可执行动作是：stop automation when token status, channel state or reconciliation timestamp is missing。仍然未知的是：private account eligibility, future rate limits and support-side recovery。

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

仍需明确的未知项

• whether the private account has the same permission and product access
• clock drift, token revocation, account policy changes and future endpoint behavior
• missed messages, silent stale streams, proxy drops and partial channel recovery
• whether the exchange exposes every lost private event for replay
• private account eligibility, future rate limits and support-side recovery

实用结论

Coinbase Advanced Trade WebSocket 与 Kraken WebSocket v2 应按 session-control system 比较，而不是只当作行情流端点。Coinbase 记录了 Advanced Trade WebSocket overview、endpoints 与 authentication；Kraken 记录了 WebSocket v2 channels 和 WebSockets token route。实用结论是：把 API-key scope、authentication payload、token freshness、heartbeat/liveness evidence、reconnect policy 与非秘密 order/market-data identifiers 拆开，之后才可判断某个流是否能进入生产。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。