Backtesting
How to Run Your First Crypto Backtest
A practical first-backtest workflow for crypto spot strategy research: choose a finalized version, configure assumptions, run the test, and read the first result.
Traseq··6 min read
A practical first-backtest workflow for crypto spot strategy research: choose a finalized version, configure assumptions, run the test, and read the first result.
Start with a no-code crypto spot strategy, lock the version, run the backtest, and keep the result traceable for comparison.
To run your first crypto backtest, start with a finalized strategy version, choose a supported market and timeframe, set the date range, initial capital, fees, and slippage assumptions, then review the result as historical research evidence. The point is not to prove that a strategy will work live. The point is to learn how the rule set behaved in the past under explicit assumptions.
In Traseq, that workflow is focused on crypto spot research. Traseq is not a live trading or exchange execution platform, and backtests do not guarantee future results.
A first crypto backtest should answer five questions:
If the answer is unclear, do not optimize yet. First fix the strategy definition, the test settings, or the way you are reading the result.
A backtest should run against a stable strategy, not a moving draft.
In Traseq, a finalized Ready version is locked for backtesting. That gives the result a stable reference point: the backtest can point back to the exact rules, version, market, timeframe, range, and execution settings that produced it.
This prevents a common research problem. If you edit the rules after seeing the result, you may forget which version produced which backtest. That turns research into guesswork.
If you have not built a strategy yet, start with How to Build a Crypto Strategy Without Code or the first strategy guide.
The market and timeframe are not cosmetic settings. They define the behavior you are testing.
Use the timeframe to match the strategy idea:
Traseq's current main workflow focuses on crypto spot research and supports 15m, 1h, 4h, and 1d timeframes. The main workflow exposes major USDT spot pairs across large-cap and high-volume tokens.
When in doubt, start with a larger timeframe such as 4h or 1d. Shorter timeframes scan more bars, create more opportunity for fees and slippage to matter, and can make weak rules look active without making them useful.
The date range decides which market regimes the strategy sees.
A first test can use a simple preset such as:
3M for a fast recent behavior check6M for a broader first look1Y or 2Y for a more serious baselineDo not treat one date range as the whole truth. A strategy that looks clean during a trending market may fail in a sideways period. A strategy that survives a volatile period may still be too inactive in calmer markets.
The first backtest is a baseline, not a verdict.
Many first backtests look better than they should because costs are ignored.
At minimum, review:
In Traseq, new workspaces can begin from workspace defaults, and the backtest panel lets you review fees, slippage, and execution presets before running. Signal-driven entries and exits fill at the next bar open, and fees and slippage are applied after the theoretical fill price is determined.
After the settings are ready, run the backtest. When it finishes, do not start by asking whether the return is high enough.
Start with this review order:
The result page is not just a scorecard. It is a debugging surface for the strategy idea.
For metric interpretation, read Backtest Metrics and the reading backtest results guide.
After the first backtest, pick one next action:
Avoid changing many things at once. If you adjust entry, exit, timeframe, and costs all together, the second result may differ, but you will not know why.
The first backtest creates a baseline. The second backtest starts the actual research process.
Useful comparison questions include:
1h versus 4h?In Traseq, comparison sets let you put backtests side by side across performance, risk, conditions, and time periods. For the full workflow, read How to Compare Backtest Results or the comparison guide.
A crypto backtest is a historical simulation of a strategy's rules on past market data. It shows what would have happened under the selected assumptions, but it does not predict or guarantee future performance.
You need a finalized strategy version, a supported trading pair, a timeframe, a date range, initial capital, and explicit fee and slippage assumptions.
Start with the timeframe that matches the idea. 4h and 1d are often easier for a first review because costs and noise are less likely to dominate than on very short timeframes.
Not immediately. First confirm that the rules behaved as intended, the trade count is reviewable, and the cost assumptions are explicit. Then create one controlled variation and compare.
No. Traseq is a crypto spot strategy research workspace. It does not place live orders or connect to exchange accounts for execution.
| Timeframe | Better first use case |
|---|
1d | Medium or long-term trend research |
4h | Swing-style strategy research |
1h | Intraday to short-swing research |
15m | Shorter-term experiments where costs need extra attention |
| Result pattern | Practical next step |
|---|
| No trades | Loosen the entry or confirm the conditions are reachable |
| Very few trades | Test a longer range or simplify the setup |
| Many small losses | Review costs, exit logic, and trade frequency |
| Good return with deep drawdown | Study risk before optimizing return |
| Cleaner result than expected | Create a controlled v2 and compare |
Nov 1, 2025