FAQ
Questions and answers
Short answers about hardware, data, the licence and Telegram. Didn't find yours? Write to support.
The system
WhatsMiner (MicroBT); Antminer (Bitmain) on stock firmware, Vnish, AML and Pitbit; Avalon (Canaan); Elphapex DG1, DG1+ and DG Home. SHA256 and Scrypt are counted separately, each in its own units.
Need another model or firmware? We'll add it on request.
The licence doesn't limit the number of devices. The system is built for farms with thousands of machines: subnets are scanned in parallel, polling runs at two rates — a fast one every 45 seconds and a detailed one every 5 minutes — and a bulk operation covers up to 500 machines at once.
Yes — one machine at a time or hundreds at once, up to 500 per operation, with a confirmation, a Cancel button and the result for every machine. Pool change, reboot and LED locate work on every supported family. The rest depends on the vendor and firmware: WhatsMiner also has power on and off, power mode, power limit and frequency; Antminer with Vnish — stopping and starting mining and a power limit; Avalon — power on and off and power mode; Elphapex — power on and off. The miners' admin password is entered once in the settings and stored encrypted.
Missing a command for your model? We'll add it on request.
Several safeguards prevent that. A machine switched off by an operator is a status, not an incident. A hashrate drop is measured against the machine's own norm, not its nameplate. Thresholds can be set for the whole fleet, a vendor, a group or a single machine — WhatsMiner, for example, has its own temperature threshold. Rules stay silent on stale data: a machine that has gone quiet is reported by the Not responding alert. On top of that there are scheduled quiet hours and muting by individual error codes.
The bot writes to the shift's group chat and in private messages to people who have linked their account, with separate severity thresholds. Every recipient picks their own language with /lang. Messages are batched, a summary arrives on a schedule (every 12 hours by default), and an incident message has an acknowledge button — once pressed, the message shows who took it.
Turn on the built-in proxy. The system supports VLESS, Trojan and WireGuard: paste the connection link (vless://, trojan:// or a .conf file) into the notification settings, and the bot's messages will go through the server you specified. Only Telegram traffic goes through the proxy — miner polling stays in the local network and the licence check goes directly. The proxy comes with the Linux build; on Windows, notifications go to Telegram directly.
Four: English, Russian, Chinese and Thai. Every user picks the interface language, and every Telegram recipient picks the language of their messages. Error code descriptions are available in all four languages too.
Installation and data
Linux with systemd (amd64 or arm64) and Windows 10 or 11, 64-bit. A regular server or computer in the same network as the miners will do: the system is a single program file with a built-in database, no Docker needed.
On Linux the installer sets it up as a service with one command; on Windows it runs from the unpacked folder while its window stays open.
For the licence — only key activation and a daily check, over HTTPS to hash-hut.net or hash-hut.ru. Through the same server the system checks for a new version every 6 hours (this check can be turned off) and builds the Hash-Hut pool chart. If the connection drops, the system keeps working: a licence confirmation is valid for 14 days plus another 30 days on top, and only after that does the system go read-only until the connection is back. Notifications need access to Telegram, directly or through the proxy.
For a farm with no internet at all we issue an offline key — write to support.
On your server, in the built-in SQLite database. There is no cloud: the interface runs in your network, and we have no access to it. History is kept for a year: detailed points for 7 days, 5-minute points for 30 days, hourly points for a year.
For the licence check the system sends the key itself, an installation ID, a hash of the server fingerprint, the program version, the number of devices and the server time. For the Hash-Hut pool chart it sends the login and worker name of the machines on our pool.
There are three roles. A viewer sees the table, charts, history and alerts; an operator can also control individual machines; an administrator runs bulk operations, changes settings and manages users. Any user can be limited to their own groups and subgroups — a technician, for example, sees only their container. Logins, changes and commands go to the audit log with the IP address.
User passwords are stored as argon2id hashes, login attempts are limited, and every state-changing request is protected against CSRF. Miner admin passwords and the Telegram bot token are stored encrypted (AES-256-GCM) with the encryption key in a separate file, and they are never sent back to the browser. There is no admin/admin: the first administrator is created with a one-time token from the server console. On Linux the service runs in a systemd sandbox.
On Linux, with a button in the interface. Every 6 hours the system checks for a new version and shows the release notes to the administrator. Releases are signed, and the signature and checksum are verified again right before installation. An update restarts the service for a few seconds, so it never installs itself — you choose the moment.
On Windows the interface tells you about a new version the same way, and you update by closing the start.cmd window and replacing hashhut-monitor.exe with the file from the new archive.
Licence
Sign in to the cabinet with your Hash-Hut account — the same one you use on the pool site — press “Get the 14-day trial key” and confirm. The key unlocks every feature with no device limit. The 14 days start when the key is issued, so take it once the server is ready. It is one per account and works on one server; a confirmed email is required. Activation goes through the licence server once.
The system warns you in advance, in the interface and in Telegram. After the end of the term it runs read-only for 7 days: monitoring, alerts and notifications keep going, commands and settings are locked. Then the system asks for a key and Telegram notifications pause, while polling and history recording continue. Your data doesn't go anywhere: renew for free on the Hash-Hut pool or buy a full licence, and everything comes back with its history.
Yes: the licence renews itself while your farm mines with us. The conditions: the devices have hash-hut.net or one of its subdomains as their first pool, and together these machines make at least 5 PH/s on SHA256 or 250 GH/s on Scrypt. The check runs every hour; each successful check moves the end date to 7 days from that check, so a short downtime at the farm doesn't close the licence. You need an activated key — the trial key will do — and a regular connection to the licence server. The License tab shows how much is missing to reach the threshold.
Write to support in Telegram — we'll tell you the price and how to pay. A full licence has no device limit, includes every feature and update, and works with any pool. Paying from your Hash-Hut pool BTC balance is coming soon.
Yes. The system already has everything a farm needs day to day, and if something is missing — a new model, a firmware, a report or an integration — we'll add it on request. Write to support in Telegram what you need and on which hardware.
Still have questions?
Ask us in Telegram
We'll help you choose a licence, install the system and connect your hardware. And you can start right away with a trial key from the cabinet.