Back to catalog / Crypto quant workflows
Export backtest trades for independent review
Retain individual trades and run settings so summary metrics can be recomputed.
Goal
Make results traceable to each entry, exit, and fee assumption.
Steps
- Run the backtest with a fixed strategy, range, and dataset. [backtest]
- Specify
--export tradesand--backtest-directory=user_data/custom-backtest-resultsfor trade-level output. [backtest] - Archive export, config, and command; independently recompute trade count and aggregate P&L. [backtest]
How to verify
Exported count matches the summary and sample trades show entry/exit times and reasons.
Troubleshooting
`--export none` omits trade records; rerun with `trades` explicitly.
Permissions
Prerequisites
- Python 3.11+, Freqtrade installed, a pinned strategy, and a local user-data directory.
Permissions
- Use public market data and local history; treat every trading decision as research and never connect a live account.
Limitations
The export contains simulated trades, not exchange fills or statements.
Pinned upstream source
- Repository
- freqtrade/freqtrade
- File path
- docs/backtesting.md
- Pinned commit
82e4c9604c51523f7e05c5a297167cf2b13a2129- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: GPLv3
Main topic
Build a reproducible crypto research workflow