Audits › hummingbot/hummingbot › Kraken
Bot × exchange
Does hummingbot work with Kraken?
The hummingbot README names Kraken as a supported exchange (README scanned 2026-09-17). We did not run the bot against Kraken: this page reports what the public code says and what the exchange itself publishes.
Kraken facts
- CoinGecko trust score
- 10 / 10 · rank 3
- Country
- United States
- Established
- 2011
- 24h volume (BTC, normalized)
- 0
- Puerto Rico residents
- Not verified: the eligibility page needs JavaScript to render (source, 2026-09-17)
- Derivatives
- CFTC-regulated perpetuals for U.S. clients since 2026-06-15, about 3x leverage (source, 2026-09-17)
- Official API
- Yes (spot); U.S. futures API access not confirmed (source, 2026-09-17)
Exchange data: CoinGecko public API and the exchange's own endpoints, 2026-09-17. More on the Kraken page.
What the audit says about running it live
From the hummingbot audit (2026-09-17), the controls that matter most once a live API key is connected:
| Control | Verdict | Evidence |
|---|---|---|
| API key permissions | Partial | GET /search/code?q="/withdraw" repo:hummingbot/hummingbot path:connector -> total_count 0 (2026-09-17) |
| Orphaned stop-loss | Absent | hummingbot/strategy_v2/executors/position_executor/position_executor.py, constructor: raises ValueError unless triple_barrier_config.stop_loss_order_type == OrderType.MARKET ("Only market orders are supported for time_limit and stop_loss") |
| Websocket and data reconnection | Partial | hummingbot/core/api_throttler/async_throttler.py (AsyncRequestContext.within_capacity, rate-limit waiting); hummingbot/core/web_assistant/connections/ws_connection.py (detects closed socket, raises ConnectionError, handles ping/pong) |
| Order rejection handling | Present | hummingbot/connector/client_order_tracker.py, process_order_not_found() |
| Position reconciliation with the exchange | Partial | hummingbot/connector/client_order_tracker.py, restore_tracking_states() and process_order_not_found() (lost_order_count_limit=3) |
Before you connect a key
- Create the API key with trading enabled and withdrawals disabled, and restrict it to your server's IP if Kraken allows it.
- Start in paper or dry-run mode if the bot has one (the README mentions it).
- Decide the maximum loss per day before the first order and check the bot can enforce it: see the circuit breaker control. If it cannot, the watchdog enforces it from outside with a read-only key.