Simulation Run Save Blueprint Draft Validate Against History Deployment Gate Checks LIVE BOT
1

The Simulation Audit (Testing)

Goal

Determine whether your indicator combination produces meaningful trade decisions when modeled against historical market data.

What Happens

You run a simulation over 50 or more candles. The bot executes modeled trades based on its configured logic, logging every Buy, Sell, and Hold action and calculating a Signal Impact Score (SIS) that reflects the weighted historical contribution of each indicator family.

Key Takeaway

You see what the bot would have done given that historical data. These results are purely diagnostic — they measure modeled potential, not future market behaviour.

Action Point

Review your Signal Impact Score and Signal Breakdown to understand which indicators drove the bot’s modeled decisions before advancing.

2

Blueprint Drafting & Validation (Archiving the DNA)

Goal

Create an immutable, auditable snapshot of your validated configuration before connecting it to live funds.

What Happens

You use the Save Blueprint Draft feature. BitThor takes a deep snapshot of your bot’s exact parameters, indicators, and logic — this is your Bot DNA Profile. This draft is stored safely, allowing you to revisit and re-validate this exact setup even if you later adjust other settings.

Why This Matters

This step prevents configuration drift. By saving the DNA, you create a verifiable baseline. If the live bot’s parameters ever diverge from your saved draft, BitThor alerts you — because the active configuration no longer matches the one you tested.

Action Point

Save your Blueprint Draft. This action locks in your tested configuration DNA and is a prerequisite for the final deployment step.

3

Live Deployment & Gate Checks (Go-Live)

Goal

Safely connect your validated configuration to the live market analyzer through three automated verification gates.

What Happens

You initiate the final deployment sequence. This is a three-part technical verification, not a single switch:

  1. Configuration Hash Check — Verifies the live bot’s current settings still exactly match the saved Blueprint DNA hash recorded at simulation time.
  2. Activation Token & 5-Minute Window — The server issues a short-lived activation token once the hash check passes. This token must be consumed within five minutes, preventing a stale approval from being used after conditions change.
  3. Live Analyzer Connection Health — Confirms the live market analyzer is in an active, connected state before issuing the final activation signal.
The Result

Only when all three gates pass does BitThor activate your bot. Its status changes to Active and it begins monitoring the market using the exact configuration from your tested Blueprint Draft.

Action Point

Follow the on-screen prompts through the Deployment Readiness panel. If a gate fails, each failure includes a plain-language explanation and a recommended remediation step.

Related Guide

Passing the Simulation Wizard

Understand the three HTTP 400 failure codes and the minimum data prerequisites before your first run.

Read →

Related Guide

Blueprint Lifecycle Flowchart

Trace the full process from Blueprint Draft Save through validation, drift detection, and live activation.

Read →

Related Guide

Deployment Troubleshooting Flowchart

Step-by-step remediation for DATA_INTEGRITY_EXCEPTION, HASH_MISMATCH, and CONNECTION_ERROR failures.

Read →

Disclaimer: This guide describes the technical process of deploying a trading bot. Simulation results are based on historical data and do not predict future market conditions or performance. Trading cryptocurrencies involves a high degree of risk, and you may lose substantial amounts of capital. BitThor does not provide personalized financial advice. Consult with a qualified financial advisor before making any investment decisions.