XID / MMM hashrate: workers, shares and last activity
Separate miner-reported, pool-estimated and chain-estimated hashrate; interpret workers without assuming device counts.
Plain text versionCompare matching measurements and windows
Record the source time, unit and field before comparing numbers. GH/s is 1,000 times MH/s. A web pool estimate and an instantaneous MMM local reading are not the same benchmark; short-window share activity affects estimates.
What workers and accepted shares establish
A worker is a work label under an address in the source. Accepted shares are pool work records, not confirmed blocks or paid income. Distinct labels help inspection, but names can change or be reused, and several machines can share an address.
Distinguish zero, unknown and absent records
A usable zero is displayed as zero; missing or unavailable fields remain a dash. An absent worker can mean an address mismatch or limited coverage, not necessarily an offline miner. Compare last activity with the local MMM state.
Inspect address fields in the XID monitor. See MMM mainnet setup for connections and balance and maturity for reward meanings.
Common questions
Does a lower pool hashrate prove a fault?
Not necessarily. Check units, source time, estimation window and share activity.
Do six workers prove there are six Macs?
No. Workers are work labels, not hardware inventory identifiers.