RoadmapsProjects
Sign in./start

Learn

RoadmapsProjects

Contribute

DiscoverIssues

Account

Sign in./start-building

Become an Open Source Builder. Learn. Build. Contribute.

Learn

RoadmapsProjectsStart Building

Contribute

DiscoverIssues

Account

Sign inDashboardSettings

Legal

PrivacyTerms

© 2026 Pull // all rights reserved

PrivacyTerms

lesson // bitcoin

Bitcoin Economics

Supply schedule, fee markets, mining incentives, and security assumptions.

beginner4 days

Public lesson — sign in to track progress on this roadmap.

./sign-in

On this page

Learning objectives

  • Explain the fixed supply schedule and halvings
  • Describe how fees bid for limited block space
  • Connect miner incentives to network security

study // plan

Lessons are primers. Depth comes from required reading, interactive labs, reflection, and a hands-on check with evidence — the BOSS study pattern.

Research on Bitcoin Search

Required reading

  • bookMastering Bitcoin

    Ch. 1: Introduction

Reflection prompts

  1. Explain Bitcoin Economics to a teammate without jargon — what problem does it solve?
  2. What would break in production if you misunderstood Bitcoin Economics?
  3. Which BIP, book chapter, or Core doc is authoritative here, and what did you verify?

Lab // Regtest check

After reading, run one hands-on check related to Bitcoin Economics. Prefer local regtest or Polar over mainnet.

evidence required

  • ·Command output or screenshot from your local lab
  • ·One sentence on what you observed vs expected
  • ·Link to the required reading section you used

Bitcoin is software and an incentive system. If you only memorize data structures, you will still be surprised when fees spike, blocks fill, or miners orphan a chain tip. Economics explains the behavior.

Why this matters

Builders ship wallets, fee estimators, and Lightning nodes. All of them live inside a fee market and a security budget. Ignoring incentives leads to stuck transactions and brittle products.

Analogy

Block space is like seats on a fixed-size bus that leaves every ~10 minutes. When demand is high, people bid higher fares (fees). Miners are drivers paid by the fare box plus a scheduled subsidy that halves over time.

Supply schedule

New bitcoin enters circulation through the block subsidy. Approximately every 210,000 blocks (~4 years), the subsidy halves. Eventually the subsidy trends toward zero and security relies more on fees.

Loading diagram…

Users bid for inclusion; miners earn subsidy and fees; hashpower secures the ledger.

Fee markets

A transaction pays a fee equal to inputs minus outputs. Wallets express urgency as sat/vB (satoshis per virtual byte). Higher fees usually confirm faster when the mempool is congested.

further reading

  • bookMastering Bitcoin

    Ch. 2: Overview

  • articleBitcoin Optech: Transaction fees

progress // sign in

Reading is public. Sign in to mark lessons complete, sync across devices, and unlock your roadmap.

./sign-in-to-track
prevCryptography PrimernextUTXO Model

On this page

Press Shift + ? for keyboard shortcuts.

Press R to research on Bitcoin Search.

const feeSats = inputSumSats - outputSumSats; const satPerVb = feeSats / virtualSize;

Security assumption

Bitcoin’s security assumes that attacking the chain (for example, rewriting recent history) costs more than it is worth, primarily because honest mining is rewarded and hashpower is expensive. Fees and subsidy fund that hashpower.

What builders should design for

  • Fee spikes: always support fee bumping (RBF/CPFP) for on-chain sends
  • Dust and uneconomical UTXOs: tiny outputs can cost more to spend than they are worth
  • Confirmation targets: “next block” vs “within a day” are different products

Common mistakes

  • Hard-coding a fee like “10 sat/vB forever”
  • Treating the 21 million cap as a UX detail instead of a consensus rule
  • Assuming Lightning removes the need to understand fees, channels still open/close on-chain

Worked mental model

Re-read the diagrams in this lesson once out loud in plain language. If you cannot explain the flow to a friend without jargon, pause and revisit Mastering Bitcoin / Mastering Lightning chapters linked in Resources. Chapter references are intentional, not decorative.

Hands-on habit

Every protocol idea should be paired with one local experiment:

  1. Reproduce the happy path on regtest (or Polar for Lightning)
  2. Break it on purpose (wrong fee, expired invoice, offline peer)
  3. Write down what error you saw and which layer produced it (wallet, node, mempool, peer)

That habit turns reading into builder instinct.

Glossary check

Pick three terms from this lesson and define them in one sentence each without opening notes. Weak definitions mean the lesson is not finished yet.

Resource order

Use Resources in order: narrative book chapter first, then BIP/BOLT for precision, then implementation docs for commands. Jumping straight to RPC flags without the mental model creates brittle knowledge.

Next steps

Read Mastering Bitcoin chapters 1, 2, then start the UTXO model, the accounting system every wallet actually uses.