Back to pool comparison
Publish blocks, not a claimed reward address
Publish the height and full block hash of blocks your pool finds in a public block list or API. We match both against our canonical history and read the reward address from the matching chain block. We do not accept a claimed reward address on trust.
For public feeds we monitor, matching and attribution run automatically; no need to contact us for individual blocks or address changes. A new feed must first be discovered and added to monitoring: publishing a list does not mean our collector has found it. If your feed is not yet monitored, or you cannot publish a list, contact [email protected] with your public site and available block evidence.
We cannot identify pools from payout behaviour: pool reward addresses use Wormhole exits, whose payouts do not appear as ordinary outgoing transfers in this index. An absence of outgoing records is not evidence that a pool has not paid miners. The verification method is published block heights and hashes, not inferred payout patterns.
Estimated hashrate is difficulty work divided by usable adjacent block intervals, not a direct measurement. Pool rows sort by that chain estimate, descending; unverified estimates follow known values. Unknown or solo covers all unassigned blocks and is not itself a verified pool. Fees and additional operating inputs remain self-reported on each pool’s detail page.
Loading unmapped-address snapshot.
Pool coverage and operator submissions
This list is not exhaustive. To be listed or correct a report, contact [email protected] with your public Quantus mainnet site, API or public terms, and sample block heights and hashes. A claimed reward address alone is not accepted. Clear public operator statements are valid sources; machine-readable fee and version endpoints make updates more reliable. No private keys or credentials are needed.
PearlFortune’s advertised pool remains under review: its public miner README names a Quantus pool, but its site returned a Cloudflare tunnel error on 11 September 2026 and no canonical block mapping could be verified. We do not assign blocks from the pearl-prover name.
The quantus-mainnet-pool telemetry name is also an unverified identity: neither timing nor a name substitutes for published block hashes. FURNACE, aria-mainnet and other steady producer labels remain unattributed where no matching public pool evidence was found. qtc.suprnova.cc, K1Pool, Qverse and qtc.luckypool.io listings for Qubitcoin are excluded: they concern a different coin.
SOURCES AND LIMITS
What do these numbers mean?
How are blocks assigned to pools?
We match pool-published round heights and hashes against our indexed canonical blocks, then read the reward addresses from those matched blocks. Recent blocks paying those verified addresses are attributed to the pool. Suprnova is an explicitly labelled exception: its hash field is a PoW hash, so repeated confirmed heights are compared with canonical authors; this has lower assurance than exact block-hash matching. Orphan/pending rows do not establish mappings. Mapping is evidence of a relationship, not proof of ownership. Prior evidence is rechecked against the chain even when APIs are unavailable. Conflicting or unmapped addresses remain unknown or solo.
What is the window?
Block shares use all indexed canonical blocks with timestamps in the trailing 24 hours. Missing history is labelled. Hashrate estimates sum difficulty over usable adjacent block intervals; shares use each pool's fraction of that work. Random variation and different time windows make these estimates differ from pool-reported rates.
Can hosted solo be separated?
Not reliably from reward addresses. Quanpool's published pooled and hosted-solo rounds can pay the same address. Unknown or solo is an attribution category, not a verified count of solo miners. Self-reported hosted-solo counters are shown separately and are not substituted for chain measurements.
What happens when a pool is down?
The collector fetches the listed Quantus providers about once a minute with an identifying User-Agent. API reports are labelled self-reported, timestamped, and hidden on failure or after 15 minutes. Fees are checked on the same cycle, independently of round data: a failed or missing fee is unavailable, and fee observations expire after 3 minutes. Quanpool’s optimised-miner developer fee is charged by the mining software in addition to the pool fee; the displayed approximate combined cost adds their published percentages, not a claimed exact effective deduction. Hosted-solo fees are stated separately. LuckyPool’s public lpminer statement is a valid independent fee source when the JSON API omits that field. Public statements and benchmark pages have explicit review dates and expire after seven days pending review; they are not represented as fresh API reads. Chain counts continue using canonical evidence. If the pool snapshot itself is missing or over 3 minutes old, the summary table shows Unavailable rather than stale figures or guessed pool names.
Which QTC network is this?
This page concerns Quantus mainnet. Public service listings and canonical reward-address attribution are separate; relay activity is not counted twice. Qubitcoin also uses the ticker QTC; aggregator entries for that different coin are not used here. Listing a pool is not an endorsement.