Back to catalog / Crypto quant workflows
Verify historical funding rates for futures backtests
Separate historical funding from user-specified fallback assumptions.
Goal
Goal: Separate historical funding from user-specified fallback assumptions.
Steps
- Check the contract, range, and exchange funding-history availability. [leverage]
- Review
futures_funding_rate; document the configured fallback when historical funding is unavailable. [leverage] - Report funding source, gaps, and their impact on P&L separately. [leverage]
How to verify
Each funding value is traceable to history or clearly labeled as a scenario assumption.
Troubleshooting
Withhold return conclusions if source is unclear; do not backfill past periods with current rates.
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
Funding, leverage, and liquidation add major risk; this is historical research only.
Pinned upstream source
- Repository
- freqtrade/freqtrade
- File path
- docs/leverage.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