Charlie Madden — The Field GuideBitcoin
Follow one payment from a digital signature to a shared history. Build the mental model before forming a view on the asset.
The learning path
- The problem of a copyable coin
- A ledger with many independent checkers
- Make history expensive to rewrite
- A supply schedule with an incentive problem
- What a wallet actually holds
- Understand the tradeoffs before the slogans
The problem of a copyable coin
Why sending money is different from sending a photo.
Understand the double-spend problem before meeting the blockchain.
A payment needs a shared answer
Imagine sending a friend a photo. You still have your copy, and sending a second one is easy. That is useful for information, but awkward for money: a payment must change who can spend a particular amount. A digital money system needs a way to distinguish an authorized transfer from two conflicting attempts to spend the same funds. The difficult question is not whether a message arrived. It is whether everyone can rely on the same account of what has already been spent.
A signature solves only one part
A digital signature is a mathematical proof that a transaction was authorized by the holder of a private key. Other people can check that proof without learning the secret. But someone holding a key can sign two different payments that spend the same funds. Both signatures may be authentic. This is the double-spend problem: authorization alone does not establish a unique transaction history. Bitcoin combines signatures with a network that agrees on an ordering, making only one of those conflicting spends part of its accepted history.
Replace the central bookkeeper
A conventional payment service keeps an authoritative ledger and rejects a second spend against the same balance. Bitcoin asks whether a network can do that job without giving one operator final control of the record. Its proposed answer uses independently checked rules, public transaction history, and a costly process for adding blocks. This arrangement still depends on software, communication, cryptography, and human coordination. As you continue, keep the goal precise: understand how participants agree on valid spending, rather than treating the word decentralized as an explanation.
Digital signatures establish authorization. A shared history is needed to resolve conflicting spends.
Sources
A ledger with many independent checkers
Separate who proposes a payment from who verifies it.
Trace a transaction and distinguish a wallet, a full node, and a miner.
The balance is a useful summary
A wallet might show a single balance, but Bitcoin tracks specific unspent transaction outputs, often shortened to UTXOs. Each output records an amount and conditions for spending it. A new transaction consumes previous outputs and creates new ones. Think of paying with a ten-dollar note and receiving change: the input disappears from your available funds, while the merchant and change outputs become separately spendable. This model makes a concrete rule possible: an output can be consumed once in the accepted chain, and only when its spending conditions are satisfied.
A full node checks for itself
A full node is software that independently validates blocks and transactions against the rules it follows. It checks matters such as spending authorization, whether inputs exist, and whether those inputs have already been spent. Nodes exchange information over a peer-to-peer network; there is no need for every node to connect directly to every other node. A message travels between peers, and each recipient can verify it. Running a node gives its operator a way to check the ledger without relying entirely on a wallet company or block explorer.
Different jobs, different authority
The wallet prepares and signs a payment. Nodes check and relay eligible information. Miners assemble candidate blocks and compete to add one to the history, a process we examine next. These roles can overlap on one machine, but they are different jobs. A miner cannot make an otherwise invalid spend acceptable to a node that enforces the existing rules. Likewise, creating thousands of node identities does not grant thousands of votes over transaction order. Distinguishing proposal from verification removes much of the mystery from the network.
Wallets authorize spending, miners propose blocks, and full nodes independently enforce validity.
Sources
Make history expensive to rewrite
Proof of work, competing histories, and probabilistic finality.
Explain why confirmations increase confidence without promising absolute irreversibility.
Hard to find, easy to check
A hash is a short digital fingerprint calculated from data. Bitcoin miners repeatedly vary candidate block data and calculate hashes, looking for a result below a target. There is no known useful shortcut: they make many attempts. Finding a qualifying result requires work, while checking it is quick. That asymmetry matters in an open network, because creating a new identity is cheap. Proof of work ties the competition for block production to computation rather than to a count of accounts or claimed identities.
Choose between valid histories
Blocks include a fingerprint of the previous block, linking the history together. Changing old transaction data changes those fingerprints, requiring new proof of work for that block and its successors. Two miners can find valid blocks near the same time, temporarily producing competing tips. Nodes ultimately follow the valid chain with the greatest accumulated proof of work. “Valid” matters: a chain with more work still cannot authorize arbitrary theft or excessive coin creation for nodes enforcing the existing rules. Work resolves ordering among histories that pass their checks.
Confidence grows with depth
A transaction receives its first confirmation when included in the accepted chain; subsequent blocks add confirmations. Replacing that history generally becomes harder as work accumulates above it. This is probabilistic finality: confidence increases, rather than switching from uncertain to mathematically impossible at a fixed number. The appropriate wait depends on the value at stake and the threat model. A majority of hash power can threaten ordering, censor transactions, or attempt reversals of its own payments, but it does not reveal other people’s private keys.
Proof of work makes alternative histories costly; confirmations reduce reversal risk under assumptions about the network and attackers.
Sources
A supply schedule with an incentive problem
Separate new issuance, transaction fees, and market price.
Read the issuance curve and understand what it can—and cannot—tell you.
Count blocks, not calendar years
The block subsidy is the maximum newly issued bitcoin a miner can claim in a valid block. It began at 50 bitcoin and halves every 210,000 blocks. That interval is roughly four years because the system targets an average block interval near ten minutes; the calendar date is not fixed. Repeated halvings make total issuance approach a ceiling below 21 million bitcoin under the current rules. Smaller units allow amounts to be divided more finely, but dividing an existing amount does not increase the number of bitcoin.
A reward has two components
A miner’s block reward combines the subsidy with transaction fees. Fees come from existing funds spent by users, rather than being newly created coins. The rules restrict how much a miner can claim: asking for more than the permitted subsidy plus fees makes a block invalid. Miners face equipment, electricity, and operating costs, so their incentives depend on both revenues and costs. As subsidies decline, future fee demand becomes a significant security question. The schedule specifies issuance; it does not guarantee a particular security budget in dollars.
Scarcity does not set demand
A predictable supply rule is one property of an asset. Its market price also depends on how much people want to hold it, their alternatives, liquidity, and changing expectations. A halving therefore does not mathematically require a price increase. Equally, a rule in software is sustained by participants continuing to recognize that rule; changing it would raise coordination and acceptance questions. Ask two separate things when evaluating a monetary system: how are units issued, and why would anyone want to use or hold them?
The halving reduces new issuance per block. It neither halves existing balances nor determines future price.
Sources
What a wallet actually holds
Control, recovery, and the responsibilities behind a balance.
Distinguish a key, an address, a recovery backup, and a custodial claim.
The coins are in the ledger
A wallet manages information used to receive, track, and authorize spending. Bitcoin is not stored inside a device like a photograph inside a camera. The shared ledger records spendable outputs; private keys help satisfy their spending conditions. A receiving address is information you can share to request a payment. A private key must stay secret because it can authorize spending. A signature can be shown to the network without exposing that key. Separating public receiving information from secret spending authority is the essential first distinction.
Recovery is part of the design
Many wallets derive their keys from a backup represented by recovery words. The exact recovery procedure depends on the wallet, its format, and any extra settings. Someone who obtains the required secret material may gain control of the funds; losing every usable copy may make spending impossible. A hardware signing device can keep key operations away from a general-purpose computer, but it cannot decide whether a recipient is honest. Backups, transaction review, software integrity, and a workable recovery plan address different problems. No single gadget resolves all of them.
Ask who can actually sign
In self-custody, you control the secret material needed to authorize spending. With a custodial service, the provider normally controls the relevant keys and credits an internal account balance to you. Its interface can look similar to a wallet, while the relationship is different: you depend on its ability and willingness to process withdrawals. Self-custody changes that dependency but introduces operational responsibilities. Before comparing products, ask who can sign, who can recover access, what happens if a device fails, and what happens if the provider disappears.
A wallet manages spending authority. Custody determines who has that authority and who bears recovery risk.
Sources
Understand the tradeoffs before the slogans
A useful conclusion is a set of better questions.
Evaluate a Bitcoin claim by identifying the layer, assumptions, and costs involved.
Open verification has resource costs
Independent verification depends on people being able to obtain and check the record. More on-chain activity means more data and validation work, so capacity is a design tradeoff rather than a free setting. Limited block space also means transactions compete for inclusion, with fees and waiting times varying. Additional payment systems can use Bitcoin as a settlement layer while moving activity elsewhere. When a service promises speed or low fees, ask which layer it uses, which party holds funds, and what conditions are required to leave that system.
Public does not mean anonymous
The chain exposes transaction history even though it does not label every output with a person’s legal name. Once an address or transaction is associated with an identity, other activity may become easier to connect. Services can also learn information outside the chain. Privacy is therefore a practical question about what is revealed, to whom, and through which channel. A public ledger helps independent auditing while creating this privacy challenge. The same transparency can be useful for verification and uncomfortable for the person whose spending becomes traceable.
Compare guarantees at the right boundary
The base protocol does not guarantee stable purchasing power, a refund after an error, or the reliability of a company using its name. Proof of work consumes energy; measuring its effects requires evidence about electricity sources and alternative uses, rather than a slogan alone. A sound evaluation separates technical rules from economic forecasts and operational choices. Finish with a checklist of questions: What problem is being solved? Who must be trusted? What can fail? What evidence would change the claim? You can investigate Bitcoin without accepting an investment thesis.
Evaluate the actual mechanism, including its costs and dependencies. Protocol rules are different from price forecasts and service promises.
Sources
Glossary
- Satoshi
- One hundred-millionth of a bitcoin; the base unit used for amounts in Bitcoin transactions.
- UTXO
- An unspent transaction output: an amount and spending conditions that a later transaction can consume.
- Full node
- Software that independently checks Bitcoin blocks and transactions against the rules it follows.
- Proof of work
- Evidence of computational effort, costly to produce and comparatively easy to verify.
- Confirmation
- Inclusion in a block, plus the depth added by later blocks in the accepted chain.
- Block subsidy
- The maximum newly issued bitcoin permitted in a block under the issuance rules, separate from fees.
- Private key
- Secret information used to authorize spending by creating a digital signature.
- Custody
- The arrangement determining who controls spending authority and bears responsibility for safeguarding it.
Enable JavaScript for scroll-driven visual stories, hands-on experiments, checkpoints, and browser-local progress.