Kraken Earn Deallocate Status API 就绪清单
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Kraken's Deallocate Earn Funds documentation says the endpoint deallocates funds from a strategy and requires Earn Funds permission. 2. Kraken's Deallocate Earn Funds documentation says the amount and strategy ID are required fields. 3. Kraken's Deallocate Earn Funds documentation describes asynchronous handling and status polling when a 202 response is returned. 4. Kraken Earn status documentation describes a pending field for dispatched allocation or deallocation operations. 5. Kraken's Get API Key Info documentation lists permissions, restrictions, nonce window, validity and last-used fields for the authenticated API key. 6. An Earn deallocation workflow should not expose API secrets, API signatures, 2FA codes or private account data in the evidence log.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Permission scope | Earn operations depend on key permissions rather than general login state | confirm the key has only the permissions needed for the test | private account policy not visible in public docs |
| Strategy identity | the strategy ID anchors which Earn position is being changed | record strategy ID as a non-secret operational identifier | renamed strategies in a private account UI |
| Nonce handling | authenticated calls require nonce and signature handling | use the client library or signing routine without logging secrets | clock or nonce-window edge cases under retries |
| Async status | deallocation can require status polling before it is final | poll status and record pending false before downstream accounting | latency during exchange-side maintenance |
| Operation concurrency | one operation can be in progress for a strategy | avoid parallel deallocation attempts on the same strategy | operator race conditions across multiple bots |
| Error mapping | minimum amount, busy state and invalid strategy errors need separate recovery actions | map each error to a stop rule instead of blind retry | future API error wording changes |
| Evidence hygiene | debugging can prove status without leaking authentication material | log endpoint name, non-secret error class, timestamp and request intent only | screenshots that accidentally reveal balances or key names |
来源地图
- Kraken Developers：Deallocate Earn Funds（kraken-deallocate-earn）
- Kraken Developers：Get Deallocation Status（kraken-deallocation-status）
- Kraken Developers：Get Allocation Status（kraken-allocation-status）
- Kraken Developers：Get API Key Info（kraken-api-key-info）
控制说明
1. Permission scope
这一项要求读者先把公开来源翻译成操作规则。这里的含义是：Earn operations depend on key permissions rather than general login state。可执行动作是：confirm the key has only the permissions needed for the test。仍然未知的是：private account policy not visible in public docs。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、恢复保证、结算保证、可用性保证、价格暗示或平台排名。
2. Strategy identity
这里的含义是：the strategy ID anchors which Earn position is being changed。可执行动作是：record strategy ID as a non-secret operational identifier。仍然未知的是：renamed strategies in a private account UI。
操作测试也必须很窄。这就是本节保留边界的原因。
3. Nonce handling
这里的含义是：authenticated calls require nonce and signature handling。可执行动作是：use the client library or signing routine without logging secrets。仍然未知的是：clock or nonce-window edge cases under retries。
操作测试也必须很窄。这就是本节保留边界的原因。
4. Async status
这里的含义是：deallocation can require status polling before it is final。可执行动作是：poll status and record pending false before downstream accounting。仍然未知的是：latency during exchange-side maintenance。
操作测试也必须很窄。这就是本节保留边界的原因。
5. Operation concurrency
这里的含义是：one operation can be in progress for a strategy。可执行动作是：avoid parallel deallocation attempts on the same strategy。仍然未知的是：operator race conditions across multiple bots。
操作测试也必须很窄。这就是本节保留边界的原因。
6. Error mapping
这里的含义是：minimum amount, busy state and invalid strategy errors need separate recovery actions。可执行动作是：map each error to a stop rule instead of blind retry。仍然未知的是：future API error wording changes。
操作测试也必须很窄。这就是本节保留边界的原因。
7. Evidence hygiene
这里的含义是：debugging can prove status without leaking authentication material。可执行动作是：log endpoint name, non-secret error class, timestamp and request intent only。仍然未知的是：screenshots that accidentally reveal balances or key names。
操作测试也必须很窄。这就是本节保留边界的原因。
仍需明确的未知项
- private account policy not visible in public docs
- renamed strategies in a private account UI
- clock or nonce-window edge cases under retries
- latency during exchange-side maintenance
- operator race conditions across multiple bots
- future API error wording changes
- screenshots that accidentally reveal balances or key names
实用结论
Kraken Earn API 操作应被视为异步资金控制流程，而不是一次按钮点击的结果。Kraken 文档说明，Deallocate Earn Funds 需要 Earn Funds API key permission、amount 与 strategy ID，并且当返回 202 时需要轮询 deallocation status；状态端点还会暴露 pending state，Get API Key Info 可查看 key 的 permission、restriction 与 usage timestamp。实用结论是：在把资金视为可用之前，先核验 key permission、strategy ID、nonce handling、同一 strategy 一次只能有一个操作，以及 status polling。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、回调、政策框架、结算路径或流动性头寸在任何未来条件下都能成功的承诺。
相關專題與工具:交易所 API 與行情資料核查
來源與證據
04- Deallocate Earn Funds · docs.kraken.com
- Get Deallocation Status · docs.kraken.com
- Get Allocation Status · docs.kraken.com
- Get API Key Info · docs.kraken.com