A plain-language explanation of crypto backtesting, what data it needs, what it can reveal, and where it can mislead traders.
Reviewed by Alphora Research
Updated June 20, 2026
What to remember
Point-in-time prices and timestamps
Funding, basis, and venue rule histories where relevant
Transaction cost and slippage assumptions
Universe membership and delisting treatment
Short answer
Crypto backtesting tests a trading strategy against historical crypto market data. It estimates how the rules would have behaved under past prices, funding, liquidity, fees, and execution assumptions before the trader risks live capital.
What a crypto backtest needs
A useful backtest needs the same inputs the live strategy would have had at the time: prices, funding, volumes, order book or slippage assumptions, exchange rules, universe membership, fees, and timestamps that prevent future data from leaking into earlier decisions.
Minimum useful dataset
The minimum dataset depends on the strategy, but crypto backtests usually need more than candles. Perp strategies often require funding histories, mark or index references, fee schedules, liquidation or maintenance margin assumptions, and liquidity snapshots or conservative slippage models.
If the live strategy would have seen a value only after the trade decision, the backtest should not use that value to form the earlier signal.
Point-in-time prices and timestamps
Funding, basis, and venue rule histories where relevant
Transaction cost and slippage assumptions
Universe membership and delisting treatment
A record of exactly which data was known at each decision time
What it can reveal
Backtesting can reveal whether a strategy idea ever had a plausible edge, when it tended to work, how painful the drawdowns were, and whether the implementation would have turned over too quickly to trade.
Where it can mislead
A backtest can look good because of overfitting, missing costs, survivorship bias, unrealistic fills, future data leakage, or a market regime that no longer exists. The backtest is evidence, not proof.
The strategy was tuned on the same window used to judge it
Execution assumes fills at prices the strategy could not actually get
The universe excludes assets that failed, delisted, or became illiquid
The result depends on one crisis, one exchange rule, or one lucky parameter
How Alphora frames backtests
Alphora treats a backtest as one artifact in a larger validation stack. The useful question is not only whether the return was high, but whether the rule is reproducible, explainable, robust to assumptions, and suitable for paper tracking before any later trading decision.