Bitcoin Difficulty Adjustment

Definition: Bitcoin difficulty adjustment is the consensus rule that periodically changes the proof-of-work target so mainnet block production averages close to one block every ten minutes. Nodes independently calculate and validate each new target; the rule does not make every block arrive on schedule.12

Date created The adaptive proof-of-work idea appears in Bitcoin’s 2008 white paper; the network’s genesis block is dated January 3, 2009.15
Protocol documentation Bitcoin Developer Guide
Directories Bitcoin Directory

How Bitcoin difficulty adjustment works

Proof of work asks a miner to find a block header whose hash is no greater than the network’s current target. A lower target makes acceptable hashes rarer and mining harder; a higher target makes them easier to find. Bitcoin Core expresses the target in each block header’s compact nBits field, while Bitcoin mining supplies the repeated hash attempts.23

On Bitcoin mainnet, nodes recalculate the target after each 2,016-block interval. The intended spacing is 600 seconds per block, giving a target span of 1,209,600 seconds, or 14 days. The adjustment compares the timestamps at the interval’s endpoints with that target span. If blocks arrived faster than expected, the next target becomes lower and mining becomes harder; if they arrived slower, the target becomes higher and mining becomes easier.234

Mainnet rule What it means
Retarget interval Every 2,016 blocks, not on a fixed calendar date.
Target timespan 14 days at the intended average of 10 minutes per block.
Adjustment bounds The measured span is limited to between one-quarter and four times the target span, so one retarget cannot change the target by more than a factor of four in either direction.
Proof-of-work limit The new target cannot exceed the network’s configured proof-of-work limit.

In simplified form, the next target is the previous target multiplied by the measured time span and divided by 1,209,600 seconds. Before that calculation, Bitcoin Core clamps the measured span to the one-quarter-to-four-times range; it then enforces the proof-of-work limit. This formula governs the mainnet retarget rule. Other Bitcoin networks can use different parameters or special minimum-difficulty rules, so the mainnet numbers should not be generalized to every test network.345

Why it matters—and where it falls short

Without periodic adjustment, a lasting change in total hash rate could shift the average pace at which miners find blocks. Retargeting is part of Bitcoin’s consensus rules: full nodes independently check that a block uses the expected target, rather than accepting a value chosen by an individual miner or pool.13

The rule responds in steps, not continuously. If hash rate rises or falls sharply just after a retarget, blocks can temporarily arrive faster or slower while the current target remains in force. The fourfold bound also means that an unusually large change may take more than one interval to be fully reflected. Consequently, the target aims for a long-run average; it does not promise an exact block schedule, a stable transaction confirmation time, or a direct measurement of current mining power.23

History

  • 2008: Satoshi Nakamoto’s white paper describes changing proof-of-work difficulty to target an average block rate as computing power and participation change.1
  • 2009: Bitcoin’s network begins with the genesis block and an adaptive proof-of-work target encoded in the original implementation.35
  • 2009–present: Bitcoin Core continues to calculate mainnet retargets from 2,016-block intervals and a 14-day target timespan; test networks may configure exceptions.34

Related Terms

Related Articles

See Also

Last updated: November 10, 2026.

Sources

  1. Nakamoto, Satoshi. “Bitcoin: A Peer-to-Peer Electronic Cash System.” 2008. https://bitcoin.org/bitcoin.pdf.
  2. “Block Chain.” Bitcoin Developer Guide. Accessed November 10, 2026. https://developer.bitcoin.org/devguide/block_chain.html.
  3. Bitcoin Core Developers. “pow.cpp.” Bitcoin Core source code. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/src/pow.cpp.
  4. Bitcoin Core Developers. “Consensus Parameters.” Bitcoin Core source code. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/src/consensus/params.h.
  5. Bitcoin Core Developers. “chainparams.cpp.” Bitcoin Core source code. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/src/kernel/chainparams.cpp.