quanpool

Your payout address is a Quantus address. It starts with qz…. Quantus is post-quantum, so an ordinary Substrate wallet or subkey will not make a valid address. Use one of the two ways below.

Easiest: the official app

1. Install Quantus Wallet (public beta): iOS, Android.
2. Open it and choose Create wallet.
3. Write down the recovery phrase it shows, and keep it offline.
4. Your qz… address is on the main screen. Copy it: that is what you mine to.

Command line: quantus-cli

For a rig with no phone. The tool is called quantus. The ready-made binary is the simplest way and needs no Rust.

1. Ready-made binary. Take the Linux build (…x86_64-unknown-linux-gnu.tar.gz) from the quantus-cli releases page, then:

tar xzf quantus-cli-*-x86_64-unknown-linux-gnu.tar.gz
./quantus wallet create --name pool

2. Or build it with cargo. A fresh Ubuntu has neither Rust nor a compiler, so cargo install quantus-cli on its own will not work. Install both first, then the CLI:

sudo apt update && sudo apt install -y build-essential
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
. "$HOME/.cargo/env"
cargo install quantus-cli
quantus wallet create --name pool

create prints your qz… address, which is your payout address. To save the recovery phrase, export it to a file and keep it secret:

quantus wallet export --name pool --format mnemonic --output ./seed.txt

The miner has a benchmark built in. In the folder holding the binary you downloaded on the Start mining tab, run:

./quanpool-miner benchmark

It runs for about ten seconds and prints your hashrate. For a steadier number, give it longer. It uses every GPU by default:

./quanpool-miner benchmark --duration 30

The custom build's speed-up is a native GPU engine: CUDA on Linux with an NVIDIA GPU, and Metal on macOS (Apple silicon). On Windows it runs at the stock miner's speed. Add --gpu-devices N to benchmark only some cards.

By default the miner uses every GPU it finds and every CPU thread but two (one is left to the OS, one to the miner's own runtime, which feeds the cards and talks to the pool). You rarely need to change anything. The flags below cap it, split it, or turn one engine off. Every flag also has an environment variable, so it works in a config file or a service unit just as well.

GPU only (stop CPU mining)

Frees the processor for the rest of the machine and lets the card do all the work. Set the CPU workers to zero:

./quanpool-miner serve --cpu-workers 0   # ...plus your --node-addr / --auth-token / --tls-cert-sha256

CPU only (no GPU)

Turn the cards off with --gpu-devices 0. Note the custom build's speed-up is CUDA, so CPU-only mining runs at the stock miner's pace:

./quanpool-miner serve --gpu-devices 0

Set the number of CPU threads

--cpu-workers N caps CPU mining at N threads. Lower it to keep the machine responsive while it mines:

./quanpool-miner serve --cpu-workers 8

Pick how many GPUs

--gpu-devices N uses the first N cards; leave it off to use them all. Other GPU knobs: --gpu-throttle-ms N inserts a pause between batches to cut heat and power (0 = flat out), and --allow-integrated lets it use an on-board GPU even when a discrete card is present.

./quanpool-miner serve --gpu-devices 1 --gpu-throttle-ms 5

The same as environment variables

Handy for a .env file or a systemd unit: MINER_CPU_WORKERS, MINER_GPU_DEVICES, MINER_GPU_THROTTLE_MS, MINER_VERBOSE. Add -v (or MINER_VERBOSE=1) for verbose logs when something looks off.

MINER_CPU_WORKERS=0
MINER_GPU_DEVICES=1
MINER_GPU_THROTTLE_MS=5

Pool or solo

On this pool the mode is decided by the port you connect to, over QUIC and stratum alike, not by a flag: pick Pool or Solo under Mode on the Start mining tab and it sets the right --node-addr. The miner's own --mode flag only changes its log wording, so you do not need it here.

Barely, and the pool handles it for you. A rig far from the server, in the US or Asia with the server in Europe, loses a sliver of hashrate to the network round trip on every share. The pool measures your connection's round trip and adjusts your share difficulty automatically, giving a distant rig a slightly longer interval between shares so it spends the same tiny fraction on round trips as one next door.

There is nothing to configure, and it works with any miner, ours or the stock one: the pool only changes the difficulty it hands you, so no miner setting or build is involved. Your expected earnings are the same either way.

"timed out" and "reconnecting" in a loop. The pool speaks QUIC over UDP, and some networks block it. Test from the rig with nc -zvu <pool host> <port>; if nothing comes back, open outbound UDP to that port on your firewall or router. Where UDP cannot be opened, mine over stratum instead, which runs over TCP: pick Stratum under Connection on the Start mining tab.

Hashrate drops right after a start, then climbs back. That is the pool's variable difficulty settling on your rig, not a fault. The "Your difficulty" chart on your page shows the ladder moving; give it a few minutes.

The GPU is not used. Run ./quanpool-miner gpu-list to see what the miner detects, then pass --gpu-devices <n> explicitly. On Linux the NVIDIA driver must be loaded (nvidia-smi answers).

"certificate" or "fingerprint" errors. The miner pins the pool's certificate. Copy the exact --tls-cert-sha256 value from the Connect tab; a fingerprint from another pool or an old copy will refuse. Stratum through a forward or a proxy: Encryption → TLS, no cert check (--tls-insecure, 6.3.1+) or None.

Your address shows "never sent". The address the rig uses and the one you look up must match character for character. Re-copy it from your wallet; a lookalike character is rejected, never silently corrected.

macOS refuses to open the miner. The binary is not notarized: run xattr -d com.apple.quarantine ./quanpool-miner once, or allow it under Privacy & Security after the first refusal.