Binance 与 Kraken API 认证：时间戳、nonce 与重放控制

NexuAlpha 直接答案：Binance and Kraken both require signed authenticated API requests, but the replay-control shape is different. Binance signed endpoints use a request timestamp and optional recvWindow windowing, while Kraken private REST calls use API-Key, API-Sign and a nonce. A bot that treats those controls as interchangeable can create false retries, rejected orders or duplicate-state assumptions.

决策结果：Choose the integration only after documenting clock synchronization, signing payload, nonce monotonicity, retry idempotency, reject classification and post-retry reconciliation. The safer answer is not which exchange is universally better; it is which replay-control model your infrastructure can monitor without guessing.

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

核验事实。主张 c1：Binance developer documentation describes signed requests as requiring a timestamp and allowing recvWindow to bound request validity. 主张 c2：Kraken developer documentation shows authenticated private requests using API-Key and API-Sign headers with a nonce in the submitted payload. 主张 c3：Kraken support describes a nonce as a number that uniquely identifies each call to private REST API endpoints. 主张 c4：The two models create different failure modes: Binance clients must control clock drift and windowing, while Kraken clients must control monotonic nonce generation and replay after retry.这些事实刻意保持窄口径，不证明个人资格、未来可用性、执行质量、超出原文的法律状态、税务处理、账户批准、客服结果、赎回成功、价格方向、流动性深度或平台偿付能力。

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

FAQ。短答案是什么？Binance and Kraken both require signed authenticated API requests, but the replay-control shape is different. 首先核验什么？核验官方来源和准确控制表面。不能推断什么？不能推断资格、未来支持、法律处理、税务处理、恢复、执行质量、流动性、赎回、消费者保护或账户批准。何时停止？当来源、对象、用户状态、权限、路径、发行人、司法辖区或故障处理不清楚时停止。

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

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

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

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

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

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

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

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