FAQ and troubleshooting

If the answer is not here, ask in Telegram or open an issue on GitHub.

The dev fee

0.75 % of the work your GPUs compute goes to the developer on each coin. Not 0.75 % of time or of accepted shares: of computed work. One small dev package runs at start, then a new one whenever the dev share would fall below 0.75 %, about one dev package per 132 of yours. The console's DEV line shows the realised percentage. Switching between your job and the dev job is designed to add no measurable loss.

Why the pool shows less than the compute rate

The top bar shows what your cards compute; the pool pays for accepted shares. Over time the pool number is a few percent lower, over short periods far lower or higher:

Compare with the miner's own pool column, which is computed the way a pool computes it.

Automatic pool failover

On by default. If your pool refuses connections, sends no work, drops sessions or rejects many shares, the miner moves to the best working pool: your own backup pools first (in your order), then the built-in approved pools that pay the same address with the same worker. It returns when your pool recovers, without flapping. It rides through DNS blocks and resets, and can use your own SOCKS5 proxy: --proxy socks5://HOST:PORT. Turn it off with --no-pool-failover; see the ranking with --pool-failover-report.

Troubleshooting

SymptomWhat to do
no GPU found: ...The line names the cause: no NVIDIA driver, a driver older than R575+ (CUDA 12.9), a card not passed to a container, or no AMD runtime. --list prints the same line.
pool and wallet disagreePass --algo pearl or --algo qtc.
TLS to the pool failsTry the address without tls://; some pools use a self-signed certificate.
dev fee: no approved dev pool can be reachedCheck firewall, DNS, VPN / proxy, the hosts file and ad-block lists for pool domains. Mining resumes by itself.
not applied (no permission (admin/root needed))Run the miner as administrator / root, or use --mem-control none.
Red line: Run as ADMIN for Profit Mode and TuningThe miner mines normally, but the power-limit search does nothing. Start it elevated.
mining paused on this cardThe card is above --panic-temp. Improve cooling; it resumes 5 C below.
Rejected shares "invalid" / "low difficulty"The card computes wrong: lower or remove your overclock. Usual sign of an unstable core or memory overclock; the miner never changes your core clock or voltage.
Many stale sharesHigh latency or a far pool region. Choose a closer endpoint.
First share takes longThe first dev package is mined before your work; then tuning. On slow cards that can take tens of seconds.
Output freezes on WindowsText selection in the console pauses output. Press Esc.
Exit code 2 with a card already in useRun exactly one miner per card.
Coin switching paused / power search offThe public price sources cannot be reached from your network. Mining goes on.

Good to know

Reporting a problem

Open an issue on GitHub and include: the output of armadig-miner --version; the --list output or the first 30 lines of a run; one console table with the DEV line and the bottom bar; the log (--log armadig.log) if the run lasted more than a few minutes; card model, coin, pool, driver version and operating system. Do not send wallets or pool logins. They are not needed.

License

Armadig is closed-source freeware: free use on your own hardware, including commercial mining. The dev fee is part of the terms and must not be removed, bypassed or redirected. No reverse engineering, modification or resale; only the complete unmodified official archive may be redistributed; no warranty.