Bitcoin is a countdown, not a calendar
There are 79,434 blocks between you and the next halving — and every “date” you’ve read is a guess
Right now the Bitcoin chain is sitting around block 970,566. The next halving fires at block 1,050,000. Nobody will vote on it, nobody can delay it, and nobody knows the exact date — because the date is not in the protocol. Only the block height is.
This is the one thing I want you to internalize before you read anything else about the halving: a halving is not a scheduled event. It is a rule, and the rule is three lines of code.
The subsidy rule, in the actual Bitcoin Core source
CAmount GetBlockSubsidy(int nHeight, const Consensus::Params& consensusParams)
{
int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
if (halvings >= 64)
return 0;
CAmount nSubsidy = 50 * COIN;
nSubsidy >>= halvings;
return nSubsidy;
}Read that slowly, because the entire monetary policy of the biggest asset on Earth lives in those few lines.
nSubsidyHalvingInterval is 210,000. COIN is 100,000,000 — one bitcoin expressed in satoshis. nSubsidy starts at 50 * COIN, which is five billion satoshis. Then the line nSubsidy >>= halvings does a bitwise right-shift by the number of halvings — which is just integer division by 2, once for every 210,000 blocks.
That’s it. That’s the halving. There is no committee, no inflation target, no “maybe next year we’ll print a bit more.” There is a counter and a right-shift.
The 21 million cap is not a constant. It falls out of the math.
This is the part that surprises people who have been in crypto for years. Bitcoin does not store “21,000,000” anywhere. There is no MAX_SUPPLY = 21_000_000 in the source. What there is, is a geometric series that happens to sum to 21 million:
210,000 blocks × 50 BTC × (1 + 1/2 + 1/4 + 1/8 + …)
The sum inside the parentheses approaches 2, so the whole thing approaches 210,000 × 50 × 2 = 21,000,000. The cap is an emergent property of halving a subsidy forever, not a number someone typed in.
And “forever” has a concrete end: the if (halvings >= 64) return 0 line. Around halving number 33, sometime near the year 2140, the reward rounds down below a single satoshi, and integer division turns it to exactly zero. The last satoshi is mined, and miners are left earning only transaction fees.
Why the date keeps lying to you
You’ve probably seen four different “next halving dates” this month. Here’s a real spread, pulled from live trackers in late September 2026: 20 March 2028, 12 April 2028, 13 April 2028, 17 April 2028. That’s a three-and-a-half-week disagreement, and none of them is wrong.
The reason is that Bitcoin has no clock — it has a block counter. A block targets ten minutes, but “targets” is doing all the work. When hash rate grows, blocks arrive faster; the difficulty adjustment only corrects course every 2,016 blocks (roughly two weeks). So the calendar date of block 1,050,000 drifts with whatever the miners are doing, while the block number sits still. (If the mining mechanics are new to you, How Bitcoin Mining Works walks the target and the nonce from the ground up.)
The block height is a fact. The date is a forecast. Any headline that states a halving date as if it were scheduled is already wrong in a small, load-bearing way.
The schedule, all the way to zero
| Halving | Block | Year | Reward per block | Cumulative supply |
|---|---|---|---|---|
| Genesis | 0 | 2009 | 50 BTC | 0 |
| 1st | 210,000 | 2012 | 25 BTC | 10.5M |
| 2nd | 420,000 | 2016 | 12.5 BTC | 15.75M |
| 3rd | 630,000 | 2020 | 6.25 BTC | 18.375M |
| 4th | 840,000 | 2024 | 3.125 BTC | 19.6875M |
| 5th | 1,050,000 | ~2028 | 1.5625 BTC | 20.34M |
| 33rd | ~6,930,000 | ~2140 | 0 | 21M |
3.125 → 1.5625
The next cut: block reward, in BTC, at block 1,050,000
Look at the shape of that table and you’ll see the real story: the first four halvings issued 19.69 million of the 21 million coins — about 94% of everything that will ever exist. The remaining ~28 halvings will spread the last 6% across more than a century.
After the 2028 cut, daily issuance drops from roughly 450 BTC to 225 BTC, and Bitcoin’s annual supply inflation falls to about 0.4% — comfortably below gold’s historical rate. This is what “disinflationary” actually means: not “deflationary,” but “the inflation rate itself keeps halving.”
What the halving does not do
Here’s where I have to be the killjoy, because the amount of nonsense written about this event is staggering.
The halving is a supply event, not a price event. Cutting new supply in half does not, by itself, make anyone’s existing coins worth more. What it changes is the flow — how much new BTC miners must sell to pay for electricity. Whether the price rises is a bet on demand absorbing that change, and demand is a story about people, not a story about code.
The “T-500” folk talk — that the 500 days before a halving are the best time to buy — is a claim about four past windows. Four. Anyone who turns a sample of four into a law has skipped the statistics class. As the trackers themselves are careful to print: “the average is a description of a small sample, not a forecast.” I’d go further: with four data points, it’s barely even a description.
The halving is the most predictable event in Bitcoin — and the least predictive.
So here’s the honest way to hold this in your head, and I’ll keep it to three points:
- 1) Read the source, not the headline. The whole rule is one function. Anyone can read it. Most people arguing about the halving never have.
- 2) Quote the block, not the date. Block 1,050,000 is certain. “April 2028” is a guess with error bars measured in weeks.
- 3) Separate the supply fact from the price bet. The halving guarantees less new supply. It guarantees nothing about the price, and anyone who tells you otherwise is selling something.
Facts checked against the Bitcoin Core source (validation.cpp, GetBlockSubsidy), bitcoin.org’s halving page, and live halving countdown trackers (block height ≈ 970,566 on 9 October 2026). Not financial advice.
(The End)
