One trading day of Kraken spot data at one-minute resolution, so you can run a
backtest the day you install TraderWe instead of waiting for your own recording to build up.
| |
|---|
| Venue | Kraken |
| Market | spot |
| Symbols | 29 |
| Rows | 36,068 |
| Window | 2026-08-11 20:00 to 2026-08-12 20:00 ET |
| Symbol format | BTC-USD |
Symbols in this file include
BTC-USD,
ETH-USD,
SOL-USD,
ADA-USD,
XRP-USD,
HYPE-USD and 23 more.
Each row carries 68 columns: price, per-minute buy and sell volume, turnover, trade strength,
and ten levels of the order book on both sides.
1. Loading it
Because the venue is not in the filename,
only one venue can occupy that folder at a time.
Swap the file when you want to test a different one. We know this is awkward and it is on our
list to fix.
1) Put the file in your data folder under
record/crypto/1m/ — create the folder if it is not there.
2) Rename it to
crypto_1m_20260812.db. The app reads the asset class from the folder and the date from
the filename; the venue is not part of either.
3) Open Backtest. The date shows up in the available-data list and you can run against it.
2. What this is
Our own recording, captured from Kraken's public market data feed by our recorder in Tokyo.
Nothing here comes from a paid data vendor. One day at one-minute resolution is a sample for
evaluating the software. It is not a data product, and it is not a substitute for recording your
own. Serious research wants more days than this and the one-second frame.
Kraken publishes BTC as XBT on its REST API; the recording normalises it to BTC-USD so the same strategy runs across venues without renaming. The quiet-market ticker behaviour we wrote about in Research is visible in this file if you look for flat stretches.
If a download looks short, check the SHA-256 shown next to the file. A truncated database opens
as a corrupt file rather than failing loudly.
