Hash rate is the number of hashing attempts a device, mining pool, or proof-of-work network performs per second. It is a rate of computation, usually expressed in hashes per second (H/s) and larger multiples such as terahashes per second (TH/s). A network-wide figure is an estimate inferred from block production and the protocol’s difficulty; it is not a direct count of every machine. Bitcoin Core, for example, labels its getnetworkhashps result an estimate over a selected range of recent blocks.
How a network estimate is made
In proof of work, miners repeatedly hash candidate block headers until one meets the network’s target. The Bitcoin developer guide describes this process and explains that difficulty changes the target threshold. Bitcoin Core’s network-hash-rate RPC estimates hashes per second from recent blocks; changing the averaging window can change the estimate, especially when blocks arrive unevenly. Therefore, two websites can report different estimates without either measuring the network’s hardware directly.
What hash rate can and cannot show
Aggregate hash rate describes estimated computational work pointed at a proof-of-work network. Under the protocol’s assumptions, an attacker attempting to replace recent proof-of-work history would need to produce competing work. But hash rate alone does not establish that a network is decentralized, immune to attacks, or economically healthy. The distribution of mining power, pool coordination, hardware access, protocol rules, and an attacker’s capabilities also matter.
Hash rate is not the same as transaction speed, the number of miners, or a miner’s expected profit. A device’s rated hash rate describes its own output; a pool’s rate aggregates participating machines; a network estimate covers observed network work. Profitability additionally depends on hardware efficiency, electricity costs, pool fees, network difficulty, block rewards and fees, and the asset’s market price. The developer guide explains that pooled miners are paid according to contributed shares under the pool’s payout method.
Related Terms
See Also
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
- Can Tokenomics Tell Whether a Crypto Project Is Sustainable?
- Why Bitcoin Can Move With Stocks — and Why Correlation Changes
Sources
- Bitcoin Core RPC: getnetworkhashps — Defines the result as estimated network hashes per second based on a selectable number of recent blocks.
- Bitcoin Developer Guide: Mining — Explains proof-of-work hashing, target thresholds, solo and pooled mining, and how pool payouts relate to contributed shares.
- Bitcoin Developer Guide: Block Chain — Describes proof-of-work targets and Bitcoin’s difficulty-adjustment rules.