How to Set a Kraken Futures Stop-Loss Trigger Based on the Mark Price?

Understanding Mark Price in Kraken Futures

1. The mark price is a calculated value designed to prevent manipulation and reflect fair market value across exchanges.

2. Kraken Futures uses a composite index that aggregates prices from multiple top-tier spot exchanges weighted by liquidity.

3. This value is updated every second and serves as the reference for liquidation, margin calls, and stop-loss execution.

4. Unlike last traded price, the mark price incorporates funding rate adjustments and time-weighted averages to reduce volatility spikes.

5. It is published publicly via Kraken’s WebSocket feed under the markPrice field within the futures_ticker channel.

Kraken API Endpoints for Mark Price Retrieval

1. The REST endpoint /derivatives/api/v4/tickers returns real-time mark price for all active futures contracts.

2. Each response includes markPrice, indexPrice, and lastPrice in the same payload.

3. WebSocket subscription to futures_ticker provides sub-second updates with minimal latency.

4. The krakenfutures Python SDK exposes get_ticker() and subscribe_to_ticker() methods aligned with these endpoints.

5. Developers must parse the markPrice field explicitly — it is not auto-mapped into order parameters by default.

Stop-Loss Order Construction Using Mark Price

1. Kraken Futures supports stop and stop_market order types where trigger conditions are evaluated against the mark price.

2. When placing an order, set the trigger_price parameter equal to the desired mark price level.

3. Specify trigger_type: 'mark' in the order payload to enforce evaluation against the mark price rather than last or index price.

4. A long position requires a stop_market order with side: 'sell' and trigger_price below current mark price.

5. All such orders undergo validation at the gateway layer — invalid trigger types or missing trigger_type fields result in immediate rejection with error code InvalidTriggerType.

Order Lifecycle and Trigger Validation

1. Once submitted, the order remains in pending state until the mark price crosses the trigger_price.

2. Cross detection occurs on the exchange’s matching engine using atomic read of the latest mark price snapshot.

3. No historical lookback or trailing logic applies — only instantaneous comparison between live mark price and stored trigger value.

4. After triggering, the order transitions to live and enters the order book or executes immediately depending on type.

5. Failed triggers due to rapid price movement or connectivity loss are not retried automatically — clients must implement idempotent resubmission logic.

Frequently Asked Questions

Q: Can I modify the trigger_price of an existing stop-loss order?A: No. Kraken Futures does not support modifying trigger conditions post-submission. Cancel and re-submit with updated parameters.

Q: Does the mark price used for triggering differ between perpetual and quarterly futures contracts?A: No. Both contract types use identical mark price calculation methodology and source index composition.

Q: What happens if the mark price jumps over my trigger_price without hitting it exactly?A: The trigger activates on the first tick where mark price is >= trigger_price for sell stops or

Q: Is there a fee difference between mark-triggered and last-price-triggered stop orders?A: No. Kraken applies identical taker/maker fee schedules regardless of trigger type selection.