Module 3 · The Idea of Bitcoin / 3.5

From a message to an agreement.

Try the whole design problem without a slogan to lean on.

You are helping a community design a digital payment system. Someone suggests emailing a coin-shaped image. Another person suggests one shared website. A third suggests giving every new username a vote.

Each proposal tells you something about the problem. None can be judged by its appearance alone.

Separate three questions.

First, who may authorize a payment? A signature can help answer that.

Second, does the payment obey the rules, including whether the amount is still available to spend? A validating node must check the history and conditions.

Third, when competing valid histories appear, how do participants converge on one? Bitcoin’s proof-of-work design uses cumulative work for that ordering problem.

Copying a message answers none of these questions by itself. A long list of usernames does not prove a long list of independent people.

Illustrative work unitsCandidates

C claims the most work, but it includes a forbidden spend. Work alone is not enough to choose a chain.

Authorization, validity, and ordering are related but different.

Ask who controls the parts.

A company can operate a reliable service across many computers while retaining central authority over its records. Independent operators may instead validate a common rule set. Distribution of machines and decentralization of control are different.

The earlier designs taught separate lessons: private credentials, issuer dependence, costly-to-produce proofs, and proposals for shared digital ownership. Bitcoin combined several tools with networking rules and incentives.

Those incentives make rewriting costly under the design’s assumptions. They do not make invalid blocks acceptable, guarantee permanent attack unprofitability, or remove every form of dependence.

Ask what the evidence establishes.

A white paper describes a proposal. Software makes that proposal testable. Transactions and participant accounts show people using it. Each is useful, but each has limits.

The network continuing beyond its creator’s public work is evidence of a system that does not need that person to approve payments. It is not evidence that no one has influence.

Now you are ready to open the machine: keys, transactions, blocks, mining, and the people who choose which rules to run.

The idea to keep

Keep the three questions separate: authorization, validity, and ordering. Then ask where control sits and what evidence supports the claims.

A moment to try it.

Take your time. Explain the reason, not only the answer.

1 of 5

An authorized sender broadcasts two payments spending the same available amount. Why is checking both signatures not enough?

Explain it in your own words.

Answers stay in this browser. Use examples only—never enter recovery words, keys, account details, or real balances.

Interactive answer checking needs JavaScript. The questions and explanations remain available here.

An authorized sender broadcasts two payments spending the same available amount. Why is checking both signatures not enough?

Both instructions may be authorized individually, but the accepted history cannot spend the same funds twice. Nodes also need availability checks and a way to settle the competing valid histories.

A higher-work branch breaks an issuance rule. A lower-work branch follows every rule. Which branch can a validating node accept?

Work selects among valid candidates. It never overrules issuance or signature requirements.

One operator owns a thousand copies of a ledger and can command all of them. Which description is accurate?

Independence of decision-makers matters. Copies under one operator do not establish decentralized control.

Match the evidence to the claim it can support.

A proposal is not a functioning system. Testing is evidence about implementation, not a guaranteed investment. A signature proves key control, not civil identity.

A merchant waits while more blocks build on top of a payment. What risk is the merchant trying to reduce, and what is not being guaranteed?

The merchant reduces the risk that a competing valid chain will replace the payment. Additional accumulated work raises that barrier under the assumptions. It does not guarantee the asset’s market price or make all attacks impossible.