Security
A straight answer to a fair question: “what does this mean for my farm and my money?”
What OCBot never asks for
| Item | The truth |
|---|---|
| Seed phrase / wallet keys | Never requested — OCBot does not connect to wallets and cannot move funds. There is simply nothing for it there. |
| HiveOS / phone / bank passwords | Not requested. The bot stores only its local config file and the Telegram bot token that you personally create. |
| Saved cards / auto-payments | Payments are manual only, USDT (BEP20) to the address you see on the Buy page. No payment profiles, no recurring billing. |
| Hidden miners | The reverse: OCBot does not mine at all. It only tunes the overclock of the miner you installed yourself in HiveOS. |
What it actually does
OCBot lives on your farm (in your HiveOS) and talks only to you through your own Telegram bot:
- finds and locks per-card overclock presets (core / mem / Power Limit within your PSU limits), verifies stability before saving, keeps a profile per card;
- watches for degradation: temperatures, dead cards, hashrate drops; helps recover after faults;
- reports: what changed, what was saved, what needs your attention.
Payments go to the wallet address shown on the Buy page; the license key is issued by the same sales worker at the moment of payment.
VirusTotal scan
Verifiability
The buyer build is obfuscated (no comments or docstrings) and protected by a per-rig license key — the bot's sources are not published. Before installing you can verify the build with the distribution's verify_protected.py against the public build archive: ocbot-dist. Questions: Telegram support bot — answered by a human (us), no middle-bots.
Payments are non-refundable: instead there is a free 3-day trial before buying. Licenses renew manually on the Buy page; no subscriptions, no auto-charges.
Small project: simple terms, manual payment, questions straight to Telegram. Nothing to hide: the build is verifiable, no trackers or hidden charges.