Quantus mainnet · QPoW · verified against upstream docs 2026-09-29
Your mining command center
Everything a Quantus miner needs in one forge: a setup wizard that writes your commands for you, a rig builder on verified hashrates, a benchmark interpreter, the wormhole system demystified, and the security checklist the docs insist on.
⚙ Setup Wizard
Pick your platform, tune the knobs, and every command below rewrites itself with your values. Paste them in order. Commands follow the upstream MINING.md and the official quantus-miner README; --chain mainnet per the mainnet guides.
Sources: chain/MINING.md · quantus-miner README · docs.quantus.com/guides/mining
🔥 Rig Builder
Add your hardware. Hashrates come from published community benchmarks (labeled per row) — your mileage varies with driver, build, and thermals. The reward estimate uses the chain's real emission formula and is labeled an estimate, never a promise.
Your hardware
What could it earn?
Defaults are a dated snapshot capture (network hashrate ≈43.01 TH/s from difficulty 516,097,908,846,369 and ~5.798M total issuance, at block 195,788 on 2026-10-09). When the builder's hourly chain snapshot loads, both defaults refresh from it automatically. Verify with the Block Explorer.
Estimate only: assumes constant difficulty and the observed ~15.9s block pace from the Oct 9, 2026 chain snapshot (block 195,788) — not the 12s target. Real results follow luck and network growth.
Verified hashrate reference (click to expand)
| GPU | Hashrate | Source |
|---|
Figures are community-observed on Quantus QPoW (Poseidon2) and vary by miner build, driver, and clocks. The longcipher row shows the official build vs. a tuned community build — official first.
📊 Benchmark Interpreter
Run ./quantus-miner benchmark --gpu-devices 1 --duration 30, then punch your number in. We grade it against the verified reference for your card class.
- CUDA vs WGSL: upstream's own Clore benches show CUDA ~4.2× faster than the wgpu path on the same host — NVIDIA users should prefer the
--cuda-gpubuild. - Throttle: mining while you work? Add
--gpu-throttle-ms 50to give the desktop breathing room. - Keep-alive: the node drops idle miner connections after 60 s — the bundled miner heartbeats every 5 s; third-party miners must too.
- CPU is for the node, not the money: ~15 MH/s per CPU thread vs 1+ GH/s on a modern GPU. A 16-core CPU adds roughly 2% to a single RTX 4090 rig.
🌀 The Wormhole System
The single most important thing to understand before you mine: rewards are never sent to an address you paste in. They go to a privacy-preserving wormhole address derived from your preimage — automatically.
Your preimage
A 32-byte secret (inner_hash) generated on your machine by quantus-node key quantus --scheme wormhole. Never shared.
Poseidon hash
The node hashes your preimage with Poseidon — the same ZK-friendly hash behind QPoW. One way, quantum-resistant.
Wormhole address
Your reward address. The node derives it at startup and logs it. Rewards land here with no claim step — private by default.
inner_hash. It is effectively your mining private key. Lose it and the rewards are unspendable. Back it up offline, encrypted.Address from key generation.Sources: chain/MINING.md (wormhole section) · docs/reference/tokenomics.md (fee schedule)
🛡 Security Checklist
Straight from the upstream security guidance. Check each item off — progress is saved in your browser.
🧰 Troubleshooter
The failure modes the docs call out, in the order to check them. Start at the top.
🏊 Pools & Mining Software
Solo mining with the official miner is the default. Third-party pools and miners exist — listed here for completeness, with their fees stated. They are not endorsed; do your own diligence before pointing hashrate at anyone's server.
| Software / Pool | Type | Fee | Notes |
|---|---|---|---|
| quantus-miner official | Solo (external miner) | None | From Quantus-Network/quantus-miner. QUIC + TLS pinning to your node; wgpu, CUDA, and CPU engines. |
| QuanPool | Pool | Check their terms | Endpoint mainnet.quanpool.com:9834. Community-run; verify payout terms yourself. |
| InnovLab | Pool | Check their terms | Endpoint us.innovlab.cc:17601. Community-run; verify payout terms yourself. |
| Fl4shMiner | Third-party miner | 1.5% dev fee | Native CUDA kernels for RTX 30/40/50. Tested ~1.14 GH/s on RTX 4090, 458+ MH/s on RTX 3080 Ti. |
| SRBminer-Multi | Third-party miner | Check their terms | Reported ~765 MH/s on RTX 4080 SUPER (per bytwork). Fee schedule on their site. |
| HiveOS flight sheets | Farm OS | Varies | Community sheets exist for Quantus on HiveOS; useful for multi-rig farms. |
Pool endpoints and third-party performance figures via community guides (bytwork, fl4shminer README, 0xmoei guide). Treat any pool's uptime and payout claims as unverified marketing until you test with small hashrate.
📡 Monitoring
A miner who isn't watching isn't mining. Wire these up on day one.
Node logs
Watch for Imported #… — if block numbers stop climbing, you're stalled.
tail -f ~/.local/share/quantus-node/chains/mainnet/network/quantus-node.logPrometheus
Node metrics at http://localhost:9615/metrics (override with --prometheus-port). Upstream docs disagree on the default — 9615 in the current mining guide and sc_cli default, 9616 in the older chain/MINING.md table — confirm with quantus-node --help.
Miner metrics
The external miner exposes http://localhost:9900/metrics (override with --metrics-port).
Telemetry
telemetry.quantus.cat — find your --name to confirm the network sees you.
Local RPC
Latest block, straight from your node:
curl -s -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"chain_getBlock","params":[]}' http://localhost:9944Reward watch
Query your wormhole address on the QTC Block Explorer — rewards need no claim step.
Sources: chain/MINING.md (monitoring) · quantus-miner README