A guide to installing the published CROT bot on your own computer. You do not need to install it to subscribe to RS Rotation copy trading.

Source: README at revision 8e061bec845c. Checked on 12 September 2026. The commands below refer to this revision.

  1. 1
    Get the code
  2. 2
    Install dependencies
  3. 3
    Check without the exchange
  4. 4
    Configure and verify the account

1. Preparation and source code

You need Git, a terminal and a compatible Python version. Check the Python requirement in pyproject.toml at the selected revision. Use a new folder separate from any running bot; installation and offline tests do not need exchange keys.

git clone https://github.com/Lermont/Crot-Pro.git CROT-setup
cd CROT-setup
git checkout 8e061bec845c0ea18ee14c9e28b6c6cbab2dc9cb

pyproject.toml · build.sh

2. Windows: installation and tests

In PowerShell, call the virtual environment Python directly; activation is not required. Installation and check commands follow the README.

python -m venv .venv
.\.venv\Scripts\python -m pip install --upgrade pip
.\.venv\Scripts\python -m pip install -e ".[dev]"

$env:HTXBOT_DISABLE_DOTENV = "1"
.\.venv\Scripts\python -m compileall .
.\.venv\Scripts\python scripts/check_imports.py
.\.venv\Scripts\python -m pytest -q
Remove-Item Env:HTXBOT_DISABLE_DOTENV

HTXBOT_DISABLE_DOTENV prevents the checks from reading a local .env. Tests use exchange stubs. Success checks the installation; it does not establish profitability or readiness to trade.

3. Linux and macOS: setup script

Read build.sh at the selected revision, then run it from the project directory:

bash build.sh

According to the README, the script installs system dependencies including TA-Lib and build tools, creates the environment and runs conformance tests. It asks before installing system packages. Keep tests enabled on your first installation.

4. Configuration and the launch boundary

After offline checks, review .env.example. Create .env only where HTX access is needed; do not overwrite existing keys. The template contains DRY_RUN=true: in this revision it prevents live-client creation, rather than providing a trading simulator.

STRATEGY selects the strategy; trading and risk settings live in strategies/<STRATEGY>/settings.py. Before live launch, verify key permissions, account mode, leverage, symbol routing and existing positions and orders. Follow the selected revision README, not another account’s example settings.

Common errors

SymptomWhat to check
Python / Git not foundCheck installation and PATH; open a fresh terminal after installation.
ModuleNotFoundErrorConfirm you use .venv Python and pip install finished successfully.
TA-Lib / compilerCheck native dependencies and Python compatibility in your revision’s build.sh and README; do not suppress the failure.
DRY_RUN=trueLive-client refusal is expected. Complete README account checks first.
Tests failKeep the error and revision ID. File an issue without .env or secrets; do not proceed to trading.

Next steps

Choosing an open-source bot · Risk management · Authorship and sources

Author: Sergei Mushtuk · · Report an error