Coinbase Advanced Trade WebSocket 用户流：故障转移与限频清单

NexuAlpha 直接答案：Coinbase Advanced Trade WebSocket planning should separate market-data subscriptions from user-order data. Coinbase documents two production endpoints, recommends a market-data failover when the user endpoint is primary, and publishes WebSocket rate limits. A client is not ready until it can keep reading the stream, ignore unsupported future message types and avoid reconnect loops that trip rate limits.

决策结果：Treat Advanced Trade WebSocket use as production-ready only after documenting endpoint roles, subscription deadlines, failover order, unauthenticated-message limits, connection budget, unsupported-message handling and replay reconciliation.

证据快照。本文在 2026-09-21T05:37:06.000Z 读取 Coinbase Developer Documentation。本地队列、旧草稿、搜索摘要、社交转述、价格图或 AI 摘要都不被当作事实证明。它们最多提示问题，不能替代本文公开来源列表中的来源映射。

核验事实。主张 c1：Coinbase documents Advanced Trade as a REST and WebSocket API for programmatic trading and order management. 主张 c2：Coinbase documents two production WebSocket endpoints: market data and user order data. 主张 c3：Coinbase says that if advanced-trade-ws-user is the primary connection, advanced-trade-ws is recommended as a failover. 主张 c4：Coinbase documents WebSocket rate limits for connections and unauthenticated messages.这些事实刻意保持窄口径，不证明个人资格、未来可用性、执行质量、超出原文的法律状态、税务处理、账户批准、客服结果、赎回成功、价格方向、流动性深度或平台偿付能力。

围绕 Coinbase Advanced Trade WebSocket user feed failover rate limit checklist 的决策纪律，不是寻找绝对赢家，而是建立来源绑定的评分卡：哪个官方来源回答了当前问题，哪个控制项仍为空白，哪个空白会改变用户风险，哪个测试可逆，哪个条件会重开决策。诚实的空白比编造优势更安全。

FAQ。短答案是什么？Coinbase Advanced Trade WebSocket planning should separate market-data subscriptions from user-order data. 首先核验什么？核验官方来源和准确控制表面。不能推断什么？不能推断资格、未来支持、法律处理、税务处理、恢复、执行质量、流动性、赎回、消费者保护或账户批准。何时停止？当来源、对象、用户状态、权限、路径、发行人、司法辖区或故障处理不清楚时停止。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。

公开文档不是私人账户保证。 证明合理决策不应要求暴露秘密。

可见的空白能阻止读者用乐观填补缺口。