The First Criticism of Bitcoin — 2 November 2008

PREV_HASHthe Satoshi investigation

Block #008

The first reply, and the answer that was already written

DOCUMENTS ON FILEmetzdowd list · reply of 2 Nov 2008 and Satoshi’s answer

SOURCE DATE02 NOV 2008

PREV_HASH#007

The whitepaper had been posted on 31 October. The first archived reply in the thread appears on 2 November 2008, and it does not open with congratulations. It grants that such a system is badly needed, then strikes at the weakest point of the design: if every node must see every transaction, the network will not scale. This is the test the author came for. And here the investigation gains something it could not have seen before reading the document itself.

Artifact 008-A · the exchange, by the archive clock

  02 NOV 2008  23:46:23 UTC   objection: it will not scale
  03 NOV 2008  01:37:43 UTC   answer
                              ---------
                              1 h 51 min

  IN THE ANSWER
  already in the paper .....  simplified payment verification (sect. 8)
  not in the paper .........  transaction size, bandwidth, card-network
                              scale, cost of the connection

OBSERVATIONThe objection is archived at 23:46:23 UTC. The answer is archived at 01:37:43 UTC — one hour and fifty-one minutes later. The core of that answer already existed in print: simplified payment verification has its own numbered section in the whitepaper published two days earlier. But the reply does not stop there. It adds figures the paper does not contain — the size of a typical transaction, the resulting bandwidth, a comparison with the scale of a card network, and what such a connection would cost.

This is where a trace recorded earlier gets its first test in the wild. In block #004 we noted, from the whitepaper alone, that the author argues by engineering estimate: bytes per year, hardware of the day, what a node must keep. That was an observation about a document written in private. Here someone throws him a real problem, in public, under time pressure. And the response is the same: numbers, rates, costs, a projection of how hardware will develop. A feature observed in the paper reappears, unprompted, in live correspondence. What the sequence establishes is narrower than „the answer was already written”, and stronger. The author had considered this class of scalability problem before the criticism appeared, and gave it a section. When challenged, he combined that documented mechanism with new quantitative estimates in under two hours.

TRACE T-009Response pattern under criticism — OPEN, one observation only. Recorded here: reply archived 1 h 51 min after the objection; structure point by point; no defensive language; a documented mechanism extended with new quantitative estimates. Criterion for closing: examine the next 5–10 critical exchanges for reaction time, structure, tone and reuse of earlier material. One instance is not a pattern.

Block sources (originals): metzdowd archive, Nov 2008 · emails

Finding #9 — pinned to the boardThe first archived critical reply to Bitcoin raises scalability. The answer is archived one hour and fifty-one minutes later. A central part of it — simplified payment verification — already exists as section 8 of the published whitepaper; the reply then extends the paper with concrete transaction-size and bandwidth estimates the paper does not contain. The sequence establishes something narrower but stronger than a prepared answer: the author had considered this class of problem before the criticism appeared publicly, and when challenged combined a documented mechanism with new quantitative engineering estimates.

CASE BOARD UPDATE

+1 FINDING #9
+1 TRACE T-009 · response pattern under criticism
+2 DOCUMENTS EXAMINED
0 CONTRADICTIONS

NEXT BLOCK

The thread turns from engineering to ideology

The objection changes: not that the system will fail technically, but that it has been tried before and always died. The answer to that one will show what the author thinks he is building. Friday, 14:10.

← previous block ↑ case dashboardnext: Friday 14:10