B.BlockAxis⌕ Search
Menu

Bitcoin mining and difficulty

A miner constructs a candidate block and searches for a header whose double SHA-256 hash does not exceed the target.

IntermediateContent revised · 13.09.20263 min reading · allow 5–10 more minutes for the workshopBlockAxis

Your learning plan

Distinguish miners from validating nodes

By the end, explain the diagram in your own words, solve the case and justify the correction.

Prerequisites : Bitcoin UTXOs explained · Consensus and finality

Level 2 · Intermediate →

Reading path · 5 / 35 · Intermediate

Key takeaway

A miner constructs a candidate block and searches for a header whose double SHA-256 hash does not exceed the target.

The essentials

A miner constructs a candidate block and searches for a header whose double SHA-256 hash does not exceed the target. It changes candidate data to try new hashes. Finding a qualifying result is expensive; checking one is comparatively cheap.

How it works

The header contains a version, previous-block hash, Merkle root, timestamp, encoded target and nonce. Bitcoin adjusts difficulty every 2,016 blocks, aiming for an average interval of roughly ten minutes. That is a statistical target, not a schedule or a maximum waiting time.

What to watch

A majority of hash power could favour reorganisations and some double spends. It cannot produce another user’s signature or force independently validating nodes to accept arbitrary inflation. Mining power controls neither private keys nor all protocol rules. The economic security budget depends on block subsidies, fees and the costs of producing work.

Understand the details

Miners assemble candidate blocks and repeatedly vary header-related data to find a hash below the target. Each attempt is unpredictable; there is no progressive completion bar. A successful miner broadcasts a block, but receiving nodes independently verify the proof of work, transactions and other consensus rules. Hash power cannot make an invalid transaction valid for those nodes.

Boundaries and common mistakes

Pools smooth individual revenue by sharing work and rewards. A pool’s reported share is not automatically one owner of all participating machines. Nevertheless, coordination and transaction selection can concentrate. Difficulty adjustments target an average block interval over time; they do not schedule an exact arrival time for the next block.

The mechanism at a glance

  1. Candidate transactions
  2. Search for proof of work
  3. Independent rule checks
  4. Accept valid block only
Distinguish miners from validating nodes. Conceptual map: read these four landmarks together with the explanation above.
Applied workshop · work at your own pace

Apply the lesson to a case

A miner finds a header with sufficient work but includes a transaction spending an already consumed output. Draw the checks performed by a receiving node. Mark the first failed rule and the consequence for the candidate block.

Does the energy already spent force other nodes to accept the block?

Choose one answer.

Terms in this lesson
Nonce
A number used in a particular protocol context: a mining search field in Bitcoin or an account transaction counter in Ethereum.
Hash
A fixed-length fingerprint computed from data by a hash function. It checks consistency, not truth.
Private key
A cryptographic secret used to authorise signatures under a signing scheme.
Prepare a correction note

Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.