Coinbase 与 Kraken WebSocket 认证和重连控制对比

决策矩阵

来源地图

• Coinbase Developer Documentation：Welcome to Advanced Trade API（coinbase-ws-overview）
• Coinbase Advanced API Python SDK：Authentication（coinbase-jwt-sdk）
• Coinbase Help：WebSocket feeds（coinbase-help-websocket）
• Kraken Support：Kraken WebSocket API - Frequently Asked Questions（kraken-websocket-faq）
• Kraken Support：How to subscribe to the Kraken WebSocket private feeds（kraken-private-feeds）

控制说明

1. Credential object

这一项要求读者先把公开来源翻译成操作规则。这里的含义是：Coinbase evidence centers JWT construction while Kraken evidence centers a REST-issued token for private feeds。可执行动作是：document how each token is created without storing secrets。仍然未知的是：account-specific permission templates。因此本文不会把未知部分包装成安全承诺、收益承诺、官方背书、审批保证、恢复保证、可用性保证或注册诱导。

2. Private channel

这里的含义是：authenticated order or account feeds are different from public market feeds。可执行动作是：subscribe only after confirming the target channel type。仍然未知的是：venue-specific channel availability。

3. Reconnect proof

这里的含义是：a socket reconnect does not prove missed private events were replayed。可执行动作是：reconcile account and order state after every reconnect。仍然未知的是：events lost during disconnect windows。

4. Token lifetime

这里的含义是：token generation and session reuse are operational risk controls。可执行动作是：rotate or refresh according to documented venue behavior。仍然未知的是：future lifetime changes。

5. Logging hygiene

这里的含义是：debug evidence must show state without exposing JWTs, tokens or account identifiers。可执行动作是：redact every auth header and token-like value。仍然未知的是：internal log retention policy。

6. Fallback route

这里的含义是：REST state checks may be required after private-feed uncertainty。可执行动作是：pair streaming with a documented state reconciliation endpoint。仍然未知的是：rate-limit pressure during incidents。

7. Stop rule

这里的含义是：automation should stop when streamed private state and fetched account state diverge。可执行动作是：freeze retries until reconciliation succeeds。仍然未知的是：fills during websocket gaps。

仍需明确的未知项

• account-specific permission templates
• venue-specific channel availability
• events lost during disconnect windows
• future lifetime changes
• internal log retention policy
• rate-limit pressure during incidents
• fills during websocket gaps

实用结论

本文最有价值的地方是克制。Coinbase Advanced Trade 与 Kraken 都公开了 WebSocket 认证路径，但操作控制对象不同。Coinbase Advanced Trade 文档把 WebSocket 纳入 Advanced API 使用范围，Coinbase SDK 文档说明 JWT 可用于 Advanced Trade 请求和 WebSocket 连接。Kraken 支持文档则把公开行情 feed 与私有 feed 分开，说明私有账户数据和交易端点使用认证 URL，并要求先通过 REST API 获取有效认证 token。实用结论是：比较两家是否适合自动化前，应先拆分凭据生成、token 生命周期、私有频道订阅、重连证明、漏事件对账和非秘密日志。 用户应获得一个更清楚的核验路径，而不是一个看似肯定、实则无法由公开证据承担的承诺。