BitThor
BitThor
  • Getting Started
  • Features
  • Blog
  • Documentation
  • Download
  • Leaderboard
  • Have an issue?

FAQ

FAQ


Simulation Troubleshooting Hub

Resolve the three most common onboarding simulation blockers

Use this plain-language guide when the starter simulation stops before completion. Start with the code shown in BitThor, follow the non-technical steps below, and rerun the same request once the issue is cleared.

Simulation Code
INSUFFICIENT_DATA_LOOKBACK

BitThor needs more historical candles before it can test this setup

The starter simulation needs at least 50 candles to warm up the indicators safely. If the selected history window is too short, BitThor stops early instead of showing a misleading result.

  1. Switch to a supported symbol with deeper bundled history, such as BTCUSDT or ETHUSDT.
  2. If you narrowed the candle window or changed the data source, widen it so the run includes at least 50 complete candles.
  3. Run the data check again before starting the sample simulation.
When to rerun. After the longer history is available, rerun the same simulation request.
Simulation Code
HASH_MISMATCH

BitThor detected a settings change between review and simulation

This usually means the saved bot settings changed after the current page loaded. BitThor stops so you do not validate one configuration and activate another by mistake.

  1. Reload the bot or reopen the setup wizard so the latest saved settings are back in view.
  2. Confirm the symbol, indicator settings, and risk controls still match what you expect.
  3. Run the simulation again only after the refreshed settings are visible.
When to rerun. Use Try Again after the page reflects the latest saved bot configuration.
Simulation Code
DATA_INTEGRITY_EXCEPTION

BitThor found a data or simulation-record integrity problem

BitThor stopped because the historical candles, simulation payload, or audit record did not pass an integrity check. This protects you from reviewing incomplete or inconsistent results.

  1. Refresh the page and rerun the onboarding data check so BitThor can request a clean dataset.
  2. If you imported or edited historical data, replace incomplete rows or switch to a bundled supported symbol.
  3. If the issue repeats, restart BitThor so the simulation audit store can be rebuilt cleanly before you continue.
When to rerun. Try Again reuses your last simulation parameters after the data or audit issue is cleared.
Legal Disclaimer. This troubleshooting guide is provided for educational and product-support purposes only. It does not constitute financial, investment, or trading advice. Simulation checks and results are based on historical information and platform state, do not guarantee future performance, and do not remove the risk of loss when real capital is used.
Open Full Getting Started Guide  Back to Documentation 
Knowledge Base
Simulation error? Get a plain-language fix.

The three most common simulation failure codes — explained in plain language with step-by-step remediation that mirrors the in-app Remediation Panel.

Open the Troubleshooting Guide 
Knowledge Base
Preparing to run your first simulation?

Review the Golden Rules prerequisites and common failure codes before you run — so you know exactly what the wizard checks and what to do if it stops.

Read the Simulation Wizard Guide 
Knowledge Base
Configuration Hash Mismatch? Restore connectivity in four steps.

Understand what a Bot Configuration Hash is, why mismatches occur, and how to re-validate your settings before proceeding to live deployment.

Read the Hash Mismatch Recovery Guide 
Knowledge Base
When indicators disagree: advanced conflict resolution diagnostics.

Learn how to diagnose complex signal conflicts (RSI vs. MACD divergence, HT vs. EMA decay) and understand the technical limitations of multi-indicator configurations.

Read the Bot Failure Remediation Guide 
Knowledge Base
What happens in the 3-step Deployment Walkthrough?

The full walkthrough guide explains each server-side gate, what it checks, why it matters, and what to do if it fails.

Read the guide 

The server recomputes your bot’s configuration hash and compares it against the hash recorded when you ran the simulation. If your bot settings have changed since the simulation, the hashes will not match and deployment is blocked. This ensures you always activate the exact configuration that was tested. To resolve a mismatch, close the modal, review your settings, and re-run the simulation.
When the hash check passes, the server issues a 5-minute activation token tied to this bot and session. If the same valid configuration is confirmed again within the window, the server returns the same token. After 5 minutes the token expires and a fresh validation pass is required. If you take longer than 5 minutes between opening the modal and submitting, close and re-open it to start a new window.
BitThor confirms that its live market analyzer is in an active, connected state before issuing the deployment token. If the analyzer is not yet connected or is still starting up, deployment is blocked until the connection is healthy. If you see this error, wait a moment for the system to finish connecting, then close and re-open the modal to try again.

Indicator FAQ


Hilbert Transform

What it measures
  • Hilbert Transform techniques estimate phase and cycle structure in a price series.
  • Analysts use it to study whether market behavior appears more trend-driven or more oscillatory over a given window.
How it's used
  • It is commonly reviewed alongside moving averages and volatility measures to understand whether a market regime is changing.
  • In practice, it can help frame the difference between persistent directional motion and short-lived cyclical movement.
Simple Analogy

It is similar to listening for rhythm changes in a song to determine whether the beat is steady or shifting.

VWAP

What it measures
  • VWAP, or Volume-Weighted Average Price, measures the average traded price after weighting each observation by traded volume.
  • It summarizes where most transaction activity has been concentrated during the measured period.
How it's used
  • It is often used as a benchmark when comparing the current price with the volume-weighted average participation level.
  • Researchers may also compare price distance from VWAP to study short-term deviation and reversion behavior.
Simple Analogy

It is like calculating a class average where larger exams count more than smaller quizzes.

RSI

What it measures
  • RSI, or Relative Strength Index, compares the magnitude of recent upward closes with recent downward closes on a normalized 0 to 100 scale.
  • Its purpose is to describe momentum intensity rather than absolute price level.
How it's used
  • Analysts use RSI to examine whether recent movement has become unusually stretched relative to its own short-term history.
  • It is typically reviewed with trend and volume context because isolated momentum readings can persist longer than expected.
Simple Analogy

It resembles a temperature gauge that shows how heated or cooled recent price movement has become.

ML FastTree Prediction

What it measures
  • FastTree is a gradient-boosted decision tree model that estimates an output from a set of historical input features.
  • In trading workflows, those features can include price, volume, indicator values, and derived market-state signals.
How it's used
  • It is commonly used as a probabilistic forecasting component that compares current feature patterns with archived observations.
  • Because market regimes change over time, model outputs are typically reviewed with validation data, risk limits, and non-ML indicators.
Simple Analogy

It is like comparing today's conditions with many prior case studies to estimate what similar patterns tended to look like.

ADX

What it measures
  • ADX, or Average Directional Index, measures the strength of a trend without specifying whether the direction is upward or downward.
  • It is derived from directional movement calculations and is intended to separate stronger trends from lower-strength market noise.
How it's used
  • Analysts often pair ADX with directional indicators to distinguish trend strength from trend direction.
  • It can help frame whether a market is moving with enough persistence for a trend-based model to remain relevant.
Simple Analogy

It is like measuring how forcefully a vehicle is accelerating without using that reading to say which road it will take next.

Risk Warning. Past performance does not guarantee future results.
Choose Platform

Download BitThor for Your Desktop


Get BitThor for your desktop and choose the platform that matches your machine before continuing.

Windows
Windows

Windows 10 & 11

Download BitThor for desktop
Linux
Linux

All major distributions

Download BitThor for desktop
macOS
macOS (Intel)

Intel processor

Download BitThor for desktop

Choose a platform before you continue  ·  Version 0.0.89.4  ·  All versions →

Risk Disclosure: Cryptocurrency trading involves substantial risk of loss and is not suitable for every user. Review your bot settings carefully before live trading. BitThor provides software tools only and does not provide investment advice. ML-based forecasting and predictive signals are analytical tools only and are not guarantees of future performance or profit.

BitThor

  • Features
  • How It Works
  • Download
  • Getting Started
  • Blog
  • FAQ's
  • Contact Us
  • Our Discord
  • Winning Recipes
  • Privacy Policy
  • Terms of Service