21Relay
Advanced curriculum
Lesson 1120 minReviewed July 2026

Mining Incentives and the Security Budget

Evaluate how Bitcoin pays miners as issuance declines, what the security-budget debate can and cannot establish, and why outcomes depend on demand rather than a guaranteed formula.

Learning outcomes

By the end of this lesson, you should be able to

  • The block reward combines subsidy and transaction fees.
  • The subsidy is small after 2040 but reaches zero only around 2140 under current rules.
  • Fee revenue depends on demand for block space.
  • Difficulty adjustment maintains block cadence, not a fixed economic security level.
1

The block reward has two components

A valid coinbase transaction may claim the block subsidy permitted at that height plus transaction fees from the block's transactions. The subsidy creates new bitcoin; fees transfer existing bitcoin from users to the miner.

The subsidy halves every 210,000 blocks. Around 2040 it will be much smaller than today, but not literally zero. Under the current schedule, subsidy issuance finally becomes zero around 2140 after repeated integer halvings.

2

Security budget is miner revenue, not a protocol constant

The term security budget usually refers to the value paid to miners over a period. Its purchasing power depends on subsidy, fees and bitcoin's market value, while the security actually purchased depends on energy, hardware, operating costs and mining competition.

Bitcoin does not specify a required dollar security budget or hashrate. Difficulty adjusts to observed block production, so the network can continue producing blocks across different hashrate levels while the economic cost of attack changes.

3

Fees are expected to matter more

The white paper anticipated that once enough coins had entered circulation, miner incentives could transition entirely to transaction fees. Fee revenue comes from demand for scarce block space, not from a guaranteed minimum payment.

Higher-value settlement, batching, Lightning channel operations and other uses can generate demand for block inclusion. Efficiency improvements can reduce bytes per activity, so transaction count alone is not a sufficient forecast of future fees.

4

A fee market has trade-offs

If fee revenue is low relative to attack opportunities, miners may deploy less hashpower. If block-space demand is strong, fees can support more mining even as subsidy declines.

Highly variable fees can also affect miner cash flow and user experience. Mining pools, out-of-band payments and concentration in block-template construction introduce additional incentive and censorship questions.

5

Why the answer remains uncertain

No one can know future bitcoin price, transaction demand, energy costs, mining hardware efficiency, layer-two usage or attack incentives decades in advance. Claims that fees will certainly be sufficient—or certainly fail—go beyond available evidence.

The useful approach is to monitor subsidy share, fee share, hashrate distribution, template decentralisation, block-space demand and reorganisation incentives while keeping protocol changes open to rigorous review.

Visual recap

From user demand to proof-of-work security

The protocol defines rewards and difficulty; markets determine their economic value and the resources miners deploy.

01

Block-space demand

02

Transaction fees

03

Subsidy plus fees

04

Miner revenue

05

Hashpower deployed

06

Difficulty adjusts

Key vocabulary

Terms worth knowing

Block subsidy
New bitcoin a valid block may create under the issuance schedule.
Fee revenue
Transaction fees claimed by the miner of a valid block.
Security budget
An analytical term for miner compensation supporting proof-of-work expenditure; it is not a protocol field or guaranteed amount.

Worked example

Subsidy falls while fee demand changes

After a halving, subsidy revenue per block is lower. The effect on hashrate depends on bitcoin price, transaction fees, hardware efficiency, energy costs and miner financing.

  1. 1Calculate subsidy and fee revenue in BTC
  2. 2Translate revenue using market price while noting volatility
  3. 3Compare with operating and capital costs
  4. 4Allow difficulty to adjust after hashrate changes
  5. 5Assess attack cost and miner concentration separately

Long-term security cannot be inferred from subsidy alone. Multiple market variables interact, and future outcomes remain uncertain.

Common misconceptions

What learners often get wrong

Misconception

Mining ends when the last bitcoin is issued.

More accurate

The subsidy approaches zero, but valid blocks can still include transaction fees; the adequacy of future incentives is an open economic question.

Misconception

A lower hash rate automatically means Bitcoin is insecure.

More accurate

Security is contextual and relates to attack goals, costs, decentralisation, confirmation policy and the value being protected.

Try it yourself

Build a qualitative post-halving model.

  • Change subsidy revenue
  • Vary fee revenue and bitcoin price
  • Vary energy and hardware cost
  • Predict short-term hashrate response
  • Explain how difficulty adjustment changes the next period

Use fictional values and public information only. Never enter seed words, private keys or other wallet secrets into a learning exercise.

Key takeaways

  • The block reward combines subsidy and transaction fees.
  • The subsidy is small after 2040 but reaches zero only around 2140 under current rules.
  • Fee revenue depends on demand for block space.
  • Difficulty adjustment maintains block cadence, not a fixed economic security level.
  • Long-term security outcomes are debated and cannot be guaranteed decades ahead.

Lesson recap

Check what you learned

Reveal each model answer, then honestly mark whether you understood it or need another review.

1 of 3

Recall

Does Bitcoin's difficulty adjustment guarantee a constant economic cost to attack the network?

References

Further reading

Lesson progress

Loading progress...

Rate this lesson

Was this lesson helpful?

No name or financial information is collected.

Found inaccurate or outdated information? Report a correction