Back to catalog / Crypto quant workflows
Evaluate cooldown and drawdown protections in backtests
Explicitly enable protections and assess how lock conditions change trades and risk metrics.
Goal
Compare historical behavior before and after cooldown/drawdown protection.
Steps
- Define
CooldownPeriodorMaxDrawdownsettings, lookback, trade limit, and stop duration for the risk question. [protections] - Run
freqtrade backtesting --enable-protections ...on the same data and range. [protections] - Compare trades skipped during locks, drawdown, and profit; retain enabled and disabled results. [protections]
How to verify
Protections are explicitly enabled, lock behavior appears in results, and settings are reproducible.
Troubleshooting
If behavior does not change, verify activation and mode compatibility, then compare risk metrics with protections on and off.
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
Protections require `--enable-protections`; applicability depends on strategy and data.
Pinned upstream source
- Repository
- freqtrade/freqtrade
- File path
- docs/includes/protections.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