Dashboard · VantagePlanned

Next Bitcoin Difficulty Adjustment Estimate

When is the next Bitcoin difficulty adjustment, and how big will it be?

Blocks left in the current epoch, the projected date of the next retarget and the change it would make at the epoch's pace so far.

ShareEmail itvoltfincrypto.com/apps/bitcoin-difficulty-adjustment-estimate
Blueprint

What the dashboard will show.

The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

Next retarget

Blocks left, the projected date and the estimated change.

Blocks until the retarget

blocks

Blocks between the latest block and the next retarget height.

Figurebitcoin_network_dailyAwaiting data

Projected retarget date

The projected time of the retarget block, from the epoch's average block interval so far.

Figurebitcoin_network_dailyAwaiting data

Estimated change

%

The difficulty change the epoch's pace so far implies, computed the way the rules will compute it at the retarget.

Figurebitcoin_network_dailyAwaiting data

Average block time this epoch

seconds

The average interval between blocks in the current epoch so far, against the ten-minute target.

Figurebitcoin_network_dailyAwaiting data

Estimate through the epoch

%

The estimated change recomputed at every block of the current epoch, which narrows as the epoch fills.

Line chartbitcoin_network_dailyAwaiting data

Block intervals this epoch

seconds

Each block's time since the block before it in the current epoch, with the epoch's running average drawn across.

Bar chartbitcoin_network_dailyAwaiting data

Past retargets

Recent retargets and how the estimates compared with what happened.

Last retarget

%

The difficulty change at the most recent retarget, against the epoch before it.

Figurebitcoin_network_dailyAwaiting data

Midpoint estimate error

%

How far the estimate made at each epoch's midpoint was from the actual change, averaged over the retargets in the period.

Figurebitcoin_network_dailyAwaiting data

Change at each retarget

%

The difficulty change at each retarget over the selected period.

Bar chartbitcoin_network_dailyAwaiting data

Every retarget

Each retarget with its height, date, new difficulty, change, the epoch's length in days and the estimate made at the epoch's midpoint.

Tablebitcoin_network_dailyAwaiting data

Period
Last year, last four years or every retarget since the genesis block
About

What it answers, and for whom.

The next Bitcoin difficulty adjustment happens at the end of the current epoch, and this dashboard counts the blocks left until it, projects its date and estimates how much difficulty will change if blocks keep arriving at this epoch's pace. The rules set the change: difficulty scales by how long the epoch's blocks took against a target of two weeks.

The estimate firms up as the epoch fills. Early in an epoch a few fast or slow blocks swing it widely; near the end it is close to exact, because most of the epoch's time is already on the chain. The dashboard draws the estimate as it moved through the epoch, names the block it was computed at and shows how past estimates compared with the changes that followed.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. The epoch starts at the last retarget height, a multiple of the epoch length; blocks left is the next retarget height minus the latest height from getblockchaininfo.
  2. The estimated change is the target timespan divided by the projected one, measured as the rules measure it from the epoch's first block to its last, and capped at a factor of four either way.
  3. The projected timespan and date extend the epoch's average block interval so far over the blocks left; both use header timestamps, which miners set within consensus limits.
  4. Each estimate is pinned to the block it was computed at, with its height and hash and the first block of the epoch it measures from.

The data it needs

Read from chain state and history

  • bitcoin_network_dailyTo buildBitcoin network by dayBlocks, hashrate implied by difficulty, difficulty, fees, transaction counts, block weight and miner revenue (subsidy plus fees) per day.
  • getblockchaininfo at the chain head: blocks, difficulty and mediantime
  • Header timestamps of every block since the last retarget height
  • bits and difficulty from the first and latest headers of the epoch
  • The actual change at past retargets, to compare estimates with outcomes
Questions

Questions people ask.

What is the Bitcoin difficulty adjustment?

At the end of every epoch, about two weeks of blocks, each node recomputes the mining target from how long the epoch took. If blocks came faster than every ten minutes on average, difficulty rises; if slower, it falls, so block times return toward the target.

How is the next difficulty adjustment estimated?

From the epoch so far: the average interval between its blocks is extended over the blocks left, and the projected epoch time is compared with the target time. The closer the epoch is to its end, the more accurate the estimate.

How much can Bitcoin difficulty change at once?

The rules limit each retarget to a factor of four up or down. In practice changes are far smaller, because hashrate rarely moves that much within two weeks.

Why do blocks come faster than every ten minutes?

When hashrate grows during an epoch, miners find blocks faster than the current difficulty expects. The next retarget raises difficulty to match, and until then blocks keep arriving early. Single intervals also vary widely, because finding a block is random.

Does the difficulty adjustment affect fees?

Not directly. Faster blocks clear the mempool sooner and can lower fee rates for a while, and slower blocks do the opposite. The fees themselves are set by users bidding for block space, not by difficulty.

Retarget
The recalculation of the mining target at the end of each epoch, which changes difficulty.
Epoch
The fixed run of blocks between retargets, about two weeks at the ten-minute target.
Target
The number a block's hash must fall below for the block to be valid. A lower target means a higher difficulty.
Median time past
The median timestamp of the previous eleven blocks. A new block's timestamp must be later than it, which limits how far miners can set times back.

Build Next Bitcoin Difficulty Adjustment Estimate on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.