krakenfx/kraken-cli/kraken-earn-staking

kraken-earn-staking

Use this skill for:

• browsing available earn/staking strategies
• allocating funds to earn products
• deallocating (unstaking) funds
• monitoring current allocations and status

Discover Strategies

Lock types

• "bonded": The strategy has bonding and/or unbonding period that lock up funds
• "instant": Known as "flexible". The funds are immediately allocated or deallocated without a lock-up period
• "flex": Known as "auto-earn". No lock-up period. Funds are available for anything - trading, withdrawal, etc. without having to explicitly deallocate them

When communicating to client, use the front-end terminology rather than API terminology (so bonded, flexible and auto-earn).

Flex

• Better known as auto-earn
• Funds in eligible wallet (i.e. spot wallet) are implicitly allocated
• No lock-up period
• Funds cannot be explicitly allocated to or deallocated from a strategy via API — Auto-Earn manages this automatically based on settings
• Auto-earn preferences (enable/disable per yield source) can be set in user settings, but not via API
• The granularity of control per yield source: staking, opt-in-rewards, base-rewards
• can_allocate and can_deallocate on flex strategy are always false even if user is eligible for the flex strategy

Examples

List all strategies for an asset:

kraken earn strategies --asset ETH -o json 2>/dev/null

Filter by lock type:

kraken earn strategies --asset ETH --lock-type instant -o json 2>/dev/null
kraken earn strategies --asset DOT --lock-type bonded -o json 2>/dev/null

Paginate results:

kraken earn strategies --limit 10 --cursor <CURSOR> --ascending -o json 2>/dev/null

Key fields in each strategy (under .items[]): id, asset, apr_estimate, lock_type.type, user_min_allocation, user_cap, can_allocate, can_deallocate, yield_source.

Allocation Workflow

1. Pick a strategy from the list and note its id.
2. Record what is allocated to it now. In .items[], find the entry whose

strategy_id is that id, and note amount_allocated.total.native and amount_allocated.pending.native (a missing pending, or a strategy that is not listed, counts as zero): ``bash kraken earn allocations -o json 2>/dev/null ``

1. Allocate funds (requires human approval):

``bash kraken earn allocate <STRATEGY_ID> 1.5 -o json 2>/dev/null ``

1. Check allocation status (bonded strategies may have a lock-up period):

``bash kraken earn allocate-status <STRATEGY_ID> -o json 2>/dev/null ``

Deallocation Workflow

1. Record what is allocated to it now. In .items[], find the entry whose

strategy_id is the strategy's id, and note amount_allocated.total.native and amount_allocated.pending.native (a missing pending, or a strategy that is not listed, counts as zero): ``bash kraken earn allocations -o json 2>/dev/null ``

1. Deallocate (requires human approval):

``bash kraken earn deallocate <STRATEGY_ID> 1.0 -o json 2>/dev/null ``

1. Check deallocation status:

``bash kraken earn deallocate-status <STRATEGY_ID> -o json 2>/dev/null ``

Bonded strategies may have unbonding periods. The status response indicates whether funds are pending or available.

If earn allocate or earn deallocate returns a network error with "verify_first": true, the move may already have happened. Run kraken earn allocations -o json again, compare both values with the ones you recorded, and check kraken ledgers. Send the call again only if neither shows the move. earn allocate-status and earn deallocate-status only say whether a known move is still pending.

View Current Allocations

kraken earn allocations -o json 2>/dev/null

Filter out zero balances:

kraken earn allocations --hide-zero-allocations -o json 2>/dev/null

Convert to a reference currency for comparison:

kraken earn allocations --converted-asset USD --hide-zero-allocations -o json 2>/dev/null

Strategy Selection Pattern

When helping a user choose a strategy:

1. List strategies for the asset.
2. Compare apr_estimate, lock_type.type, and user_min_allocation.
3. Present a summary: flexible strategies offer instant access; bonded strategies lock funds for higher yield.
4. Confirm the user's choice before allocating.

Hard Rules

• Allocate and deallocate are flagged as dangerous. Never execute without explicit human approval.
• Always show the lock type and any unbonding period before allocation.
• For bonded strategies, warn the user that funds will be locked for the stated duration.
• Check can_allocate and can_deallocate fields before attempting operations.
• If you hit a mismatch between what you are trying to do and the CLI's interface or responses — including a mismatch between this skill and the installed CLI version's contract — feel free to submit feedback with kraken feedback.