CatBitcoin

The next Bitcoin halving, explained

Updated August 6, 2026

Most people hear "halving" and picture a date already circled on a calendar somewhere, the way you'd know a leap year is coming years out. That's not quite how it works. The event that triggers a Bitcoin halving is a block height, not a date, and the calendar date just falls out of however fast the network happens to produce blocks between now and then.

What actually gets cut in half

Every time a miner finds a new block, the Bitcoin protocol pays out a fixed number of newly created bitcoin as a reward, on top of whatever transaction fees are in that block. That reward started at 50 BTC per block back in 2009. Every 210,000 blocks, the protocol cuts it in half. This is written directly into Bitcoin's consensus rules. No committee votes on it, no announcement triggers it, it just happens automatically once the block count crosses the threshold.

Why that lands around every four years

Bitcoin targets an average of one block every 10 minutes. Do the math on 210,000 blocks at that pace and you land close to four years, which is why people talk about the halving as a roughly four-year cycle. But "targets" is doing real work in that sentence. Block times aren't fixed; they drift with how much computing power is pointed at the network at any given moment. Every 2,016 blocks, the protocol adjusts mining difficulty up or down to pull the average back toward 10 minutes. It's a correction mechanism, not a guarantee, so short stretches of faster or slower blocks are completely normal.

The halving record so far

Four halvings have happened since 2009. Here's the reward at each one, by block height rather than by date, since block height is what actually triggers it.

HalvingBlock heightApproximate dateNew block reward
Genesis (starting reward)0January 200950 BTC
First halving210,000November 201225 BTC
Second halving420,000July 201612.5 BTC
Third halving630,000May 20206.25 BTC
Fourth halving840,000April 20243.125 BTC
Fifth halving1,050,000expected around 20281.5625 BTC

As of now, the block reward sits at 3.125 BTC, set at the April 2024 halving. If you ever want to see what an amount like that looks like in sats rather than BTC, the sats converter handles that arithmetic without touching price at all, since it's pure unit conversion.

Why the exact date isn't fixed years ahead

The fifth halving is expected at block 1,050,000. That's still a stretch of blocks away, and each individual block carries a small amount of timing variance around the 10-minute target. Alone, that variance is tiny, a few minutes here or there. Stacked across 210,000 blocks, it adds up to something real. A week or two of drift either direction is entirely ordinary, and a large, sudden shift in global mining hash rate (hardware coming online or going offline at scale) can nudge the estimate further. Nobody can honestly hand you an exact calendar date for a halving that's still years out. The estimate narrows as the block count climbs closer, but it stays an estimate until the block is actually mined.

What a halving isn't

It helps to be precise about scope here. A halving is a change to how many new bitcoin get created per block. That's the whole mechanism. It says nothing, by itself, about what happens to demand, price, or anything else people like to speculate about around the event, and this page isn't the place for that kind of guessing. What a halving does, mechanically and only, is shrink the rate of new supply entering circulation, on a schedule that keeps repeating until the reward rounds down toward zero sometime in the next century.

It's also worth saying plainly that the halving has nothing to do with Bitcoin's cryptography or address security. Reward schedule and key exposure are entirely separate questions. If it's the latter you're actually curious about, the quantum computing explainer covers what changed in 2026 and why, and the wallet checker lets you look up how exposed a specific address actually is right now.

My own take, for what it's worth: the halving is worth understanding once, properly, so the mechanism stops feeling mysterious. After that, I don't think it deserves close tracking as the date estimate shifts by a week here or there over the next couple of years. It's a fixed, automatic piece of code doing exactly what it was written to do back in 2009, not an event that needs watching in real time.