CryptoByPlan

Install CryptoByPlan on Windows

CryptoByPlan logoCryptoByPlanBITVAVO TRADING CO-PILOT

Windows 11 installation

Install the CryptoByPlan bot on a Windows PC you manage. It runs under your Windows account and stores credentials and trading history on that PC.

Release status: The Windows bundle is available to private testers; it is not yet a public release. The public ZIP and checksum will be added here after Windows acceptance testing.

Before you begin

  • Windows 11, 64-bit, with correct automatic time synchronization.
  • Python 3.12.x and the Python Launcher from the official Python for Windows download page.
  • About 2 GB free disk space and a stable internet connection.
  • A dedicated local install folder such as C:/CryptoByPlan. Do not place the running bot under OneDrive, Dropbox, or a network share.
  • Your own Telegram bot and Bitvavo API key with trading enabled and withdrawals disabled. Do not run another CryptoByPlan instance against the same Bitvavo account at the same time; a separate API key does not isolate exchange orders. For independent testing, use a separate Bitvavo account.

1. Download and verify

When the public beta opens, download the Windows ZIP and its matching checksum file from the official CryptoByPlan release page. Keep them in the same folder. Confirm the ZIP’s SHA-256 hash matches the value in the checksum file:

Get-FileHash ./CryptoByPlan-Windows-v3.25.10.zip -Algorithm SHA256
Get-Content ./CryptoByPlan-Windows-v3.25.10.zip.sha256

Continue only when the displayed hashes match. Example filename uses private-tester version v3.25.10; follow the filename and checksum supplied with the package you receive.

2. Extract and run setup

Open PowerShell in your download folder and replace the version in the path below with the exact version shown on the release page:

Expand-Archive ./CryptoByPlan-Windows-v3.25.10.zip -DestinationPath C:/CryptoByPlan
Set-Location C:/CryptoByPlan/CryptoByPlan-Windows-v3.25.10
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
./scripts/setup_windows.ps1

The execution-policy change applies only to that PowerShell window. Setup installs pinned dependencies and creates starter files only when absent. It does not start the bot, create a scheduled task, or place an order.

3. Create your Telegram bot and set credentials

  1. In Telegram, open @BotFather, send /newbot, and follow the prompts.
  2. From the install folder, open .env in Notepad and put the token on the existing TELEGRAM_TOKEN= line. Save it as .env, not .env.txt.
  3. Open the new bot in Telegram and send it /start. In the same PowerShell window, retrieve your numeric chat ID:
$token = (Get-Content .env | Where-Object { $_ -match '^TELEGRAM_TOKEN=' }) -replace '^TELEGRAM_TOKEN=', ''
$updates = Invoke-RestMethod "https://api.telegram.org/bot$token/getUpdates"
$updates.result | ForEach-Object { $_.message.chat.id } | Select-Object -Unique

The command displays the numeric chat.id. Put those digits on the existing TELEGRAM_CHAT_ID= line. Do not share the token or response.

Complete the Bitvavo API key and secret, Telegram token, numeric chat ID, and optional CoinMarketCap key using the exact .env instructions. Use your own Bitvavo key with withdrawals disabled. The optional CMC key adds market context but is not needed to trade.

4. Review and run the first check

Review config.yaml. A clean install starts without a DCA plan or manual Smart orders. Start one foreground instance:

./scripts/run_windows.ps1

In your own Telegram chat, check /start, /help, /status, /balances, /orders, and /funds. Do not create an order or DCA plan during this read-only check. Stop the process with Ctrl+C in PowerShell. Run only one instance per Telegram bot token.

Optional: start when you sign in

After the first check passes, you can register an optional per-user Task Scheduler task. It starts at the next Windows logon, does not run before sign-in, and does not automatically restart after a crash. It is not a Windows service.

./scripts/register_windows_task.ps1 -TaskName CryptoByPlan
Start-ScheduledTask -TaskName CryptoByPlan
Get-ScheduledTask -TaskName CryptoByPlan

Stop the task before a manual run or update:

Stop-ScheduledTask -TaskName CryptoByPlan

Remove it when you no longer want automatic startup:

./scripts/unregister_windows_task.ps1 -TaskName CryptoByPlan

← Back to installation overview

Private-tester guide for package v3.25.10. Public download is pending Windows acceptance testing.