BzMiner v100.81

Release v100.81 of bzminer

All feedback is welcome ;)

• improved pearl hashrate for amd rdna 3 and 4 and nvidia cmp 170
• 9070xt can now get over 150th
• improved quantus on 50 series nvidia gpus
• 405 mem lock shows its locked at 405 in the miner but its not actually locking in nvidia-smi
• added --oc-core-voltage-offset support for amd
• bz stops resetting oc's if no oc's are set in the config/command line
• dual c29,cn/gpu not failing for 6gb gpus anymore
• fixed high cpu/ram usage while gpu mining

Pearl — RX 9070 XT & RX 7900 XTX (bzminer v100.81)

GPU	Profile	OC	Hashrate	Power	Efficiency
RX 9070 XT	Max hashrate	--oc-core-voltage-offset -100	153.60 TH/s	315.8 W	0.486 TH/J
RX 9070 XT	Max efficiency	--oc-power-limit 221 --oc-core-voltage-offset -100	131.52 TH/s	221.0 W	0.595 TH/J
RX 7900 XTX	Max hashrate	--oc-core-voltage-offset -100	62.85 TH/s	389.0 W	0.162 TH/J
RX 7900 XTX	Max efficiency	--oc-power-limit 350 --oc-core-clock-offset -500 --oc-core-voltage-offset -100	54.48 TH/s	257.7 W	0.211 TH/J

Each profile ran 10 minutes on HeroMiners with 0 rejected shares, 0 stale shares and 0 failed proofs. Power is board power as reported by the driver.

Join us on Discord: https://discord.gg/NRty3PCVdB

---

Mines Tari, Conceal, Ryo, Ergo, Ethereum Classic, EthereumPoW, Ravencoin, Neurai, Neoxa, Meowcoin, Clore, nexa, Pearl, Quantus, Monero, Zephyr, Salvium, VERUS, Warthog and XELIS, and ships bramring and sha256d as the open-source SDK example.

Downloads

file	size	SHA-256
bzminer_v100.81_windows.zip	46.5 MB	065472adf6d3a05ec00e38b2611ff9d1cd42fe2cbcfdd60fb62dc183a626e976
bzminer_v100.81_linux.tar.gz	46.8 MB	7de384e9e0a1632c21bfa179b693af38b50598ca64980153bf2140f3372e87c9
bzminer_custom-v100.81.tar.gz	46.8 MB	667e6f66b4a278d87d9084204dd60b87bc24ef5c2231f2c2317cffdf6330628b
bzminer_mmpos-v100.81.tar.gz	46.8 MB	3e249b8537e457186cd145c665d81110937c4fc9204b6054225aea93c9328977
bzminer_v100.81_docker.tar.gz	13.4 KB	9c1f54586cfb767a1c456247c2c17a6f1e1f178da7fc09c098955e688f47c4e0
bzminer_v100.81_macos.tar.gz	59.3 MB	057d8f6f522a3030590a6a28132e028462c8a8489e7056108ddc8b2a0458ca13

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.

config.txt may be JSON or a command line. The shipped file is JSON — every setting inside one { } object. bzminer equally accepts the same file written as the options you would have typed, which is what a mining OS generates and the easier form to write by hand:

# one option per line, or a flag and its value on one line
-a pearl
-p stratum+tcp://pool:1234
-w YOUR_WALLET
--worker "My Rig"

Quote a value containing a space, and start a comment with #. An option you type on the command line beats the file's copy of it, so the file is a default you can override without editing it.

Docker

There is an image, and it carries the GPU userspace as well as the miner - no ROCm install, no driver packages, nothing on the host but a kernel driver:

docker pull bzminer/bzminer:v100.81
docker run --rm -it --gpus all bzminer/bzminer -a pearl -o stratum+tcp://pool:port -w YOUR_WALLET

The identical image is on GitHub as ghcr.io/bzminer/bzminer:v100.81 if you would rather not pull from Docker Hub.

Or keep your config, log and plugins on the host and run it as a service:

docker run -d --name bzminer --restart unless-stopped --gpus all \
    -v /opt/bzminer:/data -p 127.0.0.1:4014:4014 \
    bzminer/bzminer --set http_address=0.0.0.0

With no arguments it runs /data/config.txt; anything you pass goes straight to bzminer, so every command line on this page works unchanged. http_address has to be 0.0.0.0 for the dashboard, because the default 127.0.0.1 binds the container's loopback, which no published port can reach.

GPU flags differ per vendor. NVIDIA is --gpus all (with nvidia-container-toolkit on the host). AMD and Intel are --device /dev/kfd --device /dev/dri --group-add video --group-add render and --device /dev/dri. Overclocking, MSR tuning and huge pages additionally need --privileged; mining does not.

Update with a pull, not the miner's self-update - and the old tag stays published, so a rollback is just naming it:

docker pull bzminer/bzminer && docker restart bzminer

The binary inside the image is byte-identical to the one in bzminer_v100.81_linux.tar.gz above. Full documentation: docker run --rm bzminer/bzminer cat /opt/bzminer/docs/DOCKER.md.

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.81"
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.81.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.81/bzminer_custom-v100.81.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.81
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.

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.