Coinbase Advanced Trade 与 Kraken 订单预览和撤单控制对比
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Coinbase documentation says Advanced Trade v3 includes private endpoints for create order, cancel orders, list orders, list fills, get order and preview orders. 2. Coinbase documentation maps API-key permission levels such as view, trade and transfer to endpoint access. 3. Coinbase API-key guidance says credentials should be stored outside the code base and IP allowlisting is recommended for additional key security. 4. Kraken spot REST documentation says Cancel All Orders requires order creation or cancel-close order permissions and cancels all open orders. 5. Kraken futures documentation describes a dead man's switch endpoint where a timeout in seconds starts a countdown that cancels all user orders unless refreshed or deactivated with zero. 6. A responsible comparison separates order preview, permission scope, cancel scope, timer refresh behavior, partial fills, final state and non-secret reconciliation evidence.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Preview surface | Coinbase exposes an order preview endpoint while Kraken evidence here centers cancel scopes and timers | require a preview or dry-run equivalent before live order creation | whether every order type has a complete preview path |
| Permission scope | API keys differ by view, trade, transfer or cancel permissions | start with read-only or the smallest trade permission needed | whether inherited portfolio or sub-account scope is obvious |
| Cancel scope | batch cancel, cancel-all and dead-man controls remove different sets of orders | write down which orders the cancel command can touch | whether partially filled orders leave residual exposure |
| Timer behavior | a dead man's switch depends on continuous refresh and timeout interpretation | test timer refresh, zero deactivation and outage behavior outside production | whether network jitter causes unwanted cancellation |
| Final order state | accepted, open, pending, canceled and filled states are not interchangeable | query final state before retrying or replacing an order | whether stale local state hides an executed fill |
| Evidence hygiene | debug logs are useful only if they omit secrets and balances | store endpoint, request id, client id, non-secret timestamps and result class | what private support data may still be required |
来源地图
- Coinbase Developer Platform：Create API Keys on Coinbase Developer Platform（coinbase-auth）
- Coinbase Developer Platform：Advanced Trade API Endpoints（coinbase-endpoints）
- Kraken API Center：Cancel All Orders（kraken-cancel-all）
- Kraken API Center：Dead man's switch（kraken-deadman）
控制说明
1. Preview surface
这一项要求读者把公开来源翻译成操作规则。这里的含义是：Coinbase exposes an order preview endpoint while Kraken evidence here centers cancel scopes and timers。可执行动作是：require a preview or dry-run equivalent before live order creation。仍然未知的是：whether every order type has a complete preview path。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Permission scope
这里的含义是：API keys differ by view, trade, transfer or cancel permissions。可执行动作是：start with read-only or the smallest trade permission needed。仍然未知的是：whether inherited portfolio or sub-account scope is obvious。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Cancel scope
这里的含义是：batch cancel, cancel-all and dead-man controls remove different sets of orders。可执行动作是：write down which orders the cancel command can touch。仍然未知的是：whether partially filled orders leave residual exposure。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Timer behavior
这里的含义是：a dead man's switch depends on continuous refresh and timeout interpretation。可执行动作是：test timer refresh, zero deactivation and outage behavior outside production。仍然未知的是：whether network jitter causes unwanted cancellation。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Final order state
这里的含义是：accepted, open, pending, canceled and filled states are not interchangeable。可执行动作是：query final state before retrying or replacing an order。仍然未知的是：whether stale local state hides an executed fill。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
6. Evidence hygiene
这里的含义是：debug logs are useful only if they omit secrets and balances。可执行动作是：store endpoint, request id, client id, non-secret timestamps and result class。仍然未知的是：what private support data may still be required。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- whether every order type has a complete preview path
- whether inherited portfolio or sub-account scope is obvious
- whether partially filled orders leave residual exposure
- whether network jitter causes unwanted cancellation
- whether stale local state hides an executed fill
- what private support data may still be required
实用结论
Coinbase Advanced Trade 与 Kraken 暴露的订单控制表面不同，因此有用的比较不是品牌偏好，而是失败模式覆盖。Coinbase 文档列出 Advanced Trade v3 的 create order、batch cancel、list orders、fills、get order 与 preview orders，并将 API-key 权限拆为 view、trade 与 transfer。Kraken 文档说明 spot cancel-all 权限，也提供 futures dead man's switch endpoint，可在用户停止刷新计时器后撤销订单。安全决策记录应在生产自动化下单前比较 preview、permission、cancel scope、timer behavior、final order state、partial fills 与非秘密证据。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相關專題與工具:任選兩家交易所比較
來源與證據
04- Create API Keys on Coinbase Developer Platform
- Advanced Trade API Endpoints
- Cancel All Orders · docs-legacy.kraken.com
- Dead man's switch · docs.kraken.com