3.0.7

CryptoBot Pro 3.0.7

Licence

• The app re-checks the licence 30 seconds after start-up and every 24 hours while it stays open, not only when you open the License page.
• When the licence server reports that no subscription is active any more, the licence becomes expired: the navigation is greyed out, a toast tells you why, and the License page opens once. A later renewal restores it at the next check.
• A network error never revokes a licence. After the paid period ends, the app tolerates 7 days of failed checks, counted from the first failure, before it marks the licence expired.
• The e-mail used for the check is no longer case-sensitive on the server side.
• A running scheduler is never stopped by a licence change.

Quit, keep scheduler running

• The quit dialog and the tray menu offer "Quit, keep scheduler running" while the scheduler is on; the existing button reads "Quit and stop scheduler" in that case. Note: while the scheduler runs, the Windows installer cannot replace the engine file; the built-in updater still stops the scheduler itself.

Hyperliquid

• When Hyperliquid is unreachable at start-up, the engine retries within 20 seconds and then exits with a clear message instead of crashing with a stack trace. Nothing changes when the network is fine.
• With Telegram configured, one message a day warns when the API wallet expires in less than 14 days, or has already expired.

Orders the exchange no longer knows

• A sell cycle whose order the exchange reports as "not found" is no longer deleted. It is kept and marked in its notes with sellId not found YYYY-MM-DD, shown with a marker in Cycles, left out of the restructure and accumulation tools, and unmarked automatically if the order shows again. One Telegram alert per marked cycle (when cycle-error notifications are enabled). A sell placed less than 15 minutes earlier is never marked.

Also

• planner.log and planner_daemon.log are rotated above 10 MB when the scheduler starts.
• Nothing else changes in the engine, the configuration file or the data folders.

Installers
Windows (NSIS, auto-update for 3.0.x Windows clients), Linux (AppImage and .deb, x64) and macOS (Apple Silicon and Intel dmg, unsigned: see the macOS guide for the first launch). Same data folders and configuration as 3.0.0.

3.0.6

CryptoBot Pro 3.0.6

New — Hyperliquid API wallet

• Hyperliquid can now be connected with an API wallet instead of the wallet private key. Create it in the Hyperliquid app (More → API), then in Configuration → Hyperliquid pick the mode "API wallet (recommended)" and paste its private key and your account address.
• An API wallet can place and cancel orders but cannot withdraw to another address. It is valid for up to 180 days.
• Test connection checks that the API wallet is authorized on your account. The bot's logs show its expiry date and warn 14 days ahead.
• The wallet private key still works. An existing configuration is unchanged.

Also

• On Linux and macOS the configuration file, which holds your keys, is now written with owner-only permissions.
• The Hyperliquid client library in the engine is updated.

Installers
Windows (NSIS, auto-update for 3.0.x Windows clients), Linux (AppImage and .deb, x64) and macOS (Apple Silicon and Intel dmg, unsigned: see the macOS guide for the first launch). Same data folders and configuration as 3.0.0.

3.0.4

CryptoBot Pro 3.0.4

Fixed — buying a plan

• The 6-month and 12-month buy buttons work again. Their old checkout links had been deactivated.
• Buy buttons now open the website's /buy/<plan> address, which forwards to Stripe Checkout. A checkout link can now change without a new app version.
• The plan cards no longer say "one-time payment": every plan is a subscription with a 90-day free trial, billed monthly, every 6 months or yearly.
• The plan name shown in the app is right for 6-month and 12-month subscriptions. This one is fixed on the server, so 3.0.3 gets it too.

Installers
Windows (NSIS, auto-update for 3.0.x Windows clients), Linux (AppImage and .deb, x64) and macOS (Apple Silicon and Intel dmg, unsigned: see the macOS guide for the first launch). Same data folders and configuration as 3.0.0.