출처 검증 리서치: Kraken EARN Deallocate Status

Decision Matrix

Source Map

• 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)

Control Notes

1. Permission scope

Permission scope is the decision point where public documentation must become an operating rule. In this package, it means Earn operations depend on key permissions rather than general login state. The practical action is to confirm the key has only the permissions needed for the test. The unresolved edge is private account policy not visible in public docs, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Strategy identity

Strategy identity is the decision point where public documentation must become an operating rule. In this package, it means the strategy ID anchors which Earn position is being changed. The practical action is to record strategy ID as a non-secret operational identifier. The unresolved edge is renamed strategies in a private account UI, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Nonce handling

Nonce handling is the decision point where public documentation must become an operating rule. In this package, it means authenticated calls require nonce and signature handling. The practical action is to use the client library or signing routine without logging secrets. The unresolved edge is clock or nonce-window edge cases under retries, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Async status

Async status is the decision point where public documentation must become an operating rule. In this package, it means deallocation can require status polling before it is final. The practical action is to poll status and record pending false before downstream accounting. The unresolved edge is latency during exchange-side maintenance, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Operation concurrency

Operation concurrency is the decision point where public documentation must become an operating rule. In this package, it means one operation can be in progress for a strategy. The practical action is to avoid parallel deallocation attempts on the same strategy. The unresolved edge is operator race conditions across multiple bots, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Error mapping

Error mapping is the decision point where public documentation must become an operating rule. In this package, it means minimum amount, busy state and invalid strategy errors need separate recovery actions. The practical action is to map each error to a stop rule instead of blind retry. The unresolved edge is future API error wording changes, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Evidence hygiene

Evidence hygiene is the decision point where public documentation must become an operating rule. In this package, it means debugging can prove status without leaking authentication material. The practical action is to log endpoint name, non-secret error class, timestamp and request intent only. The unresolved edge is screenshots that accidentally reveal balances or key names, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• 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

Practical Takeaway

Kraken Earn API operations should be handled as asynchronous fund-control workflows, not as a single button result. Kraken documentation says Deallocate Earn Funds requires the Earn Funds API key permission, amount and strategy ID, and that a 202 response requires polling deallocation status. Kraken status endpoints also expose a pending state, while Get API Key Info can show permissions, restrictions and usage timestamps for the key. The decision outcome is to verify key permission, strategy ID, nonce handling, one-operation-at-a-time behavior and status polling before treating funds as available. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.