BzMiner v100.11

Release v100.11 of bzminer

All feedback is welcome ;)

• * New bzproxy mode for farms
• Improved Pearl on Nvidia Blackwell and Ampere
• Improved randomx on zen5 and epyc cpus
• Fixed randomx bugs connecting to other pools
• Fixed xelis solo mining
• webui now has a dashboard for all bzminer instances found on the network (can disable with --disable_udp)
• Added summary row in devices table for total power

* bzproxy allows a single bzminer instance on your network to communicate with the pool, while other instances of bzminer connect to that proxy instance rather than the pools directly

---

Downloads

file	size	SHA-256
bzminer_v100.11_windows.zip	14.6 MB	03b69bacb8d3188c6603e9d2f6c88866f573a0da1ae91b2d257228a41334bee4
bzminer_v100.11_linux.tar.gz	15.4 MB	895a9bc260c5731ea43cdb38eb3506bc3836206a7cf5fe164fe615babb94324a
bzminer_v100.11_macos.tar.gz	16.0 MB	2f525f606a23e63d63488416acb7f1d51a25471084f0756496ebee1d75daab82

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.11"
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 custom miner

The Linux release now includes bzminer_custom-v100.11.tar.gz, a complete Hive OS custom miner: the full bzminer binary, flight-sheet config adapter, log launcher, and native /hive_status reporting.

1. Click Copy on the Flight Sheet JSON below.
2. Open the Hive OS farm page that lists all workers.
3. Open the Flight Sheets tab.
4. Click Import from Clipboard.
5. Create/save the flight sheet and add your PEARL wallet.
6. Apply the flight sheet to the workers.

The sample mines Pearl on HeroMiners. Change url, pool_urls, algo, and coin for another pool or algorithm. The package maps those fields, %WAL%, the Hive worker name, and pass directly to bzminer. Put optional bzminer CLI arguments in user_config.

Flight Sheet JSON

{
  "name": "PEARL_BZMINER_CUSTOM",
  "isFavorite": false,
  "items": [
    {
      "coin": "PEARL",
      "pool_ssl": false,
      "pool_urls": [
        "us.pearl.herominers.com:1200"
      ],
      "dpool_ssl": false,
      "miner": "custom",
      "miner_alt": "bzminer_custom",
      "miner_config": {
        "url": "us.pearl.herominers.com:1200",
        "algo": "pearl",
        "pass": "x",
        "miner": "bzminer_custom",
        "template": "%WAL%",
        "install_url": "https://github.com/bzminer/bzminer/releases/download/v100.11/bzminer_custom-v100.11.tar.gz",
        "user_config": ""
      },
      "pool_geo": []
    }
  ]
}

Hive OS built-in miner (manual binary replacement)

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.11
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, zeph, zephyr, sal, salvium	Monero, Zephyr, Salvium	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.