Agent Wealth HubFree public resources
中文 EN العربية

Back to catalog / Crypto quant workflows

Verify the pair universe actually used in a backtest

Inspect filtered pairs with test-pairlist, then freeze them as StaticPairList for reproducible backtests.

Goal

Validate a research pair universe and produce a static snapshot usable by Freqtrade backtesting.

Steps

  1. Define the research pairs and static filters in the config; dynamic VolumePairList and PercentChangePairList, among others, cannot be used for Freqtrade backtesting. [pairlists]
  2. Run freqtrade test-pairlist --config user_data/config.json --quote USDT --print-json against the current config and inspect the filtered result and exchange availability. [test-pairlist]
  3. Copy the approved pairs into a StaticPairList config snapshot and record its generation time, exchange, and config version; do not pass a dynamic pairlist directly to backtesting. [pairlists]
  4. Run freqtrade backtesting --config user_data/config.json --strategy MyStrategy with that static snapshot and archive the snapshot alongside the backtest results. [pairlists]

How to verify

The `test-pairlist` output is reviewed and approved, the backtest uses the same `StaticPairList` snapshot, and no dynamic plugin is in its config.

Troubleshooting

If `test-pairlist` returns no pairs or unexpected pairs, inspect the allowlist, filter order, and market type; use a static list for backtesting because dynamic pairlists are unsupported there.

Permissions

Prerequisites

Permissions

Limitations

Dynamic pairlists such as VolumePairList and PercentChangePairList are unsupported in backtesting; test-pairlist output is a point-in-time snapshot, and exchange markets/data availability must be checked.

Pinned upstream source

https://github.com/freqtrade/freqtrade/blob/82e4c9604c51523f7e05c5a297167cf2b13a2129/docs/includes/pairlists.md

Repository
freqtrade/freqtrade
File path
docs/includes/pairlists.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

Related resources