BzMiner v100.03b8

Release v100.03b8 BETA of bzminer

All feedback is welcome ;)

• Pearl is about five times faster on Turing - RTX 20-series and GTX 16-series. An 80 W RTX 2070 Max-Q went from 5.73 TH/s to 29.17 TH/s at 76 W. The new kernel uses Turing's own tensor instruction and is picked automatically on any Turing card with 4 GB or more
• Pearl's dev fee is now 1%, down from 2%
• Pearl is faster on Blackwell - better throughput, and the proof work now overlaps the search
• Warthog no longer submits duplicate shares around the dev-fee switch
• Shares no longer get stuck on "pending" when the pool changes.
• Ergo mines on WoolyPooly again.
• Xelis improvement on older zen archs (zen 1, 2, 3)
• Overclocking works on 50-series cards again
• A core clock lock holds when an offset is applied with it
• cpu_threads now governs every CPU thread the miner starts, not just the mining workers - and they are all pinned
• OpenCL is only loaded if something can use it.
• Memory clock locks are checked against the card
• Hotkeys for the memory clock, and lock keys that start from where the card is
• The tuning hotkeys act on one card at a time, and every screen shows which one
• The mining table has a tbs column: the real, measured time between shares
• The top border counts pool reconnects
• The full hotkey legend is on every screen, and every key on it works everywhere
• The console draws correctly at any terminal size
• Log lines say what level they are, and are colored by it
• *[i]/[I]` steps the refresh rate through round numbers - 100ms, 250, 500, then every half second to 5s, then 6s, 7.5s, 10s, 15s, 20s, 30s, 45s, 60s. It used to multiply by 3/2, which lands on 295ms, 442, 663, 994
• New: DRAM timings. tCL/tRCD/tRP/tRAS and the secondaries as the board actually programmed them, in clocks and in nanoseconds - which is not what the DIMM is rated for whenever an XMP/EXPO profile is applied, declined, or hand-tuned. On the CPU device page, in the web dashboard's Memory panel, and in --ram-info. AMD platforms; Intel reports n/a and touches no registers
• The CPU's arch cell says the architecture
• The device page shows more
• CPU fans are detected on Linux boards the kernel has no sensor driver for. Mini-PCs especially carry an ITE or Nuvoton chip Linux does not recognise, and then nothing anywhere reports a fan. bzminer reads the chip directly when - and only when - no kernel driver has, as root and read-only. superio_fans false turns it off
• should work on mmpos stats page now
• Quieter, more useful logs.
• Fixed per-thread CPU usage read 0% on a fully loaded Linux machine; AMD CPUs reported temperatures for CCDs that are not physically fitted; the share log kept naming the thread count from startup after [t] had changed it; and the CPU row's cfg cell now tracks the thread count while it changes

---

Downloads

file	size	SHA-256
bzminer_v100.03b8_windows.zip	13.6 MB	2dc20b65aa95a6fd2b0b4cfc19df92ff07c9e75339f8c3db2ae0ef44491420ad
bzminer_v100.03b8_linux.tar.gz	14.8 MB	e3fda202f1b7845f10838e90472cb571068d050ddf4a84532e3d3d75c513cedc
bzminer_v100.03b8_macos.tar.gz	14.2 MB	6855b5f3337b6c70172079f0fccccfbb15305ce44e39a83a27da67cc5c1707e7

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.03b8"
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.03b8
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

algorithm	coin	dev fee	notes
ergo	Ergo	1%	Autolykos v2. GPU only, and memory-hard: it builds a table of N 32-byte elements (about 2 GB) in VRAM, so a card needs the room for it. N grows with block height, and the table is rebuilt when it changes. Wallet addresses start with '9'.
pearl	Pearl	1%	a zk proof-of-work: each share is a STARK proof, so it is far heavier per hash than a normal algorithm. Also mines SOLO - point -p at your node's RPC URL instead of a pool. Wallet addresses start with 'prl1'.
sha256d	—	none	The open-source SDK example: a full algorithm plugin (CPU+GPU, pool stratum, bench job source). Copy plugins/public/sha256d as a template for your own.
verus	VERUS	1%	VerusHash v2.2 CPU mining. A Verus R-address, optionally followed by .worker.
warthog	Warthog	2%	janushash - the GPU filters sha256t and the CPU runs verushash, on the same nonces. Needs BOTH a GPU and the CPU; one without the other finds nothing. Wallet addresses are 48 hex characters.
xelis	XELIS	1%	xelhash. Wallet addresses start with 'xel:'.

Files

download	what it is
bzminer_<ver>_<os>	Full. All 17 plugins compiled in. One self-contained binary - take this one unless you know you want the other.
bzminer_<ver>_<os>_lite	Lite. No plugins compiled in; loads them from a plugins/ folder beside it. Useless on its own - it needs the archive below.
bzminer_<ver>_<os>_plugins	The drop-in plugins. Required by lite; a full user can also drop a newer one here to override the built-in copy.

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.