Skip to content
QuantIDE
← Venues and comparisons

For Kraken

Kraken, without debugging a nonce.

Anyone who has wired Kraken by hand knows the ritual: the right permission boxes, the nonce window, an invalid-nonce error anyway, and a forum thread from years ago. That belongs in an adapter written against Kraken’s API, as code in your project. You describe the strategy.

The setup

The errors that have nothing to do with your edge.

Invalid nonce. Permission denied. Rate limit exceeded. None of these are trading problems, and all of them stand between an idea and a running process.

01State the strategy

Entries, exits, sizing and the drawdown you will not tolerate, in your own words rather than in JSON.

02Permissions kept narrow

Kraken scopes keys granularly: querying funds is a different permission from placing orders. The adapter is written to need only what the strategy uses, and never withdrawal rights.

03Nonces and rate limits in the adapter

Monotonic nonces and Kraken’s tiered rate counter are handled in the adapter, written against the API as a Model Context Protocol server in your repository, instead of surfacing as errors you have to interpret.

04Backtest, then build routing deliberately

History first. Live order routing is built and tested before it touches capital, then run at a size you would not mind being wrong about.

Held to account

Why there is no supported-exchanges list.

Tools in this category maintain a fixed roster of exchanges, and the roster is the reason for the monthly bill. QuantIDE ships the layer beneath it.

Not a pre-built integration

Kraken is not a feature we maintain. The adapter is written against its API in your project and is yours to read, fix and keep. A venue nobody has connected yet is connected the same way.

No withdrawal permission, ever

Kraken lets you scope a key narrowly, and a trading strategy has no business holding the right to move funds off the exchange. Query and order permissions are all it needs, and the key stays on your machine, never travelling with a Stack you share.

Rate tiers decide how fast you can trade

Kraken meters API calls against a tiered counter that decays over time, so a strategy that backtests well at one order a second may not be allowed to run that way. Testing surfaces that before your capital does.

Due diligence

Kraken, the questions asked first.

Why do Kraken integrations throw invalid nonce errors?

Kraken requires every signed request to carry a nonce larger than the last one that key used. Run two processes on one key, restart at the wrong moment, or let clocks drift, and you get rejections that look like an authentication failure but are not. It belongs in the adapter, not in your day, which is where it is handled.

Which API permissions should I enable?

Only what the strategy needs. Querying funds and placing orders are separate permissions on Kraken, and withdrawal rights are a third that a trading strategy has no business holding. The adapter is written to the narrow set and nothing more.

Do I have to write the code myself?

No. Describe what you want and it is written as readable source you own, in whatever language the job calls for. You can open it, change it, and ask what any part of it does.

Does it trade live on Kraken out of the box?

No. Nothing trades live out of the box. Order routing is built against Kraken’s API with your keys, and tested before it touches capital.

Where are my API keys stored?

On your machine, scoped to the one connection that uses them, and never included when a Stack is shared. The setup travels; your credentials do not.

Can I trade more than crypto?

Yes. There is no supported-venue list. Equities, futures and forex brokers are connected the same way: an adapter written against their API, in your project.

What does it cost?

One monthly plan: no tiers and nothing to unlock. Current terms are shown before you download rather than printed here. It runs on Windows, macOS and Linux, and you can cancel anytime.

Further

Where to go from here.

Start with the strategy. The nonce is handled.