From payment to a running engine, in six steps. The same instructions
ship inside the package as buyer_guide_local.md.
Requirements: Python 3.10+. Windows 10/11 is the fully tested platform.
cd C:\btcMaster python -m venv .venv .venv\Scripts\activate # Linux/macOS: source .venv/bin/activate pip install -r requirements.txt
OKX → API Management → new key. Enable Read and Trade. Leave Withdraw disabled — the engine never needs it and you should never grant it.
copy .env.example .env # Linux/macOS: cp .env.example .env
Fill only your own values: OKX_API_KEY, OKX_SECRET_KEY,
OKX_PASSPHRASE. Safe defaults for everything else are already in the file.
python collect_fp.py
It prints a string like BTCM1-1A2B3C4D5E6F7A8B. This ties the licence to
this machine. Reinstalling the OS or swapping the motherboard changes it.
Open the claim page, enter the email you used at checkout, the claim code from your payment email, and the fingerprint from step 3. We sign a licence bound to that machine and email it back — usually within a minute.
Save the licence file as btcMaster.license in the package root, then:
python local_launcher.py
First run verifies signature, fingerprint and expiry, shows the licence agreement
(type ACCEPT), then checks for revocation online and starts the engine.
Later starts work offline from a cached token. On a headless server, sign the agreement in
writing and run with BTCM_ACCEPT=1.
Logs go to logs/. Start small: the leverage in .env is yours to
set, and the risk governor will not save you from an over-sized first position.
python ui_server.py # Local Pro only → http://127.0.0.1:8765
The cockpit binds to localhost only. Parameter changes follow a draft → promote flow and most take effect only after a restart — that is deliberate.
| Message | Meaning | Fix |
|---|---|---|
| No licence file found | btcMaster.license missing from the root | Put the emailed file next to local_launcher.py |
| Fingerprint mismatch | Licence bound to another machine | Request a re-issue with the new fingerprint |
| Invalid signature | File edited or forged | Re-download the licence from your email |
| Licence revoked | Refund, dispute, or terms breach | Contact support |
| Engine exits immediately | Bad API key or no network | Check logs/master.log |
| Download link expired | Links last 72 hours | Reply to your order email for a fresh link |
Email product@yrmt.top from the address you bought with. Re-issues, new-machine swaps and delivery problems are usually handled the same day.