Quantus mining with no rewards: address, sync and index checks
Distinguish a valid zero, absent indexed rewards and refresh failure; check mainnet addresses, sync, miner compatibility and pool payouts.
Plain text versionStart with the data state
A failed refresh retains previous numbers with their original fetch time. Old source records are flagged separately. A successful query with no reward today can be zero; malformed or absent data stays unknown. Resolve retrieval failures before assessing mining.
Check the local node and network
Use the official mining guide to check mainnet, chain tip, node/miner versions and connectivity. Incomplete sync, orphan blocks, protocol mismatch or disconnection require local inspection. The website cannot read your logs or repair a process.
Check pool settlement separately
When mining through a pool, block rewards may first go to its block-producing address and later be transferred to participants. The queried miner_reward index is not the pool’s full transfer ledger. No block reward on your personal address does not establish no pool income; check pool settlement and wallet transactions.
Keep a comparable check record
Record the public address, network, reward block, source time and local state. Inspect recent rewards in the Quantus monitor and the explorer. See wormhole and QTC rewards and Mac mainnet sync.
Common questions
Does zero today prove my Mac is offline?
No. Zero rewards, index delay, pool settlement and device connectivity are different questions.
Are all pool payments listed as mining rewards here?
No. This queries the block-reward index; pool transfers require a separate check.