BOVOBot Community Edition

Desktop control. Secure mobile access.

Run the protected public bot locally on Windows with Standard Futures only. Lead Trade, account binding, broker attribution, API keys, secrets and passphrases are not included. The signed Android app supports encrypted QR transfer and mobile monitoring.

Community Edition Standard Futures only Windows 0.1.0.38 Android 1.6.1 SHA-256 verified Outside EU/EEA only No automatic trading start

Decentralized community distribution

Two local applications, one documented trust chain.

Bovotrade does not custody funds, connect an exchange account through this website, or collect exchange credentials. Every release is delivered with a published file size and SHA-256 hash.

Desktop: Windows x64 · BOVOBot 0.1.0.38
Mobile: Android · BOVOBot 1.6.1
Delivery: Signed packages with hash verification

Current public release

Windows bot and Android companion app.

The desktop package performs the local Standard Futures workflow. Lead Trade and account authorization are technically absent from this public build. The mobile package is a separate companion application and does not replace the desktop bot.

Windows x64

Community Edition

BOVOBot 0.1.0.38

A protected single-executable desktop release with Standard Futures only. Lead Trade, account binding and broker attribution are not included. Users add their own Standard API key, secret and passphrase locally.

File: BOVOBot_Community_Edition_0.1.0.38_win-x64.zip
Size: 64.3 MB
Standard route: Available after local setup
Lead Trade: Not included
Getting Started: Manual after local setup

Android

Signed companion app

BOVOBot Mobile 1.6.1

A release-signed companion app for encrypted QR credential transfer and mobile monitoring. It validates its package identity and signer before opening.

File: BOVOBot_Mobile_1.6.1_Android.apk
Size: 35.6 MB
Package: com.bovobot.monitor.customer
Minimum: Android 6.0 (API 23)

Mobile release protection

Hardened against extraction and tampering.

Release obfuscation, full AOT compilation and post-AOT IL stripping
Android Keystore-backed secrets and AES-256-GCM encrypted local cache
Runtime package, version, release-mode integrity and signer verification
Screenshot blocking, no cleartext transport and no Android backup export

These controls materially increase resistance to reverse engineering and manipulation. No client application can be guaranteed to be impossible to analyze or attack, especially on a compromised or rooted device.

New hedge system

Profit-Locked Hedge Release explained.

Initial LONG and Initial SHORT are separate margin inputs; every hedge opens from the configured initial margin of its own side.
As soon as a valid LONG trailing stop is accepted and synchronized while the paired SHORT is open, the bot must attempt to close the complete SHORT even when its PnL is negative.
SHORT Step Recompounding is symmetric with LONG: after SHORT reaches its own Minimum Profit and the matching SHORT trailing stop is accepted, each confirmed boost anchors the next full favorable SHORT profit step.
A fresh full order book supplies spread, VWAP, worst ask and depth gap for the complete SHORT quantity.
Fees, funding, accrued costs, slippage and Minimum Profit % are calculated and logged. If the profit-safe boundary is not met, the bullish risk override still requires a complete reduce-only FOK close attempt; partial closes are not allowed.
The LONG boost waits until the SHORT is confirmed absent. Boost fill, target leverage and the re-armed trailing order for the complete LONG quantity must then be confirmed before the next boost step.

A technical FOK rejection, incomplete order-book depth or delayed exchange synchronization can postpone the close; the bot retries from fresh state. If the LONG trailing order fills first, the confirmed LONG exit continues to drive the remaining SHORT close. Separate positions cannot be closed atomically, so fills, profit and liquidation protection cannot be guaranteed. Verify positions and protection orders directly at KuCoin.

Futures, leverage and automated orders can cause substantial or total loss.

The included example values explain configuration behavior and are not a recommendation or promise of performance.

First installation only

Documented desktop defaults.

Existing local databases and saved settings are not overwritten by these defaults.

Setting	Default	Purpose
Market allowlist	BTC	Only BTC is enabled on a new installation.
Initial order	20 USDT	Base margin input for the first order.
Leverage	20x	High-risk leverage, limited by the exchange maximum.
DCA / Safe	x1 / x1	Uses the unchanged base multiplier for additional orders.
Trailing / retracement	0.50% / 0.10%	Activation distance and permitted pullback for the configured exit logic.
Leverage boost	Active from 0.52%	Adds 5x up to 25x, still capped by the exchange.

Installation

Verify first, configure locally, then start deliberately.

01
Download the correct package
Use the ZIP for Windows or the signed APK for Android.
02
Compare SHA-256
Do not open a package when its calculated hash differs from the value below.
03
Limit exchange permissions
Use a dedicated Futures key without withdrawal permission. Never send credentials through email or community chat.
04
Transfer only through the encrypted QR flow
Keep both devices under your control and delete an exported transfer QR after use.
05
Start trading only on the desktop
Review markets, capital, leverage and open positions before manually pressing Start.

Integrity and download

Verify the package you install.

The server verifies each file against its release manifest again before sending it.

Windows ZIP

BOVOBot Community Edition 0.1.0.38

5076523c8064ea299756ff859bae75b706a1416c8fe9cc24e56c315c08d5baf9

Get-FileHash .\BOVOBot_Community_Edition_0.1.0.38_win-x64.zip -Algorithm SHA256

Android APK

BOVOBot Mobile 1.6.1

df60b6a689928ccc267c717b3734f5e39f8e2e556c5c9aa8e676280c0b3825a9

Compare this value with a trusted SHA-256 utility before installing the APK.

Understand every setting

The detailed guide explains directional initial margin, side leverage, DCA, Safe Orders, the Profit-Locked Hedge Release, API permissions and the first controlled start.

Open settings and hedge guide