Cryptocurrency News & Market Updates

TL;DR

• Most multi-strategy operations need two layers of separation: process isolation (one API key per process) and strategy isolation (subaccounts with their own balances, P&L, and risk surface). Kraken supports both natively.

• Multiple API keys solve process problems inside one account: separate nonce sequences, scoped permissions, clean blast radius if a single key is compromised.

• Subaccounts isolate each strategy across linked accounts: separate balances, separate margin calculations, separate per-account rate limits, while still consolidating into one volume tier for fees.

• Subaccounts on Kraken Derivatives are open to any eligible client (set up via support ticket); on Kraken Spot they are gated to institutional clients via the Kraken institutional team.

• Run one API key per process. Most “invalid nonce” errors in production are one key shared across multiple processes, not a clock-skew problem.

Two layers of separation: process isolation vs. strategy isolation

The core architectural question for systematic traders is how to separate strategies, permissions, and balances across accounts and processes. Kraken provides two distinct answers, operating at different layers.