Block #004
Why anyone would run it
Documents on file: whitepaper, sections 5–8 (Network, Incentive, Reclaiming Disk Space, Simplified Payment Verification) · prev_hash: block #003
A machine that works is not yet a system that runs. Someone has to spend electricity on it, and the whitepaper answers why: whoever adds a block takes the new coins. The reward doubles as the way coins enter circulation — no issuer needed.
Here the document changes register. Up to now it argued about hashes and signatures. From section 6 on, it argues about motives.
Source text · whitepaper, section 6
„…he ought to find it more profitable to play by the rules… than to undermine the system and the validity of his own wealth.”
Bitcoin: A Peer-to-Peer Electronic Cash System, p. 4, Incentive
Four observations from these sections
recorded, not concluded
the attacker is described as someone who counts costs, not as an adversary with unlimited power
the conclusion drawn is that it pays more to play by the rules than to break them
disk space is calculated in bytes per year and compared to ordinary consumer hardware
section 8 answers the scalability objection before the objection was ever raised in public
That last point is the one to keep. In block #002 we watched the first critic of the mailing list attack scalability — and the answer was already written, weeks earlier, in section 8. The author had run the objection in his own head before anyone raised it.
The rest of these sections reads like an engineer costing a build: bytes per year, hardware of the day, what a node must keep and what it may forget. No formal proofs. No theorems. Estimates, and the arithmetic behind them.
Block sources: bitcoin.org/bitcoin.pdf
Finding #5 — pinned to the boardSecurity is argued economically: the attacker is modelled as someone who counts costs. The scalability objection is answered in section 8, weeks before it was raised publicly (see block #002). The register is that of an engineer costing a build — estimates and arithmetic, no formal proofs.
In block #005Privacy, and a chapter of arithmetic that ends with working C code inside an academic-style paper. That combination is rare enough to be a trace. Friday, 14:10.