How to mine

How to mine Warthog

janushash needs a GPU and the CPU together. What the calibration phase means, and how to mine solo.

Algorithm
janushash (-a warthog)
Mines on
A GPU (NVIDIA, AMD, Intel or Apple) and the CPU, together
Dev fee
2%
Wallet
48 hexadecimal characters
Solo mining
Yes, against your own node
Launcher
start_warthog in the archive

Warthog’s proof-of-work is deliberately split across both processors. The GPU filters sha256t candidates and the CPU runs VerusHash over the same nonces, and a result only counts when both halves agree. Neither half finds anything alone, so disabling either one stops the rig — and it is why a Warthog rig plans itself as a whole rather than as a list of cards.

Before you start

  • A Warthog wallet address: 48 hex characters.
  • A pool. Ones that authorised a real login when this build shipped:
    • stratum+ssl://us.vipor.net:5120 (vipor, TLS)
    • stratum+tcp://pool.us.woolypooly.com:3140 (WoolyPooly)
    • stratum+tcp://acc-pool.pw:12000 (acc-pool)
  • A GPU and a CPU with hardware AES and carry-less multiply — any x86-64 from about 2013 on, or Apple Silicon. Without them the miner says so and stops, rather than running a path that would find nothing.
  • Ideally a real PCIe slot. Warthog streams candidates off the GPU, so an x1 riser is a ceiling. bzminer measures each card’s bandwidth at startup and sizes the flow to it.

The command

./bzminer \
  -a warthog \
  -p stratum+ssl://us.vipor.net:5120 \
  -w YOUR_48_HEX_WALLET \
  --worker rig1
  • -a warthog — the algorithm.
  • -p — the pool, or your own node for solo.
  • -w — the 48-character address.
  • --worker rig1 — the rig’s name on the pool.
Careful

Do not add --nvidia or --amd on their own: naming a device type makes it the only type that mines, which switches the CPU off and stops the rig. To limit the GPUs, use --devices, which leaves the CPU alone.

Step by step, on your platform

Pick your platform. The steps are the same shape everywhere: get the archive, put your wallet in the launcher, run it, open the dashboard. Only the details change.

Note

The first two minutes print calibrating verus while the miner works out how hard to drive the GPU filter against the CPU. A near-zero hashrate during that is expected.

  1. Download and unzip

    Get bzminer_v100.82_windows.zip from the release page and unzip it anywhere you like — a folder on the desktop is fine. There is no installer and nothing is written outside that folder except the log. The SHA-256 of the archive is published beside it if you want to check the download.

  2. Put your wallet in the launcher

    Right-click start_warthog.bat, choose Edit, and replace the placeholder wallet with your own. The pool is already filled in; other pools are listed as commented-out lines in the same file. Save it.

  3. Run it

    Double-click the launcher. The console dashboard opens in a window. Or, from a command prompt in that folder, the same thing by hand:

    bzminer.exe -a warthog -p stratum+ssl://us.vipor.net:5120 -w YOUR_48_HEX_WALLET --worker rig1

    Windows Terminal is the better console for it: the old conhost window cannot scroll the log pane with the mouse wheel and select text at the same time. Everything still works in the old console; it is just less convenient.

  4. Open the dashboard

    Browse to http://127.0.0.1:4014/ on the same machine. Nothing to install and nothing to sign in to.

Overclocking on Windows needs no special privileges for the power limit and the fan, and no administrator prompt to mine. CPU register tweaks that speed up some CPU algorithms are optional and use the PawnIO driver; install-pawnio.bat is in the archive for that, and mining carries on without it.

Note

The first two minutes print calibrating verus while the miner works out how hard to drive the GPU filter against the CPU. A near-zero hashrate during that is expected.

  1. Download and unpack

    wget https://github.com/bzminer/bzminer/releases/download/v100.82/bzminer_v100.82_linux.tar.gz
    tar -xzf bzminer_v100.82_linux.tar.gz
    cd bzminer_v100.82_linux

    A single static binary; no packages to install, and no CUDA toolkit or OpenCL SDK. The GPU driver is the only thing it needs from the system.

  2. Put your wallet in the launcher

    Open start_warthog.sh in any editor and replace the placeholder wallet. Other pools are in the same file as commented-out lines.

  3. Run it

    ./start_warthog.sh

    Or the same command written out, which is all the launcher does:

    ./bzminer \
      -a warthog \
      -p stratum+ssl://us.vipor.net:5120 \
      -w YOUR_48_HEX_WALLET \
      --worker rig1

    If you redirect the output to a file or run it under a service manager, bzminer notices there is no terminal and switches to the plain scrolling log screen on its own, so the file is readable rather than full of cursor codes.

  4. Open the dashboard

    http://127.0.0.1:4014/ on the rig itself. To see it from another machine on your network, add --set http_address=0.0.0.0 to the command — there is no password on it, so only do that on a network you trust.

Overclocking on Linux is privileged. Every clock, power and fan change is a driver write that needs root, so run the miner with sudo when you use the --oc-* flags. Without root the run still mines; each refused knob is named in the log with the reason.

Note

Warthog runs on Apple Silicon with both halves on the one chip: the GPU filters sha256t through Metal and the CPU runs VerusHash through the ARMv8 Crypto Extensions.

  1. Download, unpack, clear the quarantine flag

    tar -xzf bzminer_v100.82_macos.tar.gz
    cd bzminer_v100.82_macos
    xattr -dr com.apple.quarantine .

    The build is not signed with an Apple Developer ID, so macOS refuses to open it until the quarantine flag is cleared. That last line does it once, for the whole folder. The archive is Apple Silicon only; it does not run on Intel Macs.

  2. Put your wallet in the launcher

    Open start_warthog.sh in TextEdit or any editor and replace the placeholder wallet.

  3. Run it

    ./start_warthog.sh

    Or written out:

    ./bzminer \
      -a warthog \
      -p stratum+ssl://us.vipor.net:5120 \
      -w YOUR_48_HEX_WALLET \
      --worker rig1
  4. Open the dashboard

    http://127.0.0.1:4014/ in Safari or any browser on the Mac.

On a Mac the GPU is reached through Metal, and only algorithms with a Metal kernel use it: Ergo, KawPow, Ethash, Pearl, Warthog and CryptoNight. XELIS, RandomX and Verus mine on the CPU there. There is no overclocking on macOS.

Careful

Warthog needs the CPU as well as the GPUs. Do not add flags that switch the CPU off, and do not run a second CPU-only miner beside it — the CPU half is what the whole rig is balanced against.

The clean way is Hive’s custom miner mechanism, which installs the current bzminer straight from the release page and lets you type any algorithm name. The Hive OS and mmpOS guide has the detail and the alternative of updating Hive’s own bzminer entry in place.

  1. Make a flight sheet

    Coin, wallet and pool as usual. For the miner pick Custom, then open Setup Miner Config.

  2. Fill in the custom miner form

    Miner namebzminer_custom
    Installation URLhttps://github.com/bzminer/bzminer/releases/download/v100.82/bzminer_custom-v100.82.tar.gz
    Hash algorithmwarthog
    Wallet and worker template%WAL% — just the wallet. Hive passes the rig name separately and bzminer joins the two itself, so a template with a worker in it would name the worker twice.
    Pool URLstratum+ssl://us.vipor.net:5120 — a bare host:port means plain stratum; write stratum+ssl://host:port in full for TLS
    Passx
    Extra config argumentsAny bzminer flag, on one line — overclocks, --devices, --cpu_threads.
  3. Apply it to the rig

    Hive downloads the package on first start. Hashrate, temperatures and shares appear on the Hive dashboard because bzminer serves Hive’s stats format itself on port 4014, so leave the web server on its default port.

mmpOS ships a bzminer miner profile. What it does not ship is the current version, so the profile gets a one-time download script, and any algorithm its own list does not know is reached with --force_algo.

  1. Create a miner profile

    Miner bzminer, the coin or algorithm, your pool and wallet. The rig name becomes the worker name.

  2. Install the current version

    In the profile, under Advanced, paste this into “Initiate command prior to miner launch”. It downloads v100.82 once and exits immediately on every later launch, so it costs nothing per restart. To move to a later release, change the version on the first line.

    export version="v100.82"
    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
  3. Name the algorithm if the list lacks it

    If warthog is not among the algorithms mmpOS offers for bzminer, pick any and add --force_algo warthog to the profile’s extra arguments. It overrides whatever the OS wrote into the pool block, which is exactly what it is for.

  4. Assign the profile to the rig

    Stats come from bzminer’s own web port, so keep the web server enabled on 4014.

What you should see

First the roster, then the PCIe bandwidth measurement (about a second per card), then the planner: it groups CPU workers by shared L3 cache and decides how many candidates each GPU should feed them. Then calibrating verus for about two minutes, during which the rate is near zero. After that the mining table settles and shares arrive.

Warthog’s status column carries a rig summary, which is why its table leaves out the pool info column by default; --mining-columns brings it back if you want it.

Tuning

Both halves at once. The tuner balances the GPU filter against the CPU’s VerusHash rate, so the usual GPU tricks apply less here: leave the card near stock and give the CPU room. A GPU pushed until it throttles drags the whole pair down.

  • --cpu_threads sets the CPU half. The default holds a thread or two back; a dedicated rig can use all of them.
  • A modest power cap and a fan curve on the GPU is plenty: --oc-power-limit 200 --oc-fan-speed "t:60[30-80]".
  • --no-bandwidth-test skips the startup measurement if you would rather save the second per card and let the planner assume a full-width slot.

Warthog wants the whole machine and shares a rig poorly. Do not pair it with a second algorithm in the same process.

Solo mining

Against your own node, either way it exposes work:

# over the node's RPC
./bzminer -a warthog -p http://127.0.0.1:3000 -w YOUR_48_HEX_WALLET

# over stratum, if the node was started with --stratum 0.0.0.0:3456
./bzminer -a warthog -p stratum+tcp://127.0.0.1:3456 -w YOUR_48_HEX_WALLET

Problems

  • It finds nothing. One half of the pair is missing. Check that neither the CPU nor every GPU has been disabled, and that nothing else is monopolising the CPU.
  • The rate is near zero for the first two minutes. That is the calibration phase, and it ends on its own. Give it the two minutes before judging anything.
  • It refuses to start on the CPU. The processor lacks the AES or carry-less multiply instructions the VerusHash half needs, so it cannot mine Warthog.
  • One card much slower than an identical one. Look at its PCIe link in the device page (d): a riser at x1 is the usual reason.

More in the troubleshooting guide.