How to mine

How to mine Quantus

Poseidon2 on GPUs and CPU, no DAG. Pools, and solo mining against your own node over authenticated QUIC.

Algorithm
Poseidon2 over the Goldilocks field (-a quantus)
Mines on
NVIDIA GPUs (Turing and newer), the AMD RX 9070 XT, and the CPU
Dev fee
2%
Wallet
Starts with q, 49 characters
Solo mining
Yes, against your own node over authenticated QUIC
Launcher
start_quantus in the archive

Quantus is a post-quantum proof-of-work chain, and its hash is Poseidon2 over the 64-bit Goldilocks field. That is arithmetic work rather than memory work: there is no DAG to build and no big table to hold, so the algorithm runs on a GPU and on a CPU in the same shape, and a card with very little VRAM is not shut out of it. Both halves of a machine can mine it at once.

Before you start

  • A Quantus wallet address. They start with q and are 49 characters long.
  • A pool, or your own node. Both are covered below.
  • Hardware bzminer has a kernel for:
    • NVIDIA — Turing (RTX 20-series, GTX 16-series) and newer, up through Blackwell. The kernels ship as native code for each architecture; nothing is compiled on your machine.
    • AMD — the RX 9070 XT (gfx1201) only, through the ordinary OpenCL driver. No ROCm or HIP install is needed. Other AMD cards are rejected rather than mined slowly; that is the honest answer for now.
    • Any CPU, alongside either of the above.
Note

Quantus support is new. NVIDIA testing so far is on an RTX 3090 and AMD on an RX 9070 XT; the other architectures are built and checked against the reference implementation but have not been mined on hardware here. If yours is one of them, the Discord is where to say how it went.

The command

./bzminer \
  -a quantus \
  -p stratum+tcp://us-east.lproute.com:5660 \
  -w qYOUR_QUANTUS_ADDRESS_HERE \
  --worker rig1
  • -a quantus — the algorithm.
  • -p — the pool, or your own node for solo mining (below).
  • -w — your q address.
  • --worker rig1 — the rig’s name on the pool.

Pools

Three pools take Quantus from bzminer today. Two are ordinary stratum; the third, quanpool, is reached over QUIC instead — see below, it is barely more to type.

LuckyPool

One port, 5660, plain TCP, with variable difficulty and a 1% pool fee. Pick the region nearest you — they are all the same host name with the region in front:

stratum+tcp://us-east.lproute.com:5660      United States, east
stratum+tcp://us-central.lproute.com:5660   United States, central
stratum+tcp://us-ord.lproute.com:5660       United States, Chicago
stratum+tcp://us-west.lproute.com:5660      United States, west
stratum+tcp://ca.lproute.com:5660           Canada
stratum+tcp://br.lproute.com:5660           Brazil
stratum+tcp://eu.lproute.com:5660           Europe
stratum+tcp://pl.lproute.com:5660           Poland
stratum+tcp://tr.lproute.com:5660           Turkey
stratum+tcp://ru.lproute.com:5660           Russia
stratum+tcp://in.lproute.com:5660           India
stratum+tcp://sg.lproute.com:5660           Singapore
stratum+tcp://hk.lproute.com:5660           Hong Kong
stratum+tcp://jp.lproute.com:5660           Japan
stratum+tcp://id.lproute.com:5660           Indonesia
stratum+tcp://au.lproute.com:5660           Australia

Your Quantus address is the login and --worker names the rig, which is how the pool splits one address into several machines on its dashboard.

Kryptex

./bzminer -a quantus -p stratum+tcp://qtc.kryptex.network:7049 \
  -w qYOUR_QUANTUS_ADDRESS_HERE --worker rig1

Kryptex takes either a Quantus address or your Kryptex account name. It also wants the worker attached with a slash rather than a dot — wallet/worker, not wallet.worker. You do not have to do anything about that: bzminer recognises any kryptex.network host and sends the form that pool expects.

quanpool

quanpool has no stratum port at all. It serves the same authenticated QUIC interface a Quantus node does, so bzminer connects to it with quic:// rather than stratum+tcp://. The port chooses how you are paid: 9834 is PPLNS, 9844 is solo through the pool. The fee is 1%, and payouts run hourly from 0.11 QTC.

export BZ_QUANTUS_TLS_PIN=87dc37af6096a3ddc860b94368ca087775f3ad3e0c4e9bcff3b07ea08d8abef6
./bzminer -a quantus -p quic://eu.quanpool.com:9834 \
  -w qYOUR_QUANTUS_ADDRESS_HERE --worker rig1

That one export is the whole difference from a stratum pool. The pool proves who it is with a pinned certificate instead of a public CA, so bzminer has to be told the fingerprint to expect — it is published on quanpool.com, it is the same at every region, and it is checked before your address is sent. Your address and --worker are the login exactly as on any other pool; nothing else is needed.

quic://eu.quanpool.com:9834     Europe (main server)
quic://us.quanpool.com:9834     North America, Montreal
quic://asia.quanpool.com:9834   Asia, Singapore
Note

QUIC is UDP. If a rig sits behind a firewall that only allows TCP out, this pool looks like one that never connects — open outbound UDP to the port. Distance costs you nothing here: the pool measures your round trip and adjusts your share difficulty for it.

Careful

This protocol has no share acknowledgement, so bzminer can tell you a share was sent but never that it was accepted — the accepted counter stays at zero however well the rig is running. Your worker page on the pool is where shares are confirmed. That is a property of the protocol, not a sign anything is wrong.

Solo mining

Solo mining does not go through a stratum pool at all. Your own node opens an authenticated QUIC miner port, bzminer connects straight to it, and any block you find is yours whole. Start the node with the miner interface on:

quantus-node --validator --rewards-inner-hash YOUR_INNER_HASH --miner-listen-port 9833

The node will not talk to just anything that connects. It authenticates the miner with a token and identifies itself with a TLS certificate pin, and bzminer reads both from files named by two environment variables — so neither secret ever appears in a command line, a config file or a log. Both files are written by the node into its chain data directory:

export BZ_QUANTUS_AUTH_TOKEN_FILE=/path/to/node-data/chains/dev/miner-auth-token
export BZ_QUANTUS_TLS_PIN_FILE=/path/to/node-data/chains/dev/miner-tls-cert-sha256
./bzminer -a quantus -p quic://127.0.0.1:9833

There is no -w on that command because there is nothing for it to do: the node chooses the reward account, not the miner. If the miner runs on a different machine from the node, copy the two files across securely and keep them readable only by the user that runs bzminer.

Careful

The node protocol has no share acknowledgement, so bzminer cannot tell you a solo block was accepted — it can only tell you it sent one. Confirm blocks at the node itself (its RPC height is the plain answer). Solo pays in whole blocks, so a single rig can go a very long time between them; a pool is the steady option.

QUIC is UDP and needs a direct connection: a SOCKS5 proxy cannot carry it, and bzminer says so rather than half-working. Pool mining over TCP or TLS is unaffected by that.

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.

  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_quantus.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 quantus -p stratum+tcp://us-east.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --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

Solo mining talks to your node over QUIC, which is UDP. If the node is on another machine, open its miner port for UDP — a TCP-only rule looks like a miner that never connects.

  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_quantus.sh in any editor and replace the placeholder wallet. Other pools are in the same file as commented-out lines.

  3. Run it

    ./start_quantus.sh

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

    ./bzminer \
      -a quantus \
      -p stratum+tcp://us-east.lproute.com:5660 \
      -w qYOUR_QUANTUS_ADDRESS_HERE \
      --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

There is no Metal kernel for Quantus, so a Mac mines it on the CPU. Everything below still applies; the GPU simply sits this one out.

  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_quantus.sh in TextEdit or any editor and replace the placeholder wallet.

  3. Run it

    ./start_quantus.sh

    Or written out:

    ./bzminer \
      -a quantus \
      -p stratum+tcp://us-east.lproute.com:5660 \
      -w qYOUR_QUANTUS_ADDRESS_HERE \
      --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.

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 algorithmquantus
    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 URLus-east.lproute.com:5660 — 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 quantus is not among the algorithms mmpOS offers for bzminer, pick any and add --force_algo quantus 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.

The whole launcher

This is start_quantus.sh as it ships in the Linux archive: LuckyPool live at the top, and every other target — the other regions, Kryptex, and your own node — sitting under it commented out. Switching pool is commenting one line and uncommenting another.

#!/usr/bin/env bash
# bzminer - sample quantus launcher
#
# EDIT THE WALLET BELOW before running - it is a placeholder, not a real
# address, and the pool will reject shares sent to it.

cd "$(dirname "$0")" || exit 1

# The first line is live. To use a different pool, comment it out
# and uncomment one below.

./bzminer -a quantus -p stratum+tcp://us-east.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1

#   LuckyPool (US west)
# ./bzminer -a quantus -p stratum+tcp://us-west.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
#   LuckyPool (Europe)
# ./bzminer -a quantus -p stratum+tcp://eu.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
#   LuckyPool (Singapore)
# ./bzminer -a quantus -p stratum+tcp://sg.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
#   Kryptex - takes a Kryptex account name or a wallet; bzminer sends
#   Kryptex's wallet/worker form rather than wallet.worker
# ./bzminer -a quantus -p stratum+tcp://qtc.kryptex.network:7049 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
#   SOLO against your own node (quantus-node --validator --miner-listen-port
#   9833). The node picks the reward account, so the wallet on this line is
#   ignored. Both files below live in the node's chain data directory.
# export BZ_QUANTUS_AUTH_TOKEN_FILE=/path/to/node-data/chains/dev/miner-auth-token
# export BZ_QUANTUS_TLS_PIN_FILE=/path/to/node-data/chains/dev/miner-tls-cert-sha256
# ./bzminer -a quantus -p quic://127.0.0.1:9833 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1

# Add any of these to the end of the line you are running:
#   --nvidia                 mine only on NVIDIA (also --amd/--intel/--cpu)
#   --oc-power-limit 160     see readme.txt for the rest of the --oc-* options
#   --benchmark              ignore the pool and mine a local test server

And start_quantus.bat, the same file for Windows. Note the environment lines use set rather than export, and that they must come before the command that uses them:

@echo off
cd /d %~dp0

REM bzminer - sample quantus launcher
REM
REM EDIT THE WALLET BELOW before running - it is a placeholder, not a real
REM address, and the pool will reject shares sent to it.

REM The first line is live. To use a different pool, comment it out
REM and uncomment one below.

bzminer.exe -a quantus -p stratum+tcp://us-east.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1

REM   LuckyPool (US west)
REM bzminer.exe -a quantus -p stratum+tcp://us-west.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
REM   LuckyPool (Europe)
REM bzminer.exe -a quantus -p stratum+tcp://eu.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
REM   LuckyPool (Singapore)
REM bzminer.exe -a quantus -p stratum+tcp://sg.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
REM   Kryptex - takes a Kryptex account name or a wallet; bzminer sends
REM   Kryptex's wallet/worker form rather than wallet.worker
REM bzminer.exe -a quantus -p stratum+tcp://qtc.kryptex.network:7049 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1
REM   SOLO against your own node (quantus-node --validator --miner-listen-port
REM   9833). The node picks the reward account, so the wallet on this line is
REM   ignored. Both files below live in the node's chain data directory.
REM set BZ_QUANTUS_AUTH_TOKEN_FILE=C:\quantus\node-data\chains\dev\miner-auth-token
REM set BZ_QUANTUS_TLS_PIN_FILE=C:\quantus\node-data\chains\dev\miner-tls-cert-sha256
REM bzminer.exe -a quantus -p quic://127.0.0.1:9833 -w qYOUR_QUANTUS_ADDRESS_HERE --pass x --worker rig1

REM Add any of these to the end of the line you are running:
REM   --nvidia                 mine only on NVIDIA (also --amd/--intel/--cpu)
REM   --oc-power-limit 160     see readme.txt for the rest of the --oc-* options
REM   --benchmark              ignore the pool and mine a local test server

pause

Tuning

Poseidon2 is arithmetic, not memory traffic, so the core clock is what pays and the memory clock is nearly free to leave alone — the opposite of Ergo or Ethash. Raise the core, watch the power, and let the memory sit where it is:

./bzminer -a quantus -p stratum+tcp://us-east.lproute.com:5660 -w qYOUR_QUANTUS_ADDRESS_HERE \
  --oc-core-clock-offset 150 --oc-fan-speed "t:65[30-85]"

The CPU mines it too, in its own right. On a rig where the GPUs mine Quantus and you want the processor left alone, --cpu 0 turns the CPU off rig-wide; to keep a second algorithm on the CPU instead, give each one its own devices — the devices guide shows how.

Measure a change on the pool rather than on the console: give it an hour at each setting and compare accepted shares. The hashrate line moves faster than that, but it is an average and it will happily tell you a good story about a setting that is dropping shares.

Problems

  • “QUIC needs a certificate pin and a token”. A quic:// URL was given without a pin. Set BZ_QUANTUS_TLS_PIN to the 64-character SHA-256 itself, or BZ_QUANTUS_TLS_PIN_FILE to a file holding it — a pool publishes its pin, and your own node writes one into its data directory. The token is separate: for a pool it is just the wallet already on the command line, so leave it unset; for your own node set BZ_QUANTUS_AUTH_TOKEN_FILE, because that token is a secret and a file keeps it out of a command line and a log.
  • Solo connects and then nothing happens. Check the node is running with --miner-listen-port, that UDP reaches it, and that the token and pin came from that node’s data directory — a stale pin fails the check before the token is ever sent.
  • The AMD card is refused. Only gfx1201 (RX 9070 XT) has a bundled kernel. Other AMD cards will mine other algorithms in the same rig; use --devices to keep Quantus on the cards that can run it.
  • Shares are rejected. Press u and check the address: 49 characters, starting with q, nothing appended. On Kryptex an account name works too.

More in the troubleshooting guide.