A miner can run at the same displayed hashrate for two weeks and still produce a different reward total in each week. Its machine output, the network’s proof-of-work target and the pool’s payment method are different measurements. Start by identifying which one changed.
Hashrate measures a rate; difficulty describes the target
Hashrate expresses hashing work per second. Difficulty describes how demanding the network’s proof-of-work target is relative to its reference level. More hashes improve the opportunity to find valid work, but they do not schedule an individual miner’s next successful block. The Bitcoin developer guide explains the target requirement and the adjustment process.
On Bitcoin mainnet, the difficulty adjustment occurs at a 2,016-block interval with an approximately two-week target duration. “About two weeks” is not a fixed calendar appointment: actual block arrival times vary. A dashboard countdown based on recent block times is an estimate, not a protocol guarantee that a retarget will happen at a particular hour.
Network hashrate is estimated, not read from every machine
A network chart is not a live inventory of all miners’ power meters. Bitcoin Core’s getnetworkhashps documentation describes a network hashrate estimate based on recent blocks. A shorter and a longer observation window can yield different values without either provider observing a different physical network.
When comparing two dashboards, record the averaging window and observation time first. An abrupt move in a short-window chart deserves a different interpretation from a persistent change across longer windows. Do not subtract two unmatched snapshots and present the result as an exact number of miners that joined or left.
| Metric | Useful for | Not sufficient for |
|---|---|---|
| Local running hashrate | Monitoring machine output | Proving all work reached the pool |
| Estimated network hashrate | Comparing network activity over a stated window | Counting connected machines exactly |
| Network difficulty | Understanding the current proof-of-work target | Predicting the next block’s time |
| Net pool credit | Reconciling the pool’s credited reward | Measuring total business profit |
A 10% difficulty increase is not a 10% revenue subtraction
For an illustrative expected-value comparison, hold hashrate, operating time, block reward composition and other conditions fixed. If difficulty rises from an index of 100 to 110, the relative expected reward per unit of hashing becomes 100 ÷ 110 ≈ 0.90909091. That is approximately a 9.09% decrease, not exactly 10%.
If an invented baseline expectation were 0.001 BTC for a period, the corresponding simplified expectation would be about 0.00090909 BTC. This is a proportional sensitivity example, not a forecast of your next payout. It deliberately holds inputs constant that can change in practice. Pool payment rules and the distinction between gross reward and credited amount still matter.
Pool shares are not the same as network blocks
Pools use submitted shares as evidence of contributed work. Shares normally meet an easier target than a network-valid block, allowing the pool to measure contributions more frequently. Braiins’ explanation of shares and estimated hashrate describes this statistical measurement. Its older payout examples should not be read as a statement of the pool’s current reward scheme.
A high share count cannot be interpreted without the assigned share difficulty and time window. Similarly, changing the pool’s share difficulty is not the same event as Bitcoin changing network difficulty. Keep both labels in a log if the miner dashboard exposes them.
BTC output and cash operating surplus can move differently
Hashrate Index’s hashprice definition includes Bitcoin price, network difficulty, subsidy and transaction fees among its inputs. A stable BTC reward does not imply a stable value in the currency used to pay an electricity bill. Nor does higher currency revenue prove that energy and hosting costs stayed unchanged.
For a reproducible comparison, record the period, accepted-work basis, BTC credits, any currency-conversion price and separately measured electricity use. Then use the mining electricity worksheet to compare the entered revenue with costs. If the local miner looks steady but the pool display changes, use the pool-hashrate diagnostic guide before treating the difference as a network-difficulty effect.
Educational information, not a wallet audit, transaction validation or personalised financial advice. Service support and interfaces can change. Report an error with the page URL; never send recovery phrases or private keys.