andriu-kun/-wildrig-multi
FinanceA multi-algorithm GPU miner for AMD, NVIDIA and Intel cards, aimed at people mining several coins with existing rigs.
WildRig Multi is a mining binary for mixed-GPU rigs rather than a wallet or pool service. It is worth a look only if you already have compatible hardware, a pool account and a coin whose algorithm appears in its list.
The problem
A miner wants one machine to run several algorithms without tracking down a separate binary per coin. With single-algorithm miners, switching coins often means swapping software, learning different flags and rebuilding monitoring. WildRig changes that by exposing one option set across a long algorithm list, so a rig operator can point the same tool at a different pool or algorithm by changing the -a flag and connection details. The result is a single workflow for benchmarking and running supported coins, with per-GPU intensity and clock controls in the same configuration.
What's different
The distinguishing feature is breadth: the README lists dozens of algorithms from KawPow-family proof-of-work variants through x16r, GhostRider, heavyhash and sha256 variants, and claims support for AMD GCN 2nd gen through RDNA 4, NVIDIA Maxwell through Blackwell, and Intel Arc Alchemist and Battlemage cards. That matters for mixed rigs, where one tool covering all three vendors reduces the number of separate configurations to maintain. GPU settings can be applied per card with comma-separated values, and the tool can lock core and memory clocks, set power limits, cap temperature and run a watchdog that terminates a stuck kernel.
The trade-off is that breadth brings uneven coverage. The README itself flags that nexapow does not work on pre-RDNA AMD cards and that evohash and some similar algorithms produce incorrect shares on NVIDIA Blackwell GPUs. Miners with newer cards should confirm the specific algorithm and card combination before relying on it. There is also a developer fee: most algorithms are listed as zero fee, but several carry 0.75%, 1% or 2% fees, so profitability calculations need to account for that difference.
Who should try it
A good fit is someone with an existing multi-GPU rig who wants to benchmark several supported algorithms or switch coins without changing tooling, especially where cards from different vendors sit in the same machine. A poor fit is someone without supported hardware, anyone mining an algorithm absent from the list, or someone who needs vendor-backed support and a clear compatibility guarantee. The long supported-GPU list is a starting point, not a promise: the note that some cards lack default intensity values means tuning may be required to get useful hashrates. Old GCN 1st-gen cards are explicitly unsupported and the README says that will not change.
Requirements and limitations
You need a supported AMD, NVIDIA or Intel GPU, a pool endpoint and credentials, and NVIDIA driver 452.39+ on Windows or 450.80.02+ on Linux. The README does not provide a download link, checksum or build instructions in the supplied excerpt, and there is no declared license, only an as-is warranty disclaimer. For an operator, that means the source of the binary and its integrity are questions to settle before running it on a mining rig.
Day-to-day use involves more than launching it: pool URL, user and password, protocol choice, retry behavior and temperature limits all need to be set, and the watchdog or a custom script can be configured to react to a stalled card. GPU clock, power and fan controls are also available, but the README does not document safe values or a tuning method. Check the pool's supported protocol and difficulty settings against the available protocol and difficulty flags.
HotRepo's take
The repository was observed once, on the 2026-10-26 NEW-REPOSITORY board, at #23 with 363 total stars; that is a new-project ranking, not a daily growth measurement, and HotRepo has no comparable daily history for it. With one snapshot, persistence cannot be judged. Before adopting, verify that the exact GPU generation and algorithm pairing you need is not one of the known-issue cases, and establish where the binary comes from.
Written by AI from the project's README, updated October 26, 2026. The project's own docs are the source of truth.