Skip to content

Releases: dwespl/axehub-miner

AxeHub Miner v1.7.2

Choose a tag to compare

@dwespl dwespl released this 25 Oct 08:56

AxeHub Miner v1.7.2

Faster bc3hash, and a miner you can steer while it runs.

  • BitcoinIII (bc3hash) is faster on NVIDIA and AMD cards.
  • Controls in the live panel and on the status page: pause or resume the rig or one
    device, change wallet, pool, worker and temperature limit on the fly, save them to the
    config, tune a device or the whole rig, restart. Over HTTP every change needs
    --http-token; read-only status stays open.
  • More statistics: energy used, session average, hashrate history, time since the
    last share.
  • bc3hash on AMD also runs with AMD's own OpenCL driver (amdgpu-pro) on Linux.
  • bc3hash now mines on the CPU too (--cpu), on any processor (AVX2 makes it faster);
    far slower than a card, for a machine without one or for spare cores beside it.
  • No configuration changes - existing axehub-miner.conf files and Hive OS flight sheets
    keep working as-is.

One binary, three algorithms (whirlpool | bc3hash | sha3-256t), GPU and CPU.
Windows | Linux | Hive OS.

Verify your download against SHA256SUMS-v1.7.2.txt.

AxeHub Miner v1.7.1 — bc3hash on RTX 50-series and GTX 10-series

Choose a tag to compare

@dwespl dwespl released this 21 Oct 14:00

AxeHub Miner v1.7.1

Maintenance release — broader GPU coverage.

  • BitcoinIII (bc3hash) now runs on the newest and the older NVIDIA generations:
    RTX 50-series and GTX 10-series join the already-supported RTX 20/30/40 and
    GTX 16 cards. CapStash (whirlpool) and sha3-256t are unchanged and continue to cover
    the full range.
  • No configuration changes — existing axehub-miner.conf files and HiveOS flight sheets
    keep working as-is.

One binary, three algorithms (whirlpool | bc3hash | sha3-256t), GPU and CPU.
Windows · Linux · HiveOS.

Verify your download against SHA256SUMS-v1.7.1.txt.

AxeHub Miner v1.7 — bc3hash on every backend, AMD on Hive OS

Choose a tag to compare

@dwespl dwespl released this 19 Oct 16:42

AxeHub Miner v1.7

Adds bc3hash, BitcoinIII's current proof of work, on NVIDIA (CUDA) and AMD or other
discrete GPUs (OpenCL) — and AMD cards now mine it on Hive OS out of the box. The pre-fork
sha3-256t stays selectable, and CapStash (Whirlpool) is unchanged. One binary for Windows,
Linux and Hive OS.

Downloads

OS Archive
Windows x64 axehub-miner-v1.7-windows-x64.zip
Linux x64 axehub-miner-v1.7-linux-x64.tar.gz
Hive OS axehub-miner-1.7.tar.gz

Verify against SHA256SUMS-v1.7.txt (sha256sum -c).

Distributed in binary form only. 1% disclosed dev fee on CapStash (CAP) / BitcoinIII (BC3)
mining; the optional Monero dual-mine is 0%.

AxeHub Miner v1.6 — OpenCL backend for AMD

Choose a tag to compare

@dwespl dwespl released this 18 Aug 16:32

AxeHub Miner v1.6

Multi-backend solo miner for CapStash (CAP, Whirlpool-512 fold) and BitcoinIII
(BC3, triple SHA3-256), on CUDA / OpenCL / Vulkan / CPU, from one binary. Windows
and Linux. Works with any pool.

New in 1.6

  • New OpenCL backend for AMD. --backend opencl (or cuda,opencl on a mixed
    NVIDIA+AMD rig) drives AMD GPUs through OpenCL, which is faster than Vulkan on AMD.
    It uses the OpenCL runtime already on your system — nothing extra to install. NVIDIA
    still runs CUDA by default; add opencl only for the AMD card.

  • The tuner now tunes the memory clock as well. --tune measures on your card
    whether a lower memory clock saves power without costing hashrate, pins it when it
    pays off, and prints exactly what it saved. If your card gains nothing, it says so
    and changes nothing.

  • The core clock is now chosen with the memory clock already set. These are one
    operating point, not two settings: once memory stops taking a share of the power
    budget, the best core clock moves. Re-run --tune after upgrading — a clock picked
    by an older version was measured under different conditions.

  • mem_lock config key, same grammar as clock_lock (mem_lock = 0:810,1:810).
    Either key present in your config for a card this rig is mining makes the miner
    use your values and ignore the tuned file entirely, for both clocks. An entry naming
    a card the rig is not mining does nothing, and the miner says so at startup.

    NVIDIA only, and needs an Ampere or newer card with a recent driver. Anything else
    is told plainly that the feature is unavailable, and keeps mining.

  • AMD cards on Linux report board power on the status page and in the log, so watts
    and efficiency show on a Linux AMD rig. It comes from the same kernel sensor node that
    already supplied temperature and fan. (Windows AMD reports no power — the vendor
    library differs by card generation, so it is left unimplemented rather than guessed at.)

  • Smoother, quieter behaviour on long unattended runs, and clearer output while the
    tuner is working — each step is announced before it starts, so a long clock sweep
    shows its progress as it goes.

Releasing a tuned clock

The tuned point lives in <your-config>.clock (e.g. axehub-miner.conf.clock), beside
your config. The locks themselves live in the driver and outlive the miner, so deleting
that file is not enough on its own:

nvidia-smi -i <pci-bus-id> -rgc
nvidia-smi -i <pci-bus-id> -rmc

Two separate commands — nvidia-smi refuses them combined. -rgc on its own leaves
the memory clock pinned.

Verify

axehub-miner --selftest                    # CapStash / Whirlpool
axehub-miner --algo sha3-256t --selftest   # BitcoinIII / triple-SHA3

Both must print self-test PASS.

Dev fee

1%, disclosed (~6 s per 600 s), for CAP and BC3. The other 99% goes to your wallet.
The optional Monero (RandomX) CPU dual-mine has no fee.

AxeHub Miner v1.5 — temperature and fan for AMD

Choose a tag to compare

@dwespl dwespl released this 16 Aug 10:41

AxeHub Miner v1.5 — temperature and fan for AMD

Temperature and fan monitoring for AMD cards, alongside NVIDIA, so temp_limit covers
cards of either kind whichever backend they mine on.

Same two coins — CapStash (CAP), Whirlpool-512 fold, and BitcoinIII (BC3),
triple-SHA3-256 — same three backends (CUDA / Vulkan / CPU) from one binary, on
Windows, Linux and Hive OS. It works with any pool serving these coins; ours are
pool.axehub.app:3336 (CAP) and pool.axehub.app:3338 (BC3).

Temperature and fan on AMD

The miner reads a card's temperature and fan by its PCI bus id: AMD's control library on
Windows, the kernel's sensor node on Linux. On Linux any card whose driver exposes such a
node is read the same way. NVIDIA cards go through the management library, which reports
more detail.

The readings appear in the status display, in the HTTP API and on the Hive OS panel, and
temp_limit acts on them — a card that reaches the limit pauses until it has cooled.
A card whose sensors are unavailable reports no value, and the thermal limit stays out of
the way on that device; set your own fan curve there.

Self-test and CPU backend

--selftest on the CPU device checks every CPU kernel that could be selected on your
machine. Every CPU kernel proves itself against the reference implementation on your own
machine before it is used to mine.

The CPU backend's Whirlpool starting kernel is an 8-wide batch; per-machine autotuning has
the final say. The status display's device column shows the card model, with the vendor and
brand words dropped so the model itself has the room.

Downloads

Platform Asset
Windows x64 axehub-miner-v1.5-windows-x64.zip
Linux x64 axehub-miner-v1.5-linux-x64.tar.gz
Hive OS axehub-miner-1.5.tar.gz

Checksums are in SHA256SUMS-v1.5.txt, attached to this release.

Every build passes the bit-exact GPU==CPU self-test on both algorithms (--selftest).
1% disclosed dev fee; the optional Monero CPU dual-mine stays at 0%.

AxeHub Miner v1.4 — a tuned clock survives on Hive OS

Choose a tag to compare

@dwespl dwespl released this 15 Aug 06:42

AxeHub Miner v1.4 — a tuned clock survives on Hive OS

Clock tuning now sticks on Hive OS, and the CPU backend is more careful about which of
its kernels it picks.

Same two coins — CapStash (CAP), Whirlpool-512 fold, and BitcoinIII (BC3),
triple-SHA3-256 — same three backends (CUDA / Vulkan / CPU) from one binary, on
Windows, Linux and Hive OS. It works with any pool serving these coins; ours are
pool.axehub.app:3336 (CAP) and pool.axehub.app:3338 (BC3).

Hive OS: a tuned clock stays tuned

--tune sweeps the GPU core clock and saves the best one for the mode you asked for.
On Hive OS that value used to disappear the next time a flight sheet was applied,
because applying one rebuilds the miner config from the panel. It is now saved beside
the config in its own file, axehub-miner.conf.clock, which the flight sheet does not
touch — so the miner re-applies it at every start and there is nothing to copy into
the panel by hand.

--tune keeps its pick in that file and leaves your config alone. To clear a saved
clock, delete it and run nvidia-smi -i <pci-bus-id> -rgc to release the lock on a
card that is already running (the miner prints the bus id when it saves). If
you upgraded from an earlier version and already have a clock_lock line in your
config, that line still wins — remove it to let tuning take over.

A clock_lock line you set yourself in the flight sheet's Extra config arguments
box wins outright and the saved file is ignored, so pin every card you want in that one
line or leave the key out and let tuning own it.

The Hive OS package now ships its README.md, which covers the flight-sheet fields and
tuning end to end: running it from a Hive Shell, which field in the OC tab takes an
absolute locked clock rather than a +/- offset, and how to clear one.

CPU backend

The CPU backend now takes the median of several measurements per kernel on both
algorithms, and sizes each measurement to the machine so the check costs about the same
whether the CPU is fast or slow. On a machine where two kernels
are close together, the faster one is picked more reliably.

Downloads

Platform Asset
Windows x64 axehub-miner-v1.4-windows-x64.zip
Linux x64 axehub-miner-v1.4-linux-x64.tar.gz
Hive OS axehub-miner-1.4.tar.gz

Checksums are in SHA256SUMS-v1.4.txt, attached to this release.

Every build passes the bit-exact GPU==CPU self-test on both algorithms (--selftest).
1% disclosed dev fee; the optional Monero CPU dual-mine stays at 0%.

AxeHub Miner v1.3 — Hive OS support + native RTX 50xx

Choose a tag to compare

@dwespl dwespl released this 11 Aug 11:00

AxeHub Miner v1.3 — Hive OS support + native RTX 50xx

A solo miner for CapStash (CAP) and BitcoinIII (BC3) from one binary:
CUDA (NVIDIA), Vulkan (AMD / Intel & others) or CPU. Windows, Linux — and now
Hive OS. This build adds native GPU code for Blackwell (RTX 50xx); the
supported NVIDIA range spans GTX 10xx through RTX 50xx and newer.

Hive OS

  1. Wallets → Coins → Add Coin — add a custom coin (CapStash or
    BitcoinIII); the algorithm you pick there is only a Hive label, the miner
    takes its algorithm from the Hash algorithm field below. Then Add
    Wallet
    for that coin with your cap1... / bc1... address. The template
    field also accepts a literal address instead of %WAL%.
  2. Create a Flight Sheet, pick Custom as the miner, and set the pool to
    Configure in miner.
  3. Installation URL = the URL of axehub-miner-1.3.tar.gz below (right-click
    the asset in the Assets list and copy the link).
    Miner name = axehub-miner.
  4. Fill in:
Field Value
Pool URL (required) host:port — the port is required. pool.axehub.app:3336 for CAP, pool.axehub.app:3338 for BC3
Wallet and worker template (required) %WAL%.%WORKER_NAME%
Hash algorithm whirlpool for CAP (the default if left blank) — required for BC3: set sha3-256t
Pass optional — d=1 asks the pool for fixed difficulty 1
Extra config arguments optional tuning keys, one per line
  1. Apply the flight sheet to your rig.

To use a backup pool, add a second host:port in the same Pool URL field,
separated by a space
— it must serve the same coin (a second line is ignored).
Extra config keys are appended last and override earlier values, so keep the pool,
wallet and algorithm in their own fields; use the box for tuning only, e.g.
backend = vulkan or cpu_threads = 4. (temp_limit applies to the CUDA path;
without a temperature sensor there is nothing to enforce it against.)

Hashrate, accepted/rejected shares and uptime report to the Hive OS dashboard.
Per-GPU temperature and fan are reported on the CUDA (NVIDIA) path; on the Vulkan
path the miner cannot read those sensors, so they show 0 with no card mapping —
including on an NVIDIA card forced to backend = vulkan. Set your own fan curve.

AMD rigs, and Intel-only rigs, without a Vulkan driver: the start script attempts
to install mesa-vulkan-drivers once per boot (needs apt + network); if that fails
it prints it on the miner console (not in the miner log) — install the package
yourself and reboot.

Hive OS images based on Ubuntu 20.04 or newer (glibc 2.31+) are supported.

All three packages ship the Vulkan loader (vulkan-1.dll / libvulkan.so.1)
beside the binary; your GPU vendor's Vulkan driver is still required. The Linux
and Hive OS builds run on glibc 2.31 or newer.

Verify

# Linux / Hive OS
./axehub-miner --selftest
./axehub-miner --algo sha3-256t --selftest
# Windows
axehub-miner.exe --selftest
axehub-miner.exe --algo sha3-256t --selftest

Both must print self-test PASS. The check runs on the backend it selects, so you
can gate each one: add --backend cuda, --backend vulkan or --backend cpu.

Checksums — download SHA256SUMS-v1.3.txt next to your archive, then:

sha256sum --ignore-missing -c SHA256SUMS-v1.3.txt              # Linux
certutil -hashfile axehub-miner-v1.3-windows-x64.zip SHA256    # Windows — compare the
                                                               # output with the matching
                                                               # line in SHA256SUMS-v1.3.txt

Downloads

Target Archive
Windows x64 axehub-miner-v1.3-windows-x64.zip
Linux x64 axehub-miner-v1.3-linux-x64.tar.gz
Hive OS axehub-miner-1.3.tar.gz
Checksums SHA256SUMS-v1.3.txt

The Hive OS package has no v in its name on purpose — Hive OS requires
<miner name>-<version>.tar.gz.

Full flag list: see the README in this repository. The Windows and Linux packages
ship an axehub-miner.conf with the common keys documented inline; on Hive OS the
config is generated from the flight sheet.

1% disclosed dev fee. Optional Monero (XMR) CPU dual-mine stays at 0%.

AxeHub Miner v1.2

Choose a tag to compare

@dwespl dwespl released this 09 Aug 21:19

Multi-backend solo miner for CapStash (CAP) (Whirlpool-512 fold) and BitcoinIII (BC3) (triple-SHA3-256) — one binary, three backends (CUDA / Vulkan / CPU), Windows and Linux.

What's new in 1.2

  • Reworked clock tuner: --tune hashrate | efficiency | balanced | profit — pick the goal; the miner sweeps and locks the best clock for it and saves it to your conf (NVIDIA, needs admin/root).
  • Status page options on the command line: --http-bind (the page stays on localhost unless you ask for LAN) and --http-token (required before the API may change pool or wallet).
  • Smoother long unattended runs and pool reconnects.
OS Archive
Windows x64 axehub-miner-v1.2-windows-x64.zip
Linux x64 axehub-miner-v1.2-linux-x64.tar.gz

Set your wallet in axehub-miner.conf and run. Verify with axehub-miner --selftest (and --algo sha3-256t --selftest for BC3) — it must print self-test PASS. 1% disclosed dev fee (CAP/BC3); optional Monero dual-mine at 0% fee.

AxeHub Miner v1.1

Choose a tag to compare

@dwespl dwespl released this 15 Jul 15:37

AxeHub Miner v1.1

Adds a second coin: BitcoinIII (BC3), triple-SHA3-256. One binary now mines
either CapStash (CAP) (Whirlpool-512 fold, default) or BitcoinIII (BC3)
via --algo sha3-256t, on CUDA / Vulkan / CPU.

What's new

  • BitcoinIII (BC3) support — --algo sha3-256t (aliases: bc3, sha3).
    Point at pool.axehub.app:3338 with a bc1... wallet. Bit-exact GPU==CPU
    self-test against the SHA3 NIST vector: --algo sha3-256t --selftest.
  • Config gained an optional BC3 block and an algo key; --algo is documented
    in --help and the README.
  • The 1% disclosed dev fee applies to BC3 the same way it does to CAP. The
    optional Monero (XMR) dual-mine remains 0% fee.

Unchanged

  • CapStash (CAP) mining, efficiency tuner, live TUI + HTTP status, AxeHub app
    API — all as in v1.0.
  • Distributed as a code-protected, binary-only build for Windows and Linux.

Verify

axehub-miner --selftest                  # CapStash (Whirlpool)  -> self-test PASS
axehub-miner --algo sha3-256t --selftest # BitcoinIII (SHA3)      -> self-test PASS

Downloads

OS Archive Backends
Windows x64 axehub-miner-v1.1-windows-x64.zip CUDA · Vulkan · CPU
Linux x64 axehub-miner-v1.1-linux-x64.tar.gz CUDA · Vulkan · CPU

AxeHub Miner v1.0

Choose a tag to compare

@dwespl dwespl released this 15 Jul 15:37

AxeHub Miner v1.0 — first public release.

A fast multi-backend solo miner for CapStash (CAP) — a Whirlpool-512 fold
proof-of-work coin. One binary mines on NVIDIA (CUDA), AMD/Intel & other GPUs
(Vulkan), or CPU (AVX2), on Windows and Linux.

  • Live TUI + HTTP status page (/api/axehub/v1/ for the AxeHub app)
  • Bit-exact GPU==CPU self-test (--selftest must print self-test PASS)
  • Automatic efficiency tuning (--tune-eff, NVIDIA)
  • Optional Monero (XMR) CPU dual-mine at 0% dev fee
  • 1% disclosed dev fee on CapStash mining

Downloads

OS Archive Backends
Windows x64 axehub-miner-v1.0-windows-x64.zip CUDA · Vulkan · CPU
Linux x64 axehub-miner-v1.0-linux-x64.tar.gz CUDA · Vulkan · CPU

Set wallet in axehub-miner.conf to your CapStash (CAP) address, then run.
Binary-only release — see LICENSE.txt and THIRD-PARTY-NOTICES.txt.