Understanding how Bitcoin mining works begins with one distinction: miners do not create arbitrary coins or approve transactions by personal judgment. They compete to produce a valid proof of work for a candidate block. The winning block can extend Bitcoin’s public ledger, while every validating node independently checks that the block follows the network’s consensus rules.
This process combines transaction ordering, monetary issuance, and resistance to rewriting history. It is deliberately costly to propose blocks, but inexpensive for nodes to verify them. That asymmetry is central to Bitcoin’s security model.
From pending transactions to a candidate block
Bitcoin transactions are broadcast across a peer-to-peer network. Valid transactions that have not yet been confirmed may be held in nodes’ mempools. A miner selects transactions, usually prioritising those that offer higher fees relative to their data size, and assembles a candidate block. The miner also includes a coinbase transaction that claims the permitted block subsidy and transaction fees.
The block header commits to the selected transactions through a Merkle root. It also includes the previous block’s hash, a timestamp, a version, a compact representation of the current proof-of-work target, and a nonce. Changing the nonce or other adjustable data changes the header hash.
Proof of work and the target
Mining equipment repeatedly hashes block headers using SHA-256. A valid result must be numerically below the network target. Because cryptographic hash outputs are unpredictable, miners cannot solve the task through a shortcut; they make many trials. A lower target means fewer acceptable outputs and therefore more expected work.
Finding a valid hash does not guarantee permanent inclusion. Two miners can occasionally find blocks close together, creating competing tips. Nodes follow the chain with the most cumulative proof of work, and one branch normally becomes dominant. A transaction gains stronger settlement assurance as additional blocks build on top of it, although no fixed confirmation count eliminates every conceivable risk.
What hash rate measures
Hash rate estimates how many hashing attempts miners collectively perform per second. It is inferred from the rate at which blocks are found and the current difficulty; it is not measured by a central meter. Short-term estimates fluctuate because block discovery is probabilistic.
More hash rate generally means an attacker would need more computing work to compete with honest miners. Yet hash rate alone is not a complete decentralisation measure. Geographic distribution, mining-pool concentration, hardware supply, energy sources, and ownership all matter. Pools coordinate work and distribute proceeds, but individual operators can usually redirect their machines to another pool.
Why mining difficulty adjusts
Bitcoin targets an average interval of roughly ten minutes between blocks. Every 2,016 blocks, nodes recalculate the proof-of-work difficulty using the time taken to mine the preceding adjustment period. If blocks arrived too quickly, difficulty rises; if they arrived too slowly, it falls. The protocol constrains the size of an adjustment.
At the target pace, 2,016 blocks take about two weeks, but the calendar duration can differ. Difficulty does not update continuously, and ten minutes is an average rather than an appointment. One block might arrive seconds after the previous block and another might take much longer.
This feedback mechanism lets the network accommodate changes in deployed computing power without permanently accelerating or slowing issuance. When new machines join, their immediate effect is faster expected block production; the next adjustment then raises the work required. When hash rate leaves, the reverse can occur.
Block subsidy, transaction fees, and rewards
A miner’s gross block reward has two components: the newly issued subsidy and fees from transactions included in the block. The subsidy halves every 210,000 blocks. Bitcoin’s fourth halving occurred at block 840,000 on 20 April 2024 UTC, reducing the subsidy from 6.25 BTC to 3.125 BTC.
Fees are not created by the protocol on a fixed schedule. A transaction fee is the difference between the value of its inputs and outputs. Miners can choose which valid transactions to include, subject to block constraints, so fee rates become important when demand for block space exceeds available capacity.
The subsidy cannot be spent immediately: consensus rules require coinbase outputs to mature for 100 blocks. A miner that claims more than allowed creates an invalid block that full nodes reject, regardless of how much proof of work it contains.
Mining economics and pools
Revenue depends on blocks found, bitcoin-denominated rewards, and bitcoin’s market value. Costs include electricity, hardware, cooling, facilities, staff, financing, and pool charges. Difficulty and competitors’ efficiency affect how much reward a given machine can expect. Profitability therefore changes even when the protocol rules stay constant.
Solo mining produces irregular results: a small operator could wait a very long time to find a block. Pools reduce payout variance by combining participants’ work and distributing revenue according to submitted shares. Pool policies differ, and a share proves contributed work at a lower threshold; it is not itself a network-valid block.
What mining secures—and what it does not
Proof of work makes past blocks increasingly expensive to replace and provides an objective basis for choosing among competing histories. It does not allow miners to spend coins without valid signatures, increase the subsidy, or rewrite consensus rules accepted by nodes. Miners order valid transactions; nodes enforce validity.
A miner or coalition with dominant hash power could attempt transaction censorship or chain reorganisations. Such power would be serious, but it would not reveal private keys or make invalid transactions valid. Economic incentives, detection, countermeasures, and the attacker’s costs complicate real scenarios, so a raw hash-rate percentage should not be treated as a complete probability forecast.
How to evaluate mining data
- Separate measured values from estimates: network hash rate is inferred and profitability models depend on assumptions.
- Compare fee revenue with subsidy revenue, especially around halvings, without assuming a short sample predicts the future.
- Check whether pool statistics describe block production, reported connected hash rate, or ownership; these are different concepts.
- Use a full-node implementation or protocol documentation for consensus rules rather than relying only on mining-company marketing.
Bitcoin mining links physical expenditure to digital consensus. Difficulty keeps block production near its intended pace, hash rate reflects the work competing for rewards, and the declining subsidy shifts the long-run revenue mix toward fees. Together these mechanisms explain both the security provided by miners and the financial pressure under which they operate.