Audits › 3cqs-coder/SymBot › Kraken
Bot × exchange
Does SymBot work with Kraken?
The SymBot README does not name Kraken directly, but it names ccxt, the exchange library that ships a Kraken adapter. Whether the bot's own code handles Kraken's rules (symbols, order types, rate limits) is not something a README scan can tell. 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
Audit scheduled
When the SymBot audit is finished, this section will show the verdicts for API key permissions, orphaned stops, reconnection, order rejection handling and position reconciliation: the five controls that matter most once a live key is connected.
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.