Bitcoin Difficulty: How the Adjustment Works
Bitcoin difficulty explained: what the target is, how the network retargets every 2,016 blocks to keep 10-minute blocks, and why the change is capped at 4x.
Bitcoin difficulty measures how hard it is to find a valid block. Every 2,016 blocks — roughly every two weeks — the network adjusts it automatically so that blocks keep arriving about every 10 minutes, no matter how much computing power is mining.
Target, difficulty and hashes
Under the hood, the protocol works with a target: a 256-bit number that a block header's hash must fall below to be valid. A lower target means fewer valid hashes and therefore more attempts on average. Difficulty is a friendlier way to express the same thing: it says how many times harder the current target is than the easiest one allowed, which is defined as difficulty 1 and was used for the genesis block.
A handy rule of thumb: the expected number of hashes needed to find a block is about difficulty × 2^32. At the time of writing (October 2026), difficulty is roughly 133 trillion (133 T), so the network needs on the order of 570 billion trillion hashes per block. Spread over 600 seconds, that matches the estimated network hashrate of about 1 ZH/s (1,000 EH/s).
How the adjustment works
The rule is simple and has not changed since 2009:
- The 2,016 blocks of an epoch are expected to take 2,016 × 600 seconds, exactly two weeks.
- At the end of the epoch, every node compares the actual time, taken from block timestamps, with that expectation.
- The new target is the old target multiplied by actual time ÷ expected time. If blocks came 5% too fast, difficulty rises by about 5%; if they came 5% too slow, it falls by about 5%.
- The change is capped at a factor of 4 in either direction per epoch, which limits the effect of extreme swings or manipulated timestamps.
No one votes on the new value. Every node computes the same result from the same chain, which is what makes the adjustment fully decentralised. You can follow the current epoch and an estimate of the next change on our difficulty adjustment tracker.
One quirk is worth knowing: the original code measures the time across 2,015 intervals rather than 2,016. This small off-by-one has a negligible effect and has never been fixed, because changing it would require a hard fork.
Why difficulty matters
- Predictable issuance. Because blocks average 10 minutes, new bitcoin enters circulation on a known schedule, and the date of the next halving can be estimated years ahead.
- Security. High difficulty means an attacker would need an enormous amount of hashrate to rewrite recent history.
- Miner economics. When difficulty rises without a matching rise in revenue, each machine earns less and older, less efficient hardware may be switched off. When it falls, the remaining miners earn a larger share.
Over the long term, difficulty tends to follow hashrate upwards as more efficient machines are deployed, but it can fall sharply when miners go offline. After the 2021 mining exodus from China, it dropped by about 28% in a single adjustment, the largest decrease on record.
Difficulty epochs and FreeBTC seasons
Each 2,016-block period is called a difficulty epoch. FreeBTC uses these epochs as its seasons: a season starts and ends with a real retarget, so its length depends on how fast the network is mining. When hashrate is growing quickly, seasons end a little early; when it falls, they stretch out. Because each epoch boundary is a fixed block height, you can count down to it exactly, even though the calendar date moves with the block time.
Frequently asked questions
Does higher difficulty make blocks slower?
Not in the long run. Difficulty rises because hashrate rose, and the two cancel out. Blocks only run fast or slow while hashrate is changing within an epoch, before the next adjustment catches up.
Can difficulty change in the middle of an epoch?
No. On Bitcoin's main network, difficulty stays fixed for all 2,016 blocks and changes only at the boundary.
The difficulty cycle shapes every FreeBTC round: when blocks have been arriving faster than 10 minutes during an epoch, more of them tend to beat the clock until the retarget. Keep an eye on the epoch progress and put that knowledge to work in the game.