The Bitcoin halving is a protocol-level event that cuts the new-bitcoin reward paid to miners in half every 210,000 blocks, which works out to roughly every four years. The most recent halving happened on April 19, 2024, at block height 840,000, when the block subsidy fell from 6.25 BTC to 3.125 BTC. The next halving is projected for block 1,050,000, currently estimated to arrive somewhere between March and April 2028, when the subsidy will fall again to 1.5625 BTC. This mechanism is the engine that enforces Bitcoin's 21-million supply cap.
As of April 27, 2026, the current block height is 946,816 (source: Mempool.space), which puts the network about 103,000 blocks away from the next halving. The block subsidy at that tip is 3.125 BTC, confirmed by any Bitcoin node or block explorer you can point at mempool.space/block/840000. Total circulating supply is now a shade above 20 million BTC, or roughly 95.2% of the eventual 21 million cap. The halving is not a calendar event, and no line of Bitcoin's source code specifies a date. The date is emergent, derived from whatever average block time the network is running at the moment you ask.
This guide is written for readers who already know that Bitcoin is a digital asset with a fixed supply and want to understand the machinery that enforces the cap. It assumes you have read what is bitcoin and are comfortable with the idea that bitcoin mining is the process that creates new coins. If you are brand new, those two are better starting points than this one.
What you will learn:
What the halving actually is at the protocol level, not just what it sounds like
Why it happens every 210,000 blocks, and why that is not the same as "every four years"
The full history of the four past halvings and what each one changed
How to verify the current subsidy and project the next halving date from your own node or mempool.space
Why date estimates across trackers disagree by up to four weeks
What the halving does to miner economics, difficulty, and the network
Why the subsidy-to-fee transition is the bigger story that halving coverage usually misses
The operator view: what happens inside an exchange on halving day
Every figure, block height, and date in this article is sourced to the Bitcoin protocol itself or to a Tier-1 primary source, and date-stamped April 27, 2026.
What the halving actually is
At the code level, Bitcoin's consensus rules include a function that calculates the block subsidy (the newly minted BTC paid to whichever miner produces the current block). That function is deterministic: subsidy starts at 50 BTC per block at block 0, halves at block 210,000, halves again at 420,000, and so on, at every integer multiple of 210,000 until the subsidy rounds down to zero around block 6,930,000. Any node running the reference implementation or a compatible client will reject a block whose coinbase transaction pays a higher subsidy than the schedule allows.
Three things follow from this design:
The halving is automatic. No person, company, foundation, or committee triggers it. The schedule is baked into the consensus rules. Any node that wanted to pay miners more would fork itself off the network, because every other node would reject the block.
The halving is exact. There is no "around 210,000 blocks." The moment a miner seals block 210,000, 420,000, 630,000, 840,000, or 1,050,000, the subsidy for the NEXT block drops. The halving is a step function, not a ramp.
The halving is date-agnostic. Nothing in the code says "April 19, 2024." The date is whatever wall-clock time the network happens to reach that block at. A burst of new hashrate can pull the date forward by days; a major mining region losing power can push it back.
This is the single most important mental shift when reading halving coverage. The calendar dates you see everywhere are observations, not targets.
Why 210,000 blocks, and the 10-minute target
Satoshi Nakamoto chose 210,000 blocks for an elegant reason. At Bitcoin's target block time of 10 minutes, 210,000 blocks equals 2,100,000 minutes, which is 35,000 hours, which is about 3.99 years. The halving interval was calibrated to produce roughly one halving every four years while being expressible as a clean integer multiple inside the consensus rules. The four-year cadence is a consequence of the math, not the cause of it.
The 10-minute target is itself enforced by Bitcoin's difficulty adjustment, which recalibrates every 2,016 blocks (roughly every two weeks). If the network is producing blocks faster than 10 minutes (because hashrate grew), difficulty rises at the next adjustment; if slower, it falls. The feedback loop keeps the long-run average near 10 minutes but leaves room for short-run variance.
In practice, blocks have averaged slightly under 10 minutes since 2012, because global hashrate has grown faster than the difficulty retargeting can fully absorb between resets. The result is that every halving has arrived modestly earlier than the naive "four years from the last one" projection. Block 840,000 arrived on April 19, 2024, not roughly one month later as a strict ten-minute-block model would have implied from block 630,000 on May 11, 2020.
The halving schedule in one table
Halving # | Block height | Date | Subsidy before | Subsidy after | Annual issuance cut |
|---|---|---|---|---|---|
Genesis | 0 | 2009-01-03 | n/a | 50 BTC | Initial issuance ~2,628,000 BTC/year |
1 | 210,000 | 2012-11-28 | 50 BTC | 25 BTC | ~1,314,000 BTC/year |
2 | 420,000 | 2016-07-09 | 25 BTC | 12.5 BTC | ~657,000 BTC/year |
3 | 630,000 | 2020-05-11 | 12.5 BTC | 6.25 BTC | ~328,500 BTC/year |
4 | 840,000 | 2024-04-19 | 6.25 BTC | 3.125 BTC | ~164,250 BTC/year |
5 (next) | 1,050,000 | 2028 (est.) | 3.125 BTC | 1.5625 BTC | ~82,125 BTC/year |
33 (last) | ~6,930,000 | ~2140 | tiny | 0 | 0 BTC/year |
Annual issuance numbers assume a constant 10-minute block time (52,560 blocks per year). Actual issuance is modestly higher when blocks run fast. These figures are triangulated from CoinGecko's halving page (source: CoinGecko), Kraken's halving history (source: Kraken), Trezor's learn tables (source: Trezor), and direct verification against any Bitcoin Core node.
The four halvings that have already happened
Halving 1: November 28, 2012 (block 210,000)
The first halving cut the subsidy from 50 BTC to 25 BTC. At the time, Bitcoin traded at about $12 and total network hashrate was measured in the low terahashes per second. The halving was largely a protocol-community event; mainstream financial press did not cover it. The significance was that the code did what the code said it would do. One line in Satoshi's original release became a live, observed, irreversible moment. After this, the halving mechanism had empirical credibility, not just theoretical credibility.
Halving 2: July 9, 2016 (block 420,000)
The second halving cut the subsidy from 25 BTC to 12.5 BTC. Bitcoin traded near $650 at the event. This halving arrived during the early build-out of the ASIC-mining industry and was the first to receive broad coverage from crypto-native media. A short-term post-halving drawdown of roughly 40% in BTC price was followed by the 2017 bull cycle that took BTC from about $1,000 in January 2017 to near $20,000 by December 2017.
Halving 3: May 11, 2020 (block 630,000)
The third halving cut the subsidy from 12.5 BTC to 6.25 BTC during the first weeks of the global COVID-19 response. Bitcoin traded near $8,800 at the event. The halving coincided with a period of unprecedented central-bank balance sheet expansion and became the hinge point for the narrative that positioned Bitcoin as a hedge against monetary debasement. The subsequent cycle carried BTC to an all-time high near $69,000 in November 2021.
Halving 4: April 19, 2024 (block 840,000)
The fourth halving cut the subsidy from 6.25 BTC to 3.125 BTC. Bitcoin traded around $63,800 at the event. This was the first halving to occur after US spot Bitcoin ETFs launched in January 2024, which Grayscale Research framed in its "2024 Halving: This Time It's Actually Different" report (source: Research) as a structural demand shift. Where prior cycles relied on retail flows plus institutional whispers, the 2024 halving saw regulated US vehicles absorbing hundreds of millions of dollars of BTC a day, multiple times the daily post-halving issuance.
The subsidy-to-fee transition (the bigger story)
Most halving coverage stops at the block-reward change and moves on. That misses the larger arc.
Every halving cuts new issuance in half. By 2028, annual issuance will be about 82,125 BTC. By 2032, about 41,000. By 2036, about 20,500. The pattern continues until roughly 2140, when the subsidy rounds to zero. At some point long before 2140, the subsidy stops being the dominant driver of miner revenue, and transaction fees take over.
Consider the arithmetic. At the current 3.125 BTC subsidy and a spot price around $100,000, a new block pays about $312,500 in subsidy. Average transaction fees on a busy day run in the range of 0.1 to 0.3 BTC per block, or $10,000 to $30,000. Subsidy dominates. At the 2028 halving, with a 1.5625 BTC subsidy (~$156,000 at current prices), fees would represent roughly 6-16% of total miner revenue on a busy day. By the 2032 halving (~0.78 BTC subsidy, ~$78,000), the fee share climbs into the 15-30% range at today's fee rates. And this assumes BTC price stays flat, which is precisely the assumption that halving-era BTC tends to violate.
The implication: a durable fee market is not optional for Bitcoin's long-term security. Either transaction fees scale up materially (because block space gets scarcer relative to demand), or BTC denominated security payments scale up (because BTC price rises fast enough to compensate for subsidy cuts), or some combination. The halving is the slow reveal of which scenario is happening.
For the mechanics of why fees move around and what drives their long-run level, see why are bitcoin fees so high. For the supply-cap framing that makes all of this matter, see bitcoin 21 million supply cap.
Why no two trackers agree on the 2028 date
Look up "next bitcoin halving date" on five different sites today and you will see estimates ranging from March 26, 2028, to April 20, 2028. That is a four-week spread for an event that the protocol specifies to the exact block. The spread is not an error; it is the right answer, because the question itself is imprecise.
Here is why. The only fixed input is block height 1,050,000. The date depends entirely on the average block interval from block 946,816 (today's tip) forward. Trackers choose different block-interval assumptions:
Sites that use a pure 10-minute-per-block assumption project the latest dates (mid to late April 2028).
Sites that use the trailing 30-day or 90-day average block interval often land closer to late March or early April 2028, because recent hashrate growth has pushed average intervals modestly below 10 minutes.
Sites that use a 180-day or 1-year trailing window fall somewhere in between.
A sudden hashrate shock (a major mining region going offline, or an unusually warm summer cutting thermal headroom in Texas mining fleets) can push estimates out by a week or more within a day. A burst of new ASIC deployment from a public miner can pull them forward. Until block 1,050,000 actually confirms, every date you see is a model, not a fact.
Verify the projection yourself
You do not need to take anyone's word for it. The recipe is:
1. Fetch the current tip height: curl -s https://mempool.space/api/blocks/tip/height (or any Bitcoin node's getblockcount)
2. Subtract from 1,050,000. That is how many blocks remain.
3. Divide by your preferred blocks-per-day assumption. 144 blocks per day is the "ten-minute perfect" baseline. Recent actual averages have been 145-148 blocks per day, which is why projections keep drifting earlier.
4. Add that many days to today's date.
As of April 27, 2026 with tip at 946,816: 103,184 blocks remain; at 144 blocks/day, projected date is April 12, 2028; at 146 blocks/day, projected date is April 2, 2028; at 148 blocks/day, March 24, 2026. Different blocks-per-day assumption, different answer. All of them are current-state projections that will move as hashrate and difficulty evolve.
For the deeper mechanics that power this feedback loop, see bitcoin nodes vs miners vs wallets and how to buy bitcoin safely.
What the halving does to miners
The halving is the largest recurring shock in the Bitcoin mining industry. The same machine that earned 6.25 BTC per share of hashrate in the months before April 19, 2024, has earned 3.125 BTC per share ever since. For operators whose electricity and financing costs are fixed in fiat, a 50% drop in BTC-denominated revenue is existential unless offset by some combination of rising BTC price, falling network difficulty, or rising transaction fees.
In practice, the post-halving pattern has been consistent across all four events:
Immediate hashrate dip. The least-efficient machines (older generations with higher joules-per-terahash) go offline within days because they are now unprofitable. This was visible within two weeks of the 2024 halving.
Difficulty adjustment down. Because hashrate fell, blocks temporarily run slower than 10 minutes, and the next difficulty retarget adjusts downward. This partially restores profitability for surviving machines.
Gradual hashrate recovery. Over the following months, surviving operators reinvest, new ASIC generations ship, and total hashrate resumes its long-run uptrend. Bitcoin network hashrate posted a 104% year-over-year increase in 2024 according to Hashrate Index research.
Consolidation toward cheap-power operators. Each halving shakes out miners whose electricity cost sits above the new break-even. The result is a gradual concentration of hashrate at sites with sub-$0.04/kWh power, hedging programs, and access to modern hardware.
None of this is a market failure; it is the designed behaviour of the system. The subsidy cuts, the difficulty adjusts, the price does what it does, and the network keeps finding blocks roughly every ten minutes.
The operator-desk view
From an exchange operations perspective, a halving is not a dramatic event in the trading sense. The order book sees no trigger; users can withdraw and deposit as usual. The subsidy change is invisible to users: no wallet shows a different balance, no deposit address changes, no UI element updates. What actually changes during a halving week, from the inside of an exchange, is the fee-estimation endpoint recommending higher fee rates as the block-space market briefly tightens around the event, and the withdrawal queue growing by a factor of two or three in the hours on either side of the expected block as users move coins before and after "just to have been involved." The deposit-and-withdrawal team runs longer shifts, the engineering team tags every incoming confirmation against an independent node just to avoid a block-reorg surprise, and nothing catastrophic happens. The coverage on the TradFi news networks gets loud; the actual protocol does exactly what it did at blocks 210,000, 420,000, and 630,000.
What the halving does NOT do
Several myths routinely attach to the halving. Getting these wrong leads to poor risk decisions.
The halving does not double the BTC price overnight. The supply cut is to the flow of new BTC, not the stock of existing BTC. The stock of existing BTC is ~20.02 million; the halving affects the rate at which that number grows by about 0.8 percentage points of annual issuance. Any price move is about expectations, flows, and macro, not a direct supply-and-demand arithmetic.
The halving does not crash miner profitability for efficient operators. Operators at the efficiency frontier (sub-15 J/TH, sub-$0.04/kWh power) remain profitable through every halving; it is the marginal operator that shuts off, which is exactly the system's intended filter.
The halving is not a date announced by Bitcoin's developers. The date is emergent; developers have no more knowledge of the exact date than a retail trader does, beyond being better at modelling hashrate trends.
The halving is not "every four years." It is every 210,000 blocks. Four years is a consequence of a 10-minute target, not the specification.
The halving cannot be cancelled or delayed by governance. Changing the halving schedule would require impossible coordination among 100% of economic nodes (not just miners). Any faction attempting to skip a halving would fork itself off the network.
Halving and holder behaviour
If you hold BTC through a halving, nothing about your holdings changes. Your balance is identical to the block before and the block after. Your wallet addresses are unchanged. The only thing that changed is how much new BTC is being paid into circulation per block, which is a concern of miners and the long-run supply curve, not of your spendable balance.
If you are considering buying or selling around a halving, the historical record suggests (without guaranteeing) that:
Short-term price action in the weeks immediately around a halving has been noisy and often slightly negative.
Twelve to eighteen months after a halving, historically, Bitcoin has reached a new cycle high. This is a pattern, not a rule; the 2024 cycle featured a pre-halving run-up to all-time highs that broke the prior sequencing. For how traders classify and adapt to these phases, see crypto market cycles for traders.
Halvings arrive pre-priced in the sense that markets have always known the date range for years in advance. Anyone who tells you the halving is a "catalyst" is conflating a scheduled protocol event with a surprise.
Good rules of thumb are to not trade on the halving as a dramatic event, to not extrapolate past cycle tops mechanically, and to use the halving as a reminder to review your own basis, your bitcoin security checklist, and whether your long-run plan still makes sense. For more on the accumulation decision, see DCA vs lump sum.
Halving FAQ
What is Bitcoin halving in one sentence?
A protocol-mandated event that cuts the per-block subsidy paid to miners in half every 210,000 blocks, roughly every four years, until the subsidy rounds to zero around block 6,930,000 in approximately 2140.
When did the last halving happen?
April 19, 2024, at block 840,000. The subsidy dropped from 6.25 BTC to 3.125 BTC.
When is the next halving?
At block 1,050,000. Date projections as of April 27, 2026 range from late March to mid-April 2028, depending on which average block time the tracker assumes. A reasonable mid-estimate is early April 2028.
Can developers change the halving schedule?
In principle, a change would require a consensus rule modification that 100% of economic nodes accepted. In practice, coordination on anything that altered the 21 million cap or the halving schedule has been considered politically impossible by the Bitcoin community since 2013. Any attempt would produce a network fork with the changers on a minority chain.
What happens when the subsidy reaches zero?
Miners will be compensated entirely by transaction fees. The exact timing of the transition depends on fee-market evolution over the next century; see the "subsidy-to-fee transition" section above.
Does halving reduce the total supply of Bitcoin?
No. The halving reduces the rate at which new bitcoin is issued. Total eventual supply remains capped at 21 million (slightly less than 21 million in practice due to rounding in the subsidy schedule and some genuinely lost coins).
Does halving cause the Bitcoin price to go up?
Not directly and not immediately. The halving reduces new-issuance flow but does not alter the existing stock. Historically, bull cycles have followed each halving within 12-18 months, but the relationship is correlational and overdetermined; spot ETF flows, macro conditions, and institutional adoption all play major roles.
How can I verify the current block subsidy myself?
Query any Bitcoin node or a block explorer. Block 840,001 onward shows a coinbase output of 3.125 BTC plus transaction fees. Example: visit https://mempool.space/block/840000 and then https://mempool.space/block/840001 and inspect the coinbase transaction reward.
How many halvings will there be in total?
33. After halving 33, the subsidy rounds to zero in integer satoshis.
What is the 21 million supply cap?
The maximum number of bitcoins that will ever exist. It is an asymptote derived from summing the halved subsidies across 33 epochs. For the framing that ties this to Bitcoin's monetary design, see what does bitcoin solve.
Is halving a hard fork?
No. The halving is a scheduled behaviour of the existing consensus rules. All nodes running any recent Bitcoin implementation apply the subsidy change automatically at the scheduled block height without any software update.
What is the difference between the halving and the difficulty adjustment?
The halving is a one-event-every-210,000-blocks cut to the block subsidy. The difficulty adjustment is a one-event-every-2,016-blocks recalibration of how hard it is to find a valid block, designed to keep the average block time near 10 minutes. They interact but are separate mechanisms. For the protocol framing, see bitcoin blockchain.
Will the halving make Bitcoin deflationary?
Bitcoin is already disinflationary (issuance rate is falling). After the 2024 halving, annual issuance is about 0.83% of supply; after 2028 it will be around 0.41%. Strictly deflationary (total supply falling) only happens at scale when realised lost coins plus burned coins exceed new issuance, which is plausibly already happening on some tight accounting definitions.
Glossary
Block subsidy: the newly minted BTC paid to the miner who produced the current block. Distinct from transaction fees. Subject to halving.
Coinbase transaction: the first transaction in every block, which creates the block subsidy plus collected transaction fees and pays them to the miner.
Difficulty adjustment: a recalibration of the target hash threshold every 2,016 blocks, designed to keep the average block interval near 10 minutes.
Halving epoch: the ~210,000-block period between successive halvings, during which the subsidy is constant.
Hashrate: the total computational power of the Bitcoin network, typically measured in exahashes per second (EH/s).
Issuance: the rate at which new BTC enters circulation through coinbase transactions. Halved at each halving.
Stock-to-flow: the ratio of existing supply (stock) to annual new issuance (flow). Each halving doubles Bitcoin's stock-to-flow.
Supply cap: 21 million BTC, the asymptotic limit of total issuance.
Key takeaways
The Bitcoin halving is a protocol-automated event that halves the block subsidy every 210,000 blocks, enforcing the 21 million supply cap
Four halvings have happened already: 2012, 2016, 2020, and 2024; the current subsidy is 3.125 BTC per block
The next halving, at block 1,050,000, is projected for early-to-mid 2028; exact date depends on hashrate evolution and cannot be specified in advance
Historical post-halving cycles have included significant BTC price appreciation within 12-18 months, but the pattern is overdetermined and not a guarantee
Miner economics are the front line of each halving: efficient operators survive, marginal operators shut down, network hashrate briefly dips, difficulty adjusts, and the long-run uptrend resumes
The subsidy-to-fee transition is the larger story: by 2140 all revenue will come from transaction fees, and the halvings are the slow reveal of that handoff
The halving is a protocol milestone, not a trading catalyst; anyone treating the date as a surprise is misunderstanding how Bitcoin works
You can verify every fact in this article against any Bitcoin node or mempool.space without trusting any third party
From an exchange operations perspective, every halving looks the same from the inside: fee-estimate endpoints briefly elevate, a short queue builds in the hours around the event block, engineering runs extra confirmation checks against independent nodes, and then operations proceed exactly as before. The protocol does what the protocol has always done. The coverage gets dramatic; the code is calm. Readers who take one idea away from this article should take this one: the halving is a known, scheduled, transparent event whose significance comes from compounding over decades, not from any single date's price action.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Factual claims independently verified against the Bitcoin Core source at github.com/bitcoin/bitcoin, CoinGecko halving data at coingecko.com/en/coins/bitcoin/bitcoin-halving, Kraken Learn at kraken.com/learn/bitcoin-halving-history, Trezor Learn at trezor.io/learn/supported-assets/bitcoin/bitcoin-halving-explained, Swan Bitcoin at swanbitcoin.com/education/bitcoin-halving-dates, Grayscale 2024 halving research at research.grayscale.com/reports/2024-halving-this-time-its-actually-different, and live block-tip data from mempool.space/api/blocks/tip/height. Live-figure date-stamp: April 27, 2026, tip height 946,816.
Disclaimer: This content is for educational purposes only and does not constitute financial, investment, legal, or tax advice. Crypto assets are highly volatile and carry significant risk of loss. Always verify local regulations and consult a qualified professional before making financial decisions.
