Back to catalog / Crypto quant workflows

Create a reproducible baseline strategy backtest

Pin strategy, market, wallet, fees, and time range and retain a baseline result.

Goal

Generate a historical baseline for fair comparison with later strategy versions.

Confirm candles, strategy file, pair whitelist, and starting balance. [backtest]
Run freqtrade backtesting --strategy MyStrategy --timerange 20240101-20250101 --dry-run-wallet 1000. [backtest]
Retain command, config hash, strategy version, data directory, and results; report profit, drawdown, trades, and exit reasons. [backtest]

The same strategy, config, and data reproduce the trade count and summary metrics.

If results use cached or different data, confirm the actual timerange and record versions before comparison.

Python 3.11+, Freqtrade installed, a pinned strategy, and a local user-data directory.

Use public market data and local history; treat every trading decision as research and never connect a live account.

Freqtrade notes backtests differ from dry-run/live execution; a baseline is a research reference, not a return promise.

These values describe the upstream repository, not popularity or likes for an individual skill or playbook.

No metrics snapshot is available yet.

License: GPLv3