Bitcoin Cloud Mining

Difficulty adjustment in Bitcoin mining: definition

Bitcoin's difficulty adjustment resets every 2016 blocks to hold block times near 10 minutes. Here's how the 2016 block retarget and the factor of 4 cap on the target work.

Updated 2026-11-18

The short answer

Bitcoin's difficulty adjustment is the rule that keeps blocks arriving about every 10 minutes. Every 2016 blocks, the network compares how long those blocks actually took against a two week target and raises or lowers the difficulty to match. A single retarget never changes the target by more than a factor of 4 either way.

How the 2016 block cycle works

The Bitcoin Wiki describes difficulty as a measure of how hard it is to find a hash below a given target. Every Bitcoin client compares the actual time the blocks took against the two week goal and modifies the target by the percentage difference.

Here's the cycle. The network aims for one block roughly every 10 minutes, so 2016 blocks should take about two weeks if that pace holds exactly. At the end of each 2016 block stretch, every client checks the real time those blocks took. If they came in under two weeks, hashing was faster than expected, and difficulty goes up. If they ran over two weeks, difficulty comes down. The size of the change tracks how far over or under two weeks the period ran. That is the bitcoin mining difficulty adjustment every 2016 blocks.

So difficulty follows the total hash power pointed at the network. When more machines switch on, blocks come faster and the next retarget raises difficulty. When machines switch off, blocks slow down and difficulty comes down.

Reading the next retarget

You can watch the countdown live. As of mempool.space on 18 Nov 2026, the next retarget lands at block height 977,760, with an estimated change of +9.67%. That figure is an estimate and can still move, since it depends on how fast the remaining blocks in this period are found. The previous retarget was -9.13%, so the swing from one period to the next can flip direction.

A positive estimate means blocks have been arriving a little faster than the 10 minute pace, so the next retarget raises difficulty. If you want to turn difficulty into a rough sense of how often a given machine finds a block, the mining calculator does that math for you.

Why the change is capped and gradual

Two design choices keep the mechanism steady. First, the Target page says a single retarget never changes the target by more than a factor of 4 in either direction. That cap prevents large changes in difficulty. Second, difficulty can fall as well as rise. The Difficulty page answers the question "Can the network difficulty go down?" plainly: yes it can, which is what you'd expect when hash power leaves.

For more terms, see the glossary.

Common mix-ups

Difficulty is not the same as hashrate. Hashrate is the number of hashes the machines calculate per second. Difficulty is the target those guesses have to beat, and it only updates every 2016 blocks, so it lags behind sudden changes in hash power. People also assume difficulty always climbs, but any single retarget can be negative, as the -9.13% prior step shows.

Frequently asked questions

How often does Bitcoin difficulty change?

Difficulty changes every 2016 blocks. At one block about every 10 minutes, that stretch is meant to take roughly two weeks. Every node recalculates at the same height using the time the previous 2016 blocks actually took.

Can difficulty go down?

Yes. The Bitcoin Wiki states the network difficulty can go down. If the previous 2016 blocks took longer than two weeks, usually because hash power left, the next retarget lowers difficulty. The recent -9.13% step on mempool.space is one example.

How much can one adjustment move difficulty?

A single retarget can change the target by at most a factor of 4 in either direction, per the Bitcoin Wiki Target page. That cap keeps an unusually fast or slow two week period from swinging difficulty too far in one step.

Related guides

Sources