BITCOINREVERSAL RESEARCH / NETWORK & HALVING RESEARCH
Bitcoin Halving Countdown
The next subsidy cut, in focus. Follow the estimated 2028 date, explore Bitcoin’s price history and compare three transparent timing methods.
NEXT HALVING · ESTIMATED DATE
Apr 11, 202816:01 UTC · 10-minute block model
Fixed at block 1,050,000 · date estimated.
Verified network snapshot · 2026-11-04 14:01:06 UTC · 64.06% of this epoch mined . Source: mempool.space.
Bitcoin price & halving history
Daily BTC/USD price and block subsidy, aligned in time
Drag to pan · pinch or + / − to zoom · tap for exact values. Keyboard: ← / → selects a day.
Historical closes and the timestamped intraday price are separate. Subsidy steps use UTC halving-date boundaries. The next halving date is an estimate.
Charting by TradingView Lightweight Charts™ · Method & sources
THE DIRECT ANSWER
When is the next Bitcoin halving?
The next Bitcoin halving occurs at block 1,050,000, when the block subsidy falls from 3.125 BTC to 1.5625 BTC. In the network snapshot above, the fixed ten-minute model estimates Apr 11, 2028 . Actual timing depends on future block production.
Bitcoin uses block height rather than a calendar appointment. Each halving arrives after another 210,000 blocks. A faster or slower mining interval changes the estimated date without changing the target block.
FROM ONE CHART TO A BROADER FRAMEWORK
Put the cycle in context.
Explore how BitcoinReversal combines defined market conditions into long-term buy-side, sell-side and transitional research signals.
ONE BLOCK TARGET · THREE ASSUMPTIONS
Why Bitcoin halving countdowns show different dates
These estimates use the same verified block height and calculation time. Only the assumed interval changes. The ten-minute target is a stable reference; trailing averages describe recently observed mining speed. None knows how future hashrate and difficulty will develop.
PROTOCOL TARGET
Apr 11, 2028600.00 seconds / block
Constant 600-second assumption.
LAST 2,016 BLOCKS
Apr 4, 2028592.00 seconds / block
Observed header-time average over this trailing window.
LAST 20,160 BLOCKS
Apr 5, 2028592.51 seconds / block
Observed header-time average over this trailing window.
Explore a block-time scenario
540–660 seconds is a sensitivity range, not a confidence interval. At this block height, a ten-second change shifts the estimated date by approximately 8.7 days.
ORIGINAL BITCOINREVERSAL RESEARCH · FROZEN STUDY V1
How accurate were these halving estimates historically?
We reconstructed all three methods before the 2012, 2016, 2020 and 2024 halvings. At four fixed remaining-block horizons, we used only block headers available at or before the calculation cutoff. Each table compares the estimate with the eventual halving block timestamp.
At the 4,320-block horizon—approximately 30 days at the protocol target—the 20,160-block method had a median absolute error of 0.619 days across these four events. At the 52,560-block horizon, its largest error was 30.488 days. A lower median does not imply a guaranteed smaller error next time.
| Method | Median absolute error | Largest absolute error | Events |
|---|---|---|---|
| 600-second target | 0.852 days | 1.238 days | 4 |
| Trailing 2,016 blocks | 0.661 days | 1.225 days | 4 |
| Trailing 20,160 blocks | 0.619 days | 1.145 days | 4 |
| Method | Median absolute error | Largest absolute error | Events |
|---|---|---|---|
| 600-second target | 2.656 days | 3.955 days | 4 |
| Trailing 2,016 blocks | 2.319 days | 3.712 days | 4 |
| Trailing 20,160 blocks | 0.835 days | 4.355 days | 4 |
| Method | Median absolute error | Largest absolute error | Events |
|---|---|---|---|
| 600-second target | 6.501 days | 10.115 days | 4 |
| Trailing 2,016 blocks | 3.002 days | 4.237 days | 4 |
| Trailing 20,160 blocks | 3.540 days | 6.698 days | 4 |
| Method | Median absolute error | Largest absolute error | Events |
|---|---|---|---|
| 600-second target | 12.782 days | 18.523 days | 4 |
| Trailing 2,016 blocks | 11.293 days | 14.044 days | 4 |
| Trailing 20,160 blocks | 9.918 days | 30.488 days | 4 |
The horizons are defined by remaining blocks, not exactly 30/90/180/365 calendar days before the event. Actual lead times are included in the downloads. This is a retrospective reconstruction using miner-reported header timestamps, not a record of forecasts published at the time. Four events are a small sample; the methods share data and are not independent trials.
How to reproduce the historical test
Download Study JSON, Block-header evidence and Reproduction code into one folder. Run python reproduce_halving.py. The script uses only the Python standard library and verifies the signed errors, actual lead times, medians, largest errors and sample counts. The frozen study contains 48 calculations: four halvings × four block horizons × three methods.
METHOD, DEFINITIONS & DATA PROVENANCE
How this Bitcoin halving estimate is calculated
Next halving block = (floor(current block / 210,000) + 1) × 210,000 Remaining blocks = next halving block − current block Estimated time = snapshot time + remaining blocks × assumed seconds per block Trailing interval = (tip header timestamp − older header timestamp) / window blocks Historical error (days) = (estimated timestamp − actual halving timestamp) / 86,400
Network observations
The current tip and trailing-window endpoints come from mempool.space, using an Esplora-compatible API. Block hashes and timestamps for the frozen historical study are downloadable above.
Price observations
The price chart uses BitcoinReversal’s completed daily BTC/USD series. Older imported prices have unrecorded original vendor and cutoff metadata. From March 14, 2026, daily values use the last available CoinGecko tick in each UTC day.
Schedule and limits
The Bitcoin Core consensus parameters specify the halving interval. Header timestamps are miner-reported; future hashrate, difficulty adjustments, network changes and source availability can alter date estimates.
Halving dates and UTC convention
Updates, frozen evidence and revisions
The network snapshot displays its verified capture time. The intraday price is separately timestamped. The historical study remains frozen at version 1.0.0; refreshed network data does not rewrite its results. A source outage retains the last verified snapshot and labels its age rather than substituting invented data. Corrections to the study require a new version.
SHARE & CITE
A dated result others can verify
Keep the observation date and method version with your citation. Link to the original page and distinguish completed observations from estimates.
Machine-readable data: Verified JSON dataset · Direct CSV download · First-recorded network snapshots
Bitcoin halving questions
Is the next Bitcoin halving date exact?
No. The target block is fixed under current consensus rules; the date depends on block production. The countdown estimates calendar time from a stated block interval.
Why does one countdown say March and another April 2028?
Different tools use different interval assumptions and averaging windows. This page shows three methods against the same captured block height, so that difference is inspectable.
Does a halving reduce the Bitcoin in my wallet?
No. It reduces newly issued bitcoin in the block subsidy. It does not divide existing holdings.
Will the halving make Bitcoin’s price rise?
The subsidy change affects new issuance. Demand, liquidity, positioning and other conditions also affect price. A scheduled reduction is not proof of a future price increase.
What happens to issuance per day?
At exactly 144 blocks per day, issuance falls from 450 BTC to 225 BTC. Actual daily block counts vary, so these are target-rate figures.
Which estimate is most accurate?
The answer depends on the horizon and metric. The historical table reports both median and largest absolute error across four events. It does not establish a universally superior method.