FAQ
FAQ
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.
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.
- Switch to a supported symbol with deeper bundled history, such as BTCUSDT or ETHUSDT.
- If you narrowed the candle window or changed the data source, widen it so the run includes at least 50 complete candles.
- Run the data check again before starting the sample simulation.
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.
- Reload the bot or reopen the setup wizard so the latest saved settings are back in view.
- Confirm the symbol, indicator settings, and risk controls still match what you expect.
- Run the simulation again only after the refreshed settings are visible.
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.
- Refresh the page and rerun the onboarding data check so BitThor can request a clean dataset.
- If you imported or edited historical data, replace incomplete rows or switch to a bundled supported symbol.
- If the issue repeats, restart BitThor so the simulation audit store can be rebuilt cleanly before you continue.
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.
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.
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.
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.
From Simulation to Live Trading: The 3-Step Journey
Learn how to move from a successful simulation to a live trading bot through the three critical stages of drafting, validation, and deployment gates.
What is a Blueprint Draft? (The Immutable Record)
A Blueprint Draft is a permanent, unchangeable snapshot of your bot’s configuration parameters. It serves as a diagnostic artifact and historical reference—not a prediction of future performance.
The Blueprint Draft: Compliance Artifact and Auditable Record
The Blueprint Draft gives risk, compliance, and operations teams a plain-language path from a completed simulation to an Auditable Record and then to deployment gate review.
Simulate & Audit
Review the historical run, trade records, and signal context as diagnostic evidence.
Archive to Blueprint Draft
Preserve the tested parameters as an immutable Compliance Artifact for later review.
Validate Gates
Check configuration hash, activation token, and connection readiness against the deployment workflow.
Understand the Auditable Record before validation
The explainer shows how the Compliance Artifact supports audit review without turning historical data into a forecast.
Establishing Your Blueprint: Documenting Your Strategy
A Blueprint Draft is a Compliance Artifact that records the user-selected strategy parameters, indicator settings, risk controls, and simulation context that existed during a completed historical run. The workflow is designed for documentation and later review, not for forecasting future market behavior.
What is documented?
The Blueprint records the configuration and historical simulation context used for a specific review point as an Auditable Record.
Why save it?
Saving the Blueprint creates a fixed historical record so later validation can reference the same parameters.
What it is not
It is not a forecast, a recommendation to trade, or a guarantee that live market conditions will resemble the historical test.
Deployment Failure Diagnostic Wizard
Enter your error code and follow the branching, step-by-step remediation path — covering HASH_MISMATCH, CONNECTION_ERROR, TOKEN_EXPIRED, and MISSING_MARKET_REGIME.
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.
Indicator FAQ
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.
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.
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.
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.
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.
Simulation Troubleshooting Hub
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.
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.
- Switch to a supported symbol with deeper bundled history, such as BTCUSDT or ETHUSDT.
- If you narrowed the candle window or changed the data source, widen it so the run includes at least 50 complete candles.
- Run the data check again before starting the sample simulation.
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.
- Reload the bot or reopen the setup wizard so the latest saved settings are back in view.
- Confirm the symbol, indicator settings, and risk controls still match what you expect.
- Run the simulation again only after the refreshed settings are visible.
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.
- Refresh the page and rerun the onboarding data check so BitThor can request a clean dataset.
- If you imported or edited historical data, replace incomplete rows or switch to a bundled supported symbol.
- If the issue repeats, restart BitThor so the simulation audit store can be rebuilt cleanly before you continue.
Download BitThor for Your Desktop
Get BitThor for your desktop and open the auditable control panel workflow on the platform that matches your machine.
Choose a platform before you continue · Version 0.0.89.5 · All versions →
Risk Disclosure: Download CTAs are provided for educational pattern recognition workflows and software evaluation only. This content does not constitute a recommendation for specific trading strategies. 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.