Bitcoin Core getnetworkhashps RPC: Hash-Rate Estimation Guide

This guide explains Bitcoin Core getnetworkhashps RPC in plain English. It shows what the command does, what its result means and what it cannot prove.

Sampling window

nblocks controls the number of historical blocks; the default balances responsiveness against variance. Short windows react quickly but are noisy. Large windows smooth changes and lag real shifts. Always publish the chosen sample and ending height with the estimate.

Difficulty-period option

Minus one requests the interval since the last difficulty change. That aligns work under a common target but produces a short sample just after retarget. Handle boundary conditions and never assume the resulting value has constant statistical confidence.

Historical height

The optional height estimates conditions when a selected block was found. Validate bounds and active-chain identity. Recent heights may be reorganised, so retain the ending hash and chainwork rather than using a mutable height as the only reference.

Calculation and units

The result is hashes per second inferred from block work and elapsed time. Use wide numeric types and display SI prefixes without losing the underlying value. Separate H/s from miner-reported TH/s or EH/s and state rounding.

Variance and forecasting

Block arrival is probabilistic, so realised intervals vary even under steady hash rate. Confidence improves with longer samples but structural changes can make old data less relevant. Revenue models must include pool method, miner uptime, fees, difficulty and variance.

Cross-checking

Compare multiple windows and independent active-chain nodes. Large disagreement can indicate different tips, timestamps, sample boundaries or stale nodes. Public dashboards are useful context but not a substitute for verifying the underlying chain sample.

How specialists test it

Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.

Conclusion

getnetworkhashps is a chain-derived estimate whose quality depends on sample choice and block-time variance. It is useful for trends, not direct miner measurement or deterministic revenue forecasting.