Kraken Cancel-on-Disconnect 与 Coinbase 订单策略对比：API 订单生命周期控制

决策结论：Keep the bot in paper, sandbox or read-only mode until disconnect handling, order expiration, cancel behavior, fill reconciliation and duplicate-order prevention are tested with non-secret evidence. Do not infer a venue-level safety feature from a separate endpoint or order type.

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

事实审计：c1：Kraken documents a cancel-on-disconnect control for futures API trading, so disconnect behavior can be treated as an explicit bot design question rather than an afterthought. c2：Kraken WebSocket documentation separates streaming state from trading action, which means a bot still needs its own reconciliation path after connection loss. c3：Coinbase Advanced Trade documentation describes fulfillment policies such as GTC, GTD and IOC and maps them to order time-in-force behavior. c4：Coinbase documentation states downside protection in bracket orders is not guaranteed during high market volatility, so bots cannot treat an attached order as absolute risk removal. 这些声明都是窄声明，不证明个人资格、未来可用性、执行质量、来源措辞之外的监管状态、税务结果、恢复结果、钱包安全、投资适合性、流动性深度或平台偿付能力。

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

常见问题：一句话答案是什么？Kraken's cancel-on-disconnect control and Coinbase Advanced Trade order policies solve different API lifecycle problems. 应先核验什么？先核验官方来源和精确的用户控制面。哪些不能推断？个人资格、未来可用性、恢复结果、税务、执行质量、来源措辞之外的法律状态或客服结果都不能推断。什么时候停止？对象身份、权限、账户状态、网络路径、来源支持或失败处理不清楚时停止。