Mining poolsCurated directory

QTC Pool Desk

Every known Quantus mining pool, compared honestly: real fees stacked the way they actually hit you, payout terms, PPLNS windows, and copy-paste connection commands — each fact stamped with the pool page it came from. Pools change their terms; re-verify on the pool's own site before you connect.

Read this before you point a miner anywhere

Pools are counterparties, not the chain. Until a payout lands in your wallet, you are trusting the operator's accounting. Both pools below say so themselves in different words.
Address only. A pool needs your qz… payout address — nothing else. Never paste a 24-word phrase into pool software or a pool website.
Re-copy endpoints and TLS pins from the pool's own site. Servers and certificate pins rotate; a stale pin fails permanently. Anything on this page is a snapshot dated 2026-10-01.
One GPU, one miner. Never run a pool miner and your own node (or two pool miners) on the same card — rewards follow hashrate, not worker count.

The directory

Two production QTC pools are documented well enough to list with verified terms. This is a curated directory, not an exhaustive one — if you run a QTC pool with public terms, reach @kshot9000.

Effective-fee comparator

The fee that matters is the stacked fee: pool fee, then the miner software's dev fee on what's left. Enter your hashrate — the desk does the rest against dated network defaults you can override.

Your hashrate Network hashrate (TH/s) Block reward (QTC)

Connection command builder

Pick a pool and miner software, paste your payout address — get the exact command. Endpoints and pins are snapshots: the builder warns you where you must re-copy from the pool's live page.

Pool Miner software Payout address Worker (optional)

Enter your qz… payout address to generate the command.

Pool vs Solo vs your own node

The real tradeoff: a pool sells you variance smoothing. Solo keeps the whole block but pays you in lottery tickets.

How PPLNS actually works

Both pools pay PPLNS — Pay Per Last N Shares.

1. You submit shares

Your miner proves work continuously. Valid shares enter the pool's window; stale or invalid ones don't.

2. The pool finds a block

The block reward (minus the pool fee) is split across every share inside the window — weighted by share difficulty.

3. The window slides

AriaPool's window is 2 × the block's difficulty — roughly two blocks' worth of network work. Shares older than that fall out. Stop mining and your weight decays to zero: pool-hopping across a dry spell earns you nothing.

4. Confirmations, then payout

Rewards credit once the block is confirmed (Quanpool: 105 blocks). Then the payout schedule runs — twice daily on AriaPool, hourly on Quanpool — and balances below the minimum carry over.

Luck cuts both ways: a pool that finds blocks faster than expected pays above the statistical average for a while, and vice versa. The comparator above shows the expectation; the chain decides the reality.

Run your own pool

For operators: not-only-mining-pool is open-source Go pool software with a Quantus engine in the default build.

Speaks both miner dialects — native QUIC (quantus-miner/2 with token auth + certificate pinning) and LuckyPool Quantus Stratum over TCP/TLS, so the official miner and SRBMiner-Multi work concurrently.
Pure-Go Poseidon2 verification of 512-bit nonces with strict U512 targets; fixed integer share difficulty per port.
PROP/SOLO payouts driven by finalized chain events with an independently funded signing wallet.
Validated end-to-end on a real node in CI — per the repo's engine docs, every engine below the reference Bitcoin path is E2E-tested against a live node.

Source: github.com/mining-pool/not-only-mining-pool (README + docs/PLUGGABLE_ENGINES.md), verified 2026-10-01. Running a pool makes you a custodian of other people's hashrate — the trust section at the top applies to you doubly.

Safety checklist

✓ Pool gets your qz… address. Nothing else. Ever.
✓ Verify miner SHA-256 checksums before running anything you downloaded.
✓ Re-copy the server address and TLS pin from the pool's live page — never from a screenshot, a chat message, or this desk.
✓ Watch your address on the pool's own stats page after the first share; if it never appears, your endpoint or pin is wrong.
✓ Keep miner/RPC/metrics ports off the public internet; only P2P (30333/tcp) should be public on a node.
✗ Never paste your 24-word phrase into pool software or a website. Address only.
✗ Don't "verify" a pool by sending it QTC — payouts flow pool → you, never the reverse.

Sources

Every number on this page traces to one of these, with the read date.

AriaPool pool page read 2026-10-01
Fee, PPLNS terms, payout schedule, endpoints, miner builds + SHA-256 checksums, TLS pin, QPoW constants.
0xmoei/quantus community mining guide read 2026-10-01
Quanpool terms table and the pool-vs-solo-vs-node matrix; terms as published on quanpool.com at guide-writing time.
quanpool.com read 2026-10-01
Pool stats + per-address lookup (JS-rendered). Re-copy the live Start mining command from the site.
not-only-mining-pool read 2026-10-01
Open-source pool software: Quantus engine (QUIC + LuckyPool Stratum), PROP/SOLO payouts, CI E2E on a real node.
Quantus weekly update — mainnet week 1 2026-09-16
11.2 TH/s average / 24.4 TH/s peak network hashrate, 7,000+ GPUs, 53,000+ blocks.