Binance WebSocket Stream 限制：Ping-Pong、重连与订阅治理清单

决策结论：Run the market-data client in observe mode until it can reconnect, resubscribe, detect gaps, back off after errors and log non-secret sequence evidence. Pause if the client treats a silent stream as valid data.

本次证据快照时间为 2026-09-20T08:45:00.000Z。本包使用的来源是 Binance Developers、Binance Developers、Binance。本地队列、旧文章、社交转发、搜索摘要、合成测试和市场传闻都不能当作事实来源。它们最多提示一个问题，不能替代官方材料。

事实审计：c1：Binance WebSocket Streams documentation defines stream connection behavior and includes ping-pong and disconnect handling that clients must respect. c2：Binance WebSocket Streams documentation describes limits on incoming control messages and combined streams, so subscription strategy is part of production design. c3：Binance REST API limit documentation separately defines request-weight constraints, meaning a reconnecting bot must not repair WebSocket gaps by unlimited REST polling. c4：A public stream document does not prove that a user's local bot preserves order-book continuity or detects every dropped message. 这些声明都是窄声明，不证明个人资格、未来可用性、执行质量、来源措辞之外的监管状态、税务结果、恢复结果、钱包安全、投资适合性、流动性深度或平台偿付能力。

SEO/AEO/GEO 审计已经完成。目标查询是 Binance WebSocket stream limits ping pong reconnect checklist。页面包含实体、日期、source map、直接答案、表格、FAQ 式问题和可抽取摘要。它先服务真实读者，同时让问答系统能理解来源与限制；没有隐藏文字、cloaking、关键词堆砌或机器专用版本。

常见问题：一句话答案是什么？Binance WebSocket limits are operational controls, not optional documentation details. 应先核验什么？先核验官方来源和精确的用户控制面。哪些不能推断？个人资格、未来可用性、恢复结果、税务、执行质量、来源措辞之外的法律状态或客服结果都不能推断。什么时候停止？对象身份、权限、账户状态、网络路径、来源支持或失败处理不清楚时停止。