Simulation Wizard Guide

Passing the BitThor Simulation Wizard

Before any bot can proceed to live trading, it must pass the Simulation Wizard. This guide walks you through the Golden Rules prerequisites your data must meet, decodes the three most common HTTP 400 failure codes, and tells you exactly what to do next after a successful run.

Risk Disclosure: Disclaimer: Trading real capital involves substantial risk, including the potential loss of principal. Simulation results are based on historical data and do not guarantee future performance. Passing the Simulation Wizard means your historical data met the required format and completeness thresholds — it does not constitute a recommendation to trade or a guarantee of future results.

Phase 1

Golden Rules: What Your Data Must Meet

The Simulation Wizard enforces a set of non-negotiable data rules before it will run. These checks exist to protect you from reviewing results that are based on incomplete or structurally invalid historical data. Meeting these prerequisites does not guarantee a profitable simulation — it guarantees the simulation had enough valid data to run safely.

Minimum candle requirement

Your symbol's historical dataset must contain at least 50 candles before the simulation can begin. The wizard checks this before dispatching any computation. If your selected symbol does not have 50 recorded candles in the lookback window, the wizard will stop and return INSUFFICIENT_DATA_LOOKBACK.

Non-zero OHLCV requirement

Every candle in the dataset must have non-zero values in all five OHLCV fields: Open, High, Low, Close, and Volume. Any candle with a zero or null value in a critical field causes the wizard to stop with DATA_INTEGRITY_EXCEPTION. BitThor stops early to ensure you are not reviewing results computed on corrupted or missing price data.

  • Ensure your symbol has at least 50 candles of historical data recorded before running the simulation.
  • Verify that no OHLCV field contains a zero or null value across the full lookback window.
  • Do not modify bot settings after the simulation has run — changing settings invalidates the configuration hash and will require a re-run.
Phase 2

Decoding Common Simulation Failure Codes

All three failure codes below return HTTP 400. They are data requirements or configuration mismatches — not fatal flaws in your strategy. Each has a specific, actionable fix.

INSUFFICIENT_DATA_LOOKBACK — HTTP 400

What it means

The requested lookback window did not provide the minimum required candles (at least 50) for the simulation to run safely. BitThor requires this threshold to produce statistically meaningful indicator readings.

How to fix it

  • Switch to a symbol with more historical data or extend the date range in your bot's configuration to cover a longer lookback window.
  • If you recently added the symbol, wait for BitThor to record additional candles before re-running the simulation.
HASH_MISMATCH — HTTP 400

What it means

The bot configuration the simulation used is different from the configuration currently stored for your active bot. This is a security and configuration-integrity check that prevents you from validating one configuration and activating a different one.

How to fix it

  • Do not change any bot settings after starting a simulation. If you made changes, re-run the simulation with the updated settings before attempting to proceed.
  • If the app has been open for a long time without a refresh, reload the page to sync the bot settings view, then re-run the simulation.
DATA_INTEGRITY_EXCEPTION — HTTP 400

What it means

The historical OHLCV data contains null values, zero values in critical fields, or a structurally malformed dataset. BitThor stops early to prevent you from reviewing results computed on corrupted or incomplete price data.

How to fix it

  • Check your symbol's data source to confirm all OHLCV fields are populated with non-zero values for the selected lookback window.
  • If you are using a custom data import, verify the dataset structure matches the required OHLCV column format before re-importing and re-running.
Phase 3

What to Do Next

Once the simulation runs to completion without a failure code, you will see the Simulation Summary Card with the Signal Impact Score, win rate, and total P&L. From here, review the summary carefully before deciding to proceed.

  • Review the Signal Impact Score and session P&L — understand what drove the result before acting on it.
  • Complete the risk disclosure review and answer the three-question quiz in the Simulation Summary Card before the next-step button unlocks.
  • Proceed to the deployment walkthrough only after confirming that the simulation result matches the risk profile you are prepared to accept in live trading.
Legal Disclaimer

Passing the Simulation Wizard only confirms that your historical data met the required format and completeness thresholds for the simulation to run. It does not guarantee future trading success, profitability, or sustained performance. Past performance does not guarantee future results. Cryptocurrency trading involves substantial risk of loss and is not suitable for every user. BitThor provides software tools only and does not provide investment advice. Users should only trade with capital they can afford to lose and should always conduct thorough due diligence.

Return to Getting Started

Risk Disclosure: Disclaimer: BitThor is an analytical simulation and backtesting tool, not a trading signal provider or financial advisory service. BitThor provides software tools only and does not provide investment advice. All results generated are based on historical data and simulation parameters provided by the user. Past performance, including simulated results, does not guarantee future results. Cryptocurrency trading involves substantial risk of loss and is not suitable for every user. Users should only trade with capital they can afford to lose and should always conduct thorough due diligence.