BzMiner v100.10

Release v100.10 of bzminer

All feedback is welcome ;)

• New Coin: Pearl (1% dev fee, Nvidia, AMD, Intel, CPU, Solo mining)
• New Coin: RandomX (1% dev fee, CPU only)
• Improved hashrate on Xelis and Warthog
• Added Socks5 support
• First official release of entirely rewritten BzMiner
• TUI mode (default)
• Monitoring mode (many metrics available)
• Hotkeys to adjust overclocks while mining
• Many more features

NOTE: Because this is an entire new rewrite of BzMiner, many algos bzminer previously supported have been dropped (some temporarily). If you were mining any algos that are no longer supported in bz, please keep using your current version of bz and request that algo get added to a future update of bzminer

---

Downloads

file	size	SHA-256
bzminer_v100.10_windows.zip	14.4 MB	45ac10991b948e418a01fca0e3f04e2e14294b1f851cd78e119322ead1352d91
bzminer_v100.10_linux.tar.gz	15.3 MB	169aa1ffed337d99453e22d4d97faac661172335aaa1528469469ebd832adc0b
bzminer_v100.10_macos.tar.gz	15.9 MB	cebdf981f9033cbecbf4b9a52384c315b0c7a91fd8755c223a0e6475a602b187

Verify before running:

# Linux / macOS
sha256sum -c <<< "<hash>  <file>"

# Windows (PowerShell)
Get-FileHash .\<file> -Algorithm SHA256

A checksum only proves the file is the one that was published — always download from the official release page.

Getting started

1. Unpack the archive for your platform.
2. Open a start_<algo> script and replace the placeholder wallet with your own.
3. Run it, then open http://127.0.0.1:4014/ for the dashboard.

readme.txt inside each archive has the full quick start, the common options, and the hardware-safety settings. config.txt is a commented copy of every setting, generated from the shipped binary, so it always matches the build you have.

Updating on a mining OS

Both fetch this exact version, so they can be pasted as-is - the version below is already the one on this page.

MMPOS

Put this in miner profile → advanced → "Initiate command prior to miner launch". It downloads once; on every later launch the if sees the archive already in /tmp and exits immediately, so it costs nothing per restart.

export version="v100.10"
if [ -f "/tmp/bzminer_${version}_linux.tar.gz" ]; then
exit 0
else
cd /tmp; wget https://github.com/bzminer/bzminer/releases/download/${version}/bzminer_${version}_linux.tar.gz; tar -xvf bzminer_${version}_linux.tar.gz; sudo cp -adpR bzminer_${version}_linux/bzminer /opt/mmp/miners/bzminer/
fi

Hive OS

Run it over SSH or in the Hive web shell.

You do not need to know which bzminer version is installed. Hive keeps one folder per version under /hive/miners/bzminer/, and the flight sheet decides which one runs - so this replaces the binary in every bzminer folder it finds and whichever one your flight sheet points at gets the new build. That is the whole reason it does not name a version directory.

version=v100.10
cd /tmp && wget -q https://github.com/bzminer/bzminer/releases/download/${version}/bzminer_${version}_linux.tar.gz && tar -xf bzminer_${version}_linux.tar.gz || { echo "download failed"; exit 1; }
miner stop
n=0; for d in /hive/miners/bzminer/*/; do [ -d "$d" ] && cp -f "bzminer_${version}_linux/bzminer" "$d" && n=$((n+1)); done
[ "$n" -gt 0 ] && echo "updated $n bzminer folder(s)" || echo "no /hive/miners/bzminer/<version>/ found - install bzminer from the flight sheet first"
miner start

It prints how many folders it updated. 0 means bzminer has never been installed from a flight sheet on that rig, so there is nothing to replace yet.

Algorithms in this build

-a name	coin	dev fee	devices	what it is
ergo	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. Wallet addresses start with '9'.
etchash, etc	Ethereum Classic	0.50%	NVIDIA · AMD · Apple	The original Ethereum chain, still proof-of-work; ECIP-1099 halved its epoch, so its DAG is about half ETHW's at a comparable height.
ethash, ethw, ethereumpow	EthereumPoW	0.50%	NVIDIA · AMD · Apple	The proof-of-work fork kept alive after Ethereum moved to proof-of-stake.
rvn (or kawpow)	Ravencoin	1%	NVIDIA · AMD · Intel · Apple	A Bitcoin-derived chain for issuing and transferring user-created assets.
xna (or kawpow)	Neurai	1%	NVIDIA · AMD · Intel · Apple	A Ravencoin fork aimed at tying asset tokens to IoT devices and AI data.
neoxa (or kawpow)	Neoxa	1%	NVIDIA · AMD · Intel · Apple	A Ravencoin fork built around gaming and in-game reward tokens.
meowcoin (or kawpow)	Meowcoin	1%	NVIDIA · AMD · Intel · Apple	A community-run Ravencoin fork with the same asset layer.
clore (or kawpow)	Clore	1%	NVIDIA · AMD · Intel · Apple	A Ravencoin fork whose coin pays for time on a GPU-rental marketplace.
pearl	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. Also mines solo against your own node. Wallet addresses start with 'prl1'.
randomx, rx/0, xmr, monero	Monero	1%	CPU	A privacy chain that hides sender, receiver and amount by default. RandomX (rx/0) is deliberately CPU-friendly and ASIC-hostile. A Monero address. The worker name is a separate --worker argument, not a suffix on the address.
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.
verus	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. A Verus R-address. The worker name is a separate --worker argument, not a suffix on the address.
warthog	Warthog	2%	NVIDIA · AMD · Intel · Apple and CPU	A chain whose 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. Wallet addresses are 48 hex characters.
xelis	XELIS	1%	NVIDIA · AMD · Intel · CPU	A privacy-oriented BlockDAG with encrypted balances and homomorphic transfers. Wallet addresses start with 'xel:'.

Reporting problems

Please include: your OS, GPU model(s) and driver version, the algorithm and pool, and the first ~40 lines of the log (it prints the build, the devices it found, and what each backend reported). --list-metrics output helps for sensor issues.