Candleread
Crypto and DeFi · Bitcoin and the Macro Context

The halving cycle, every ~4 years

Explain how Bitcoin's block reward halves roughly every four years and why that matters for supply.

3 min read+25 XPLesson 12 of 79
Start reading

Lesson path

Crypto and DeFi

Bitcoin and the Macro Context

Lesson 12 of 7915%
Lesson 12 of 79Crypto and DeFiBitcoin and the Macro Context

Today's tiny win: make one idea click.

Explain how Bitcoin's block reward halves roughly every four years and why that matters for supply.

Learn itSpot itPass the check

Supply on a schedule

Bitcoin's supply does not enter the market in one big release. It drips in, block by block, at a rate fixed by code. Every 210,000 blocks — which works out to roughly every four years at the network's ten-minute target block time — the reward paid to miners gets cut exactly in half. This is called the halving, and it is the single most important supply-side event in Bitcoin's economic design. The exact date of each halving is not chosen by a person or a committee. It is a function of how fast miners produce blocks. So while we estimate four years, the actual interval has been a few months longer or shorter depending on hash rate growth.

Why was this designed? Bitcoin's creator wanted the issuance to feel like a mined commodity. Gold gets harder to extract over time, and Bitcoin mirrors that by mathematically reducing the new-supply rate. The block reward started at 50 BTC in 2009. After the first halving it dropped to 25, then 12.5, then 6.25, and after the April 2024 halving it sits at 3.125 BTC per block. By around 2140, the last fractional satoshi will be mined and issuance ends.

Wick checks a calculator showing 450 a day because the April 2024 halving cut about 900 new BTC a day in half, showing how new supply shrinks overnight.900 new BTC a day / 2 =about 450450/day
Wick saysAfter the 2024 halving, new Bitcoin per day dropped from about 900 to about 450.

For a trader, the halving matters for two practical reasons. First, it cuts the daily issuance roughly in half overnight. Before the April 2024 halving, miners were producing about 900 new BTC per day. After the halving, that dropped to about 450. If demand stays steady, that mathematical reduction in new supply is a meaningful squeeze on the order book. Second, the halving compresses miner profit margins immediately. Less efficient mining operations are forced offline, and surviving miners often sell less aggressively to preserve treasury — which can reduce structural sell pressure in the months following the event. Combined, these forces shift the supply-demand balance in a direction that has historically favored higher prices, even though that outcome is never guaranteed.

Wick watches a balance scale where steady demand outweighs new supply that was cut in half, showing why the halving can squeeze the order book.NewsupplyCut in halfDemandIf it stays steady?
Wick saysIf demand stays steady while new supply is cut in half, the balance can tilt toward buyers.

A word of honesty: the halving's effect on price is not a guarantee. It is one variable in a much bigger machine that includes macro conditions, regulation, and ETF flows. The next few lessons walk through the actual history so you can decide for yourself what the pattern shows.

Wick calmly thinks that the halving is one clue, not a promise, showing that macro, rules and ETF flows matter too and no price result is certain.The halving is oneclue, not a promise.?
Wick saysThe halving is one piece of a big machine, and its effect on price is never a sure thing.

Recap: every ~4 years, Bitcoin's block reward halves. Daily new supply drops by half overnight. Supply discipline is mathematical, not discretionary.

Knowledge check

Answer before moving on.

0 / 3 answered

1. How often does a Bitcoin halving occur?

2. After the April 2024 halving, the block reward dropped from 6.25 to what?

3. Why does the halving matter for traders?

Lesson handoff

Pass the check before saving.

Use the knowledge check first. After you pass it, this card turns into the save-and-continue handoff.