Every processor in the rig
NVIDIA through CUDA, AMD and Intel through OpenCL, Apple Silicon through Metal, and the CPU. Each architecture ships a precompiled kernel, so there is no CUDA toolkit and no OpenCL SDK to install.
v100.13 is out
Release notes →
Mine on everything in the rig.
BzMiner is a high performance cryptocurrency miner and hardware monitor for NVIDIA, AMD, Intel and Apple Silicon GPUs — and the CPU. Seventeen coins across ten algorithms, on Windows, Linux and macOS. One binary, no installer, no toolkit to install.
- ✓ Windows x64
- ✓ Linux x64
- ✓ macOS (Apple Silicon)
17coins
10algorithms
5device types
3platforms
0.5%–2%dev fee
Guides
How to mine, step by step
A guide for every algorithm, each with Windows, Linux, macOS, Hive OS and mmpOS covered, plus the wallet format, working pools, and what to tune. Written to be read top to bottom by someone who has never run a miner.
XELIS
XELxelhash on your GPUs and CPU at the same time. Pool, wallet, and every platform.
Read the guide →Ergo
ERGAutolykos v2, GPU only. Why it needs 2 GB of VRAM and what to do with the rest.
Read the guide →KawPow
RVN · XNA · NEOX · MEWC · CLOREOne algorithm, five chains. Naming the coin is what picks the chain, and the wallet changes with it.
Read the guide →Ethash / Etchash
ETC · ETHWThe same algorithm, two DAG schedules. Get the -a name right or every share is worthless.
Read the guide →Pearl
PRLA zk proof-of-work: every share is a STARK proof. Why the hashrate looks small, and how to mine solo.
Read the guide →RandomX
XMR · ZEPH · SALCPU only. Huge pages, thread counts, and the memory it needs, on every platform.
Read the guide →Verus
VRSCVerusHash 2.2 on the CPU, while your GPUs do something else.
Read the guide →Warthog
WARTjanushash needs a GPU and the CPU together. What the calibration phase means, and how to mine solo.
Read the guide →CryptoNight
CCX · RYOcn/gpu on GPUs and CPU, plus eighteen classic variants for private pools.
Read the guide →MoneroOcean
paid in XMROne pool, one Monero wallet, five algorithms. The password pin that makes it work.
Read the guide →Beyond the first share
Web dashboard & monitoring
Every sensor in the rig in a browser, charts, LAN access, the farm view, and the JSON API.
Overclocking
Power limits, clock offsets and locks, fan curves, per-card settings, and what to reach for per algorithm.
Console & hotkeys
The four screens, what every column means, the hotkeys, and the commands behind the c key.
Devices & multi-algo
Pick cards by number or PCI address, decide how much CPU mines, run two coins at once, and say which algorithm gets which device.
Pools & farms
Backup pools that switch back on their own, mining through SOCKS5, and one pool connection for a whole farm.
Hive OS & mmpOS
Installing the current version on a mining OS, what each flight-sheet field becomes, and the force_algo escape hatch.
Benchmarking
A real stratum server inside the miner, so a measured share is an accepted one.
The dev fee
What it costs, when it is paid, where it goes, and how to watch a whole cycle in a minute.
Troubleshooting
No GPUs found, rejected shares, a card that never mines, a dashboard that will not open.
Features
Built for rigs that run for months
Everything below is in the binary you download. There is no paid tier, no account, and nothing phones home.
One binary, no installer
Unpack it and run it. It writes nothing outside its own folder except the log file and the config you point it at. A launcher script per algorithm and a fully commented config.txt come in the archive.
Web dashboard
Served at 127.0.0.1:4014. Per-device hashrate, shares, pool state and every sensor the hardware publishes, pushed live over a WebSocket. Click any metric to chart it over 10m, 1h or 1d.
Four console screens
The dashboard, the scrolling log, the sensor table and a device page that lists every processor in the machine - including the cards that are not mining. The log pane scrolls, and text selection keeps working.
Overclocking, one implementation
Core and memory offsets, clock locks, power limits and fan curves - from the command line, config.txt, the console hotkeys or the dashboard. All four go through the same code, so they cannot disagree.
Safety limits
A card over its temperature or power limit is paused on its own and resumes when it recovers. The offset range the driver reports is enforced, so a large offset stays inside what the card actually allows.
Hardware monitor mode
Run with --dmon and bzminer mines nothing at all: GPU, CPU, per-DIMM RAM and storage sensors, DRAM timings, PCIe link state and an lstopo-style CPU topology map. A monitor that happens to mine.
Pools, failover and SOCKS5
Backup pools with automatic failover, and a failed primary is re-probed and switched back to without a gap. Every pool connection can be routed through a SOCKS5 proxy. Solo mining against your own node for Pearl and Warthog.
Several algorithms at once
Point different cards at different chains on the same rig, per device number or PCI id. Per-card intensity, per-card overclocks, and per-card pools.
Real benchmarking
A stratum server inside the miner, so a measured share is an accepted one rather than an estimate. Mine and benchmark with no pool at all.
Plugin architecture
Algorithms, hardware monitors, console front-ends and the dashboard are all plugins behind one stable C ABI. The full build compiles them in; the lite build loads them from a folder, so a single plugin can be replaced without a new miner.
Signed and verified
The released binary is signed and verifies itself at startup, GPU runtimes load only from trusted system paths, and every archive publishes a SHA-256 beside it.
Algorithms
Every algorithm, and exactly what it costs
Each algorithm declares its own dev fee. It is printed in the log at startup
and listed here straight from the shipped binary — run
bzminer --list-algos on your own copy to check it against this table.
NVIDIA
AMD
Intel
Apple
CPU
| Coin | -a name |
Dev fee | Runs on | What it is |
|---|---|---|---|---|
| Ergo ERG How to mine → |
ergo
|
1% | NVIDIA AMD Intel Apple | A smart-contract proof-of-work chain built on an extended UTXO model. Autolykos v2 is memory-hard: it builds a ~2 GB table in VRAM before it can mine, so a card needs the room for it. |
| Ravencoin RVN How to mine → |
rvn
or kawpow
|
1% | NVIDIA AMD Intel Apple | A Bitcoin-derived chain for issuing and transferring user-created assets. |
| Neurai XNA How to mine → |
xna
or kawpow
|
1% | NVIDIA AMD Intel Apple | A Ravencoin fork aimed at tying asset tokens to IoT devices and AI data. |
| Neoxa NEOX How to mine → |
neoxa
or kawpow
|
1% | NVIDIA AMD Intel Apple | A Ravencoin fork built around gaming and in-game reward tokens. |
| Meowcoin MEWC How to mine → |
meowcoin
or kawpow
|
1% | NVIDIA AMD Intel Apple | A community-run Ravencoin fork with the same asset layer. |
| Clore CLORE How to mine → |
clore
or kawpow
|
1% | NVIDIA AMD Intel Apple | A Ravencoin fork whose coin pays for time on a GPU-rental marketplace. |
| Ethereum Classic ETC How to mine → |
etchash
or etc
|
0.5% | NVIDIA AMD Apple | The original Ethereum chain, still proof-of-work. ECIP-1099 halved its epoch, so its DAG is about half EthereumPoW's at a comparable height and fits cards ETHW no longer does. |
| EthereumPoW ETHW How to mine → |
ethash
or ethw, ethereumpow
|
0.5% | NVIDIA AMD Apple | The proof-of-work fork kept alive after Ethereum moved to proof-of-stake. The -a name picks the DAG schedule, so it is not interchangeable with etchash. |
| Conceal CCX How to mine → |
cn/gpu
or cn
|
1% | NVIDIA AMD Intel Apple CPU | A privacy chain with on-chain deposits and interest, on CryptoNight-GPU since its 2021 fork. -a cn lets an auto-switching pool pick the CryptoNight variant; naming one mines that variant. |
| Ryo RYO How to mine → |
cn/gpu
or cn
|
1% | NVIDIA AMD Intel Apple CPU | The chain CryptoNight-GPU was written for; mined here through MoneroOcean, which pays in XMR. |
| Pearl PRL solo capable How to mine → |
pearl
|
1% | NVIDIA AMD Intel Apple CPU | A zk proof-of-work chain: every share is a STARK proof, so it is far heavier per hash than an ordinary algorithm and the hashrate numbers look small. |
| Monero, Zephyr, Salvium XMR · ZEPH · SAL How to mine → |
randomx
or rx/0, xmr, monero, zeph, zephyr, sal, salvium
|
1% | CPU | Monero is a privacy chain that hides sender, receiver and amount by default. RandomX (rx/0) is deliberately CPU-friendly and ASIC-hostile, and Zephyr and Salvium run the same algorithm. |
| VERUS VRSC How to mine → |
verus
|
1% | CPU | A hybrid proof-of-work / proof-of-stake chain with an identity and currency protocol on top. VerusHash v2.2 is CPU-only by design. |
| Warthog WART solo capable How to mine → |
warthog
|
2% | NVIDIA AMD Intel Apple CPU | Its janushash proof-of-work is deliberately split across both processors: the GPU filters sha256t and the CPU runs VerusHash over the same nonces. Neither half finds anything alone. |
| XELIS XEL solo capable How to mine → |
xelis
|
1% | NVIDIA AMD Intel CPU | A privacy-oriented BlockDAG with encrypted balances and homomorphic transfers. Mines on the GPUs and the CPU at once. |
| SDK example |
sha256d
|
none | NVIDIA AMD Intel CPU | The open-source SDK example: a complete algorithm plugin - CPU and GPU kernels, pool stratum, bench job source. Not worth mining; SHA-256d is ASIC territory. |
Warthog needs both a GPU and the CPU. Neither half finds anything alone, so disabling either one stops the rig. Every other algorithm mines on whichever of its listed device types are present.
The five KawPow coins share one algorithm, and the name you give -a
is what picks the chain. Each coin has its own address format, so the
wallet changes with the name. The same goes for Ethash: etchash and
ethash build different DAGs, so the name must match the pool.
“Intel” means an Arc or integrated GPU through OpenCL;
“Apple” means an Apple Silicon GPU through Metal on macOS. Six
algorithms have a Metal path — ergo, kawpow,
ethash, pearl, warthog and cn —
and those are the ones that use the GPU on a Mac.
Monitoring
A hardware monitor that happens to mine
The web dashboard is served straight from the miner at
http://127.0.0.1:4014 — the same data the console shows, pushed
live over a WebSocket. Per-device hashrate and shares, pool state, and every
sensor the hardware publishes.
- Core, hotspot and memory temperatures, fan RPM, rail power, current and voltage
- Clocks against their rated values, PCIe gen × width, link errors and TX/RX
- Per-DIMM RAM cards with DRAM timings, an lstopo-style CPU topology map, and storage
- Click any metric to chart it over 10m, 1h or 1d — histories collect even while hidden
- Overclock controls that go through the same code as the console and command line
Run bzminer --dmon and it mines nothing at all: just the monitor,
with the dashboard forced on.
JSON, for your own dashboard
/api/snapshot- Everything: devices, pools, hashrate, shares
/api/stream- The same, pushed as it changes (WebSocket)
/api/gpus- Per-GPU detail and every vendor sensor
/api/metrics- Metric histories for charting
/api/topology- CPU topology map
/api/oc- Read and apply overclocks
/status- The shape other mining dashboards expect
/hive_status- HiveOS
The dashboard binds to localhost and has no password. Set
http_address=0.0.0.0 only behind something you trust.
Get started
Mining in about a minute
-
Download and unpack
One archive per platform. Take the one for your OS from the release page and check the SHA-256 published beside it.
-
Put your wallet in a start script
There is a
start_<algo>script per algorithm in the archive. Open the one you want and replace the placeholder wallet — or pass it on the command line../bzminer -a xelis \ -p stratum+ssl://xelis.herominers.com:1187 \ -w xel:your_wallet_here \ --worker rig1 -
Open the dashboard
The miner serves its own dashboard while it runs. Nothing to install, nothing to sign in to.
http://127.0.0.1:4014/readme.txtinside the archive has the full quick start.config.txtis a commented copy of every setting, generated from the shipped binary, so it always matches the build you have. For the long version, with your platform and your coin, there is a guide per algorithm.
Dev fee
Stated up front, and visible while it runs
Each algorithm declares its own fee, it is in the table above, and it is printed
in the log at startup — so you can see it before committing a rig rather than
discover it later. Every line about it is tagged [dev fee].
[dev fee] warthog 2% - announced here, and at START and END of every slice
[dev fee] START - mining for the warthog developer on stratum+ssl://ussw.vipor.net:5120 (2.00%)
[dev fee] END - back to your pool stratum+ssl://us.vipor.net:5120 (paid 1.94% of this run so far)Paid as a time debt
Not on a fixed clock. The first slice lands about five minutes into a run and the next an hour later, and the running total is what the schedule aims at.
Split across destinations
The fee is spread over several pools rather than sent to one, so no single pool sees all of it. A destination that will not connect is backed off, dropped, and the others carry its share.
It costs your mining nothing
None of it happens on the thread that reads your pool’s jobs, so an unreachable dev pool costs you no stale job and no reconnect.
Watch a whole cycle
--test-dev-fee 30 runs the switch, the dev pool’s subscribe, the switch back and your own work resuming inside a minute.
Community
Where to find us
Questions, bug reports and feature requests are all welcome. The Discord and Telegram are where most of the day-to-day help happens.
Download BzMiner v100.13
Free, no installer, and every archive publishes a SHA-256 beside it.