How Bitcoin Halving Works

Bitcoin halving cuts the block reward in half every 210,000 blocks. Here's how the mechanism works, what it means for miners, and why the fee market matters long-term.
Lewis Jackson
CEO and Founder

There's a version of this topic that's mostly about price. "Halvings are bullish," the argument goes, and people treat the four-year event like a scheduled catalyst. That framing isn't wrong exactly — supply reduction with constant or growing demand is a real dynamic — but it's downstream of a mechanism most explanations never actually walk through.

The halving is a supply-issuance rule embedded in Bitcoin's code. Understanding it means understanding how Bitcoin controls inflation, compensates miners, and approaches its fixed cap. The price conversation, if it's worth having, comes after the mechanism.

How the Reward Structure Works

When a miner successfully adds a block to the Bitcoin blockchain, they receive a block reward — newly created bitcoin paid directly to their address. That reward started at 50 BTC per block in 2009. Every 210,000 blocks (roughly four years at the 10-minute average block time), the reward is cut in half. That's the halving.

The schedule so far:

  • Blocks 0–209,999: 50 BTC
  • Blocks 210,000–419,999: 25 BTC
  • Blocks 420,000–629,999: 12.5 BTC
  • Blocks 630,000–839,999: 6.25 BTC
  • Blocks 840,000–1,049,999: 3.125 BTC (current, post-April 2024)

This continues until the reward reaches zero — around the year 2140. By then, roughly 21 million bitcoin will have been issued. The number isn't arbitrary; it's the result of summing a geometric series: 50 BTC × 210,000 blocks × (1 + 0.5 + 0.25 + ...) ≈ 21,000,000. Bitcoin's total supply is fixed by the issuance schedule itself, not a central bank and not a governance vote.

There's a second revenue stream that becomes more important over time: transaction fees. Every transaction included in a block pays a fee to the miner who includes it. Right now fees are supplementary. Once enough halvings reduce the subsidy substantially, fees become the primary compensation. Bitcoin's long-run security model depends on fees eventually replacing subsidies — that's an active debate, not a settled answer.

The Miner Economics Problem

The halving creates a straightforward revenue squeeze: income just got cut in half while costs — hardware, electricity, hosting — didn't. What happens next depends on the relationship between bitcoin's market price and miners' operating break-even.

If price rises proportionally or more, miners are fine. If it doesn't, some share of the network becomes unprofitable and shuts down. When hash rate drops, Bitcoin's difficulty adjustment compensates automatically — every 2,016 blocks (~two weeks), the network recalibrates mining difficulty to keep average block times near 10 minutes. Lower hash rate → lower difficulty → remaining miners find blocks more easily → economics stabilize for whoever survived.

This is a real feedback loop, not a safety guarantee for any specific miner. Marginal operators with high electricity costs or aging hardware exit first. Halvings have historically accelerated consolidation toward larger, more capital-efficient mining operations. That's not necessarily a problem for the network, but it's worth being clear about: the mechanism protects the protocol, not individual participants.

Where the Constraint Lives

The deeper structural tension is what's sometimes called the security budget problem. Bitcoin's resistance to attack comes from hash rate. Hash rate is expensive to accumulate — miners need revenue to cover costs. If miner revenue falls too far, hash rate declines, and the network becomes relatively easier to attack.

This isn't an imminent concern. Post-2024 halving, transaction fee income has grown more meaningful than it was in earlier cycles, and the block reward at current prices still funds a substantial global mining industry. But the math gets harder with each successive event. By 2032, the subsidy will be approximately 0.78 BTC per block. Whether that's economically sufficient depends almost entirely on the fee market — and the fee market depends on Bitcoin's transaction volume, block space competition, and utility relative to alternatives.

No one knows with certainty how this develops. The mechanism is well-understood. The long-run equilibrium is not.

What's Changing

A few structural shifts around halvings matter more than the event headline itself.

Transaction fee income relative to subsidy grew significantly in 2023–2024, driven partly by ordinals and BRC-20 inscription activity adding block space competition. Whether that level of fee activity persists or normalizes is unclear — ordinals usage has been variable and the inscriptions market is early-stage.

More durably: as subsidies decline, fee-inclusive miner compensation models become structurally more important. Mining pools using FPPS (Full Pay Per Share) already distribute fee income as part of payouts — that distinction, relatively minor when subsidies were large, becomes more consequential as the ratio shifts.

Layer 2 usage on Lightning Network adds another variable. Lightning could complement on-chain fee income (via channel opens and closes creating base-layer transactions) or reduce it (if most payment volume migrates off-chain without compensating activity). That dynamic is genuinely unresolved.

Confirmation Signals

  • Fee revenue per block consistently representing 25–30%+ of miner income in the 2024–2028 cycle
  • Hash rate returning to pre-halving levels within two to three months post-event, indicating miner economic survivability
  • Large mining operators publicly disclosing break-even economics that remain viable at 3.125 BTC subsidy levels

Invalidation Signals

  • Hash rate sustained 30%+ decline post-halving without recovery, suggesting a security budget failure rather than normal cycle volatility
  • Fee income declining toward near-zero as Lightning absorbs payment volume without generating compensating base-layer activity
  • Major miner insolvencies specifically attributed to post-halving revenue collapse, as distinct from broader market cycle timing

Timing Perspective

Now: The 2024 halving (block 840,000, April 19, 2024) is complete. The network operates at a 3.125 BTC reward. Miner economics at current price levels are generally viable, though tighter than the 2020–2022 cycle. Fee income variability is the active variable.

Next: The 2028 halving (~1.5625 BTC) is where the security budget debate sharpens meaningfully. Fee markets need to demonstrate durability before then for the long-run model to remain credible without structural changes.

Later: Sub-1 BTC subsidies, approaching 2032 and beyond, represent the theoretical concern most acute for the fee-market transition. Far enough out to understand rather than fixate on.

Boundary Statement

This covers the halving mechanism: what it is, how it interacts with miner economics, and why the transition from subsidy to fee income matters structurally. It doesn't constitute a view on price, nor does it address mining investment decisions or tax treatment in any jurisdiction.

The mechanism works as described. What it implies for any particular cycle depends on variables outside this scope.

Related Posts

See All
Crypto Research
New XRP-Focused Research Defining the “Velocity Threshold” for Global Settlement and Liquidity
A lot of people looking at my recent research have asked the same question: “Surely Ripple already understands all of this. So what does that mean for XRP?” That question is completely valid — and it turns out it’s the right question to ask. This research breaks down why XRP is unlikely to be the internal settlement asset of CBDC shared ledgers or unified bank platforms, and why that doesn’t mean XRP is irrelevant. Instead, it explains where XRP realistically fits in the system banks are actually building: at the seams, where different rulebooks, platforms, and networks still need to connect. Using liquidity math, system design, and real-world settlement mechanics, this piece explains: why most value settles inside venues, not through bridges why XRP’s role is narrower but more precise than most narratives suggest how velocity (refresh interval) determines whether XRP creates scarcity or just throughput and why Ripple’s strategy makes more sense once you stop assuming XRP must be “the core of everything” This isn’t a bullish or bearish take — it’s a structural one. If you want to understand XRP beyond hype and price targets, this is the question you need to grapple with.
Read Now
Crypto Research
The Jackson Liquidity Framework - Announcement
Lewis Jackson Ventures announces the release of the Jackson Liquidity Framework — the first quantitative, regulator-aligned model for liquidity sizing in AMM-based settlement systems, CBDC corridors, and tokenised financial infrastructures. Developed using advanced stochastic simulations and grounded in Basel III and PFMI principles, the framework provides a missing methodology for determining how much liquidity prefunded AMM pools actually require under real-world flow conditions.
Read Now
Crypto Research
Banks, Stablecoins, and Tokenized Assets
In Episode 011 of The Macro, crypto analyst Lewis Jackson unpacks a pivotal week in global finance — one marked by record growth in tokenized assets, expanding stablecoin adoption across emerging markets, and major institutions deepening their blockchain commitments. This research brief summarises Jackson’s key findings, from tokenized deposits to institutional RWA chains and AI-driven compliance, and explains how these developments signal a maturing, multi-rail settlement architecture spanning Ethereum, XRPL, stablecoin networks, and new interoperability layers.Taken together, this episode marks a structural shift toward programmable finance, instant settlement, and tokenized real-world assets at global scale.
Read Now

Related Posts

See All
No items found.
Lewsletter

Weekly notes on what I’m seeing

A personal letter I send straight to your inbox —reflections on crypto, wealth, time and life.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.