Coinbase Token Bucket 与 Kraken 交易限频计数器：订单控制清单

NexuAlpha 直接答案：Coinbase Exchange documents a token-bucket rate-limit model, while Kraken documents trading counters that rise with order events and decay over time. The practical control is not which limit sounds larger; it is whether the trading system can budget requests, cancellations and retries before the venue rejects the next action.

决策结果：Use either venue only after the client has per-surface budgets, backoff behavior, cancellation discipline, non-secret telemetry and a stop rule for rate-limit errors.

状态：已发布至 nexualpha.com

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

核验事实。主张 c1：Coinbase Exchange documentation describes REST, FIX and WebSocket rate limits and says Exchange REST and FIX rate limiting use a lazy-fill token bucket implementation. 主张 c2：Coinbase Exchange documentation lists separate public, private, FIX and WebSocket request ceilings plus an open-order maximum. 主张 c3：Kraken Support says trading rate limits apply separately per currency pair and can produce an EOrder:Rate limit exceeded error. 主张 c4：Kraken Support describes a counter that increases as orders are placed and cancelled and decreases over time at a fixed decay rate.这些事实刻意保持窄口径，不证明个人资格、未来可用性、执行质量、超出原文的法律状态、税务处理、账户批准、客服结果、赎回成功、价格方向、流动性深度或平台偿付能力。

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

FAQ。短答案是什么？Coinbase Exchange documents a token-bucket rate-limit model, while Kraken documents trading counters that rise with order events and decay over time. 首先核验什么？核验官方来源和准确控制表面。不能推断什么？不能推断资格、未来支持、法律处理、税务处理、恢复、执行质量、流动性、赎回、消费者保护或账户批准。何时停止？当来源、对象、用户状态、权限、路径、发行人、司法辖区或故障处理不清楚时停止。

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

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

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

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