Pool failover
Pool addresses get blocked, sometimes in the middle of a run. Armadig notices and moves to a working pool on its own, with no restart. It is on by default.
What triggers a switch
- Your pool refuses or resets the connection (3 attempts in a row), times out (2 in a row), cannot be resolved by DNS, fails the TLS handshake or refuses your login.
- The session drops 4 times within 10 minutes.
- The pool sends no work: no first job within 30 seconds of the login, or no new job for 5 minutes.
- The pool rejects or marks stale more than 20 % of the last 30 answered shares (at least 10).
Where it goes
- Your choice. The pool you typed, or the location the miner picked at start. Backup pools you list with repeated
--poolare tried in your order. - Another location of the same pool operator, if the built-in list has one. The same login works there.
- Other approved pools, fastest first. These are used only when your login is a plain payout address, so every pool pays the same address.
Pools that have been crediting your shares properly rank first at every step, then the order above, then lower latency. A pool that failed rests for at least 10 minutes (20, 40, ... up to 4 hours if it keeps failing).
No flapping
A healthy pool is never left for a slightly faster one. The miner returns to your first pool only after two healthy probes, after at least 10 minutes on the backup, and at most 3 times an hour.
What you see
pool failover: pool.example:3333 -> approved pool #1 (connection failures (refused))
One line per switch, and pool=ok or pool=switched(N) on the 5-minute status line. Approved pools are shown by number, never by address.
Blocked networks
When a provider blocks pool names or addresses (DNS failures, wrong DNS answers, connection resets, broken TLS handshakes, silent drops), the miner moves on by itself. With --proxy socks5://HOST:PORT every pool connection goes through your SOCKS5 proxy and the proxy resolves the pool name. The miner uses no other circumvention.
Examples
# your own backup pools, in your order
armadig-miner.exe mine --algo qtc --pool POOL_A:PORT --pool POOL_B:PORT --wallet YOUR_QTC_WALLET
# any Kryptex location, the fastest first
armadig-miner.exe YOUR_PEARL_WALLET YOUR_QTC_WALLET --pool kryptex
# through your own SOCKS5 proxy
armadig-miner.exe YOUR_PEARL_WALLET YOUR_QTC_WALLET --proxy socks5://HOST:PORT
# print the pool ranking once
armadig-miner.exe YOUR_PEARL_WALLET YOUR_QTC_WALLET --pool-failover-report
# turn failover off
armadig-miner.exe YOUR_PEARL_WALLET YOUR_QTC_WALLET --no-pool-failover
In armadig.conf the rules can be tuned in one line: failover = switch pool-only, 20%, 300s (what to do on a pool failure, the rejected + stale limit, QTC seconds without a job).
The dev fee follows the same idea: it is mined only on approved pools and the miner tries every one of them in turn. See the fee.