Case Board — Findings, Traces and Timelines

case no. 2008-10-31 · corpus: ~600 documents · status: open
PREV_HASHthe Satoshi investigation
PREV_HASHthe Satoshi investigation
PREV_HASHthe Satoshi investigation

Case board

live state of the investigation

Everything the investigation holds so far, in one place. Findings are statements the source material supports. Traces are patterns we are watching but have not confirmed. Nothing here is a claim about anyone’s identity.

7
FINDINGS
6
OPEN TRACES
4
SOURCES EXAMINED

Findings

each card carries its source
FINDING #6SUPPORTED
The privacy section promises pseudonymity, not anonymity, and names its own limits. The final section combines applied probability with a short working C program printed inside the paper.
SOURCE DATE31 OCT 2008
ADDED TO CASE04 SEP 2026
SOURCEWhitepaper · sections 9–11
RELATED BLOCK#005
VIEW SOURCE
FINDING #5SUPPORTED
Security 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.
SOURCE DATE31 OCT 2008
ADDED TO CASE28 AUG 2026
SOURCEWhitepaper · sections 5–8
RELATED BLOCK#004
VIEW SOURCE
FINDING #4SUPPORTED
The whitepaper explicitly points to earlier work for the timestamping mechanism and for proof-of-work. It gives no earlier source for the particular combination of these elements with the rule of choosing the valid chain that carries the greatest proof-of-work. In section 4 the author analyses not only cryptography but also the problem of representation: network identities can be multiplied, so the vote is tied to a costly resource — processing power.
SOURCE DATE31 OCT 2008
ADDED TO CASE21 AUG 2026
SOURCEWhitepaper · sections 2–4
RELATED BLOCK#003
VIEW SOURCE
FINDING #3SUPPORTED
The whitepaper uses the convention of a scientific publication (structure, abstract, references) but without the institutional apparatus: no affiliation, no acknowledgements, no reviewers. In the argument, economic reasoning (cost of mediation, micropayments, reversibility) sits alongside cryptography.
SOURCE DATE31 OCT 2008
ADDED TO CASE14 AUG 2026
SOURCEWhitepaper · abstract + section 1
RELATED BLOCK#002
VIEW SOURCE
FINDING #2SUPPORTED
First audience: a few hundred cryptographers. The author sought review, not publicity.
SOURCE DATE31 OCT 2008
ADDED TO CASE07 AUG 2026
SOURCEEmail no. 1 · metzdowd list
RELATED BLOCK#001
VIEW SOURCE
FINDING #1SUPPORTED
Anonymity prepared since at least August 2008 — long before anyone was looking for the author.
SOURCE DATE31 OCT 2008
ADDED TO CASE07 AUG 2026
SOURCEEmail no. 1 · metzdowd list
RELATED BLOCK#001
VIEW SOURCE
FINDING #0SUPPORTED
The corpus is finite and public: ~600 documents. The investigation has a measurable end.
SOURCE DATE31 OCT 2008
ADDED TO CASE07 AUG 2026
SOURCEBitcoin whitepaper
RELATED BLOCK#000
VIEW SOURCE

Trace map

watched, not confirmed

A trace is a pattern that may or may not mean something. It is recorded when a document shows it, and it stays open until other documents either repeat it or fail to.

TRACE T-001ACADEMIC / TECHNICAL WRITINGOPEN
Command of the form of a technical paper — abstract, numbered sections, references — without institutional apparatus.
FIRST OBSERVED#002
TRACE T-002ECONOMICSOPEN
Technical problems argued together with the economics of a payment system: cost of mediation, micropayments, reversibility.
FIRST OBSERVED#002
TRACE T-003CRYPTOGRAPHYOPEN
Familiarity with prior work on timestamping and proof-of-work, cited directly rather than reinvented.
FIRST OBSERVED#003
TRACE T-004NETWORKOPEN
Reasoning about representation and identity in a network: addresses can be multiplied, so the vote is tied to a costly resource.
FIRST OBSERVED#003
TRACE T-005SOFTWARE / CODEOPEN
A working C program printed inside a paper written in academic form — two practices in one document.
FIRST OBSERVED#005
TRACE T-006TIMELINEOPEN
Objections answered before they were raised: the scalability reply is written into section 8 weeks before the first critic posted it.
FIRST OBSERVED#004

Two timelines

the documents, and our reading of them

SOURCE TIMELINE · when the document was written

  • 31 OCT 2008 · whitepaper + email no. 1
  • 03 JAN 2009 · genesis block
  • 08 JAN 2009 · client v0.1
  • 12 JAN 2009 · block 170

INVESTIGATION TIMELINE · when we read it

  • 07 AUG 2026 · #000 · #001 · side threads
  • 14 AUG 2026 · #002 · abstract + section 1
  • 21 AUG 2026 · #003 · sections 2–4
  • 28 AUG 2026 · #004 · sections 5–8
  • 04 SEP 2026 · #005 · sections 9–11

A research and archival project. The investigation relies solely on publicly available primary sources. We make no claims about any person’s identity; any future hypotheses will be labelled as hypotheses and grounded in documented findings.

© All rights reserved. You may share text excerpts of up to 500 characters and individual graphics — always with the project’s name and a link to the source. Publishing full episodes, collections of them or translations — in any form, paid or free — requires our written permission. Satoshi’s materials are quoted as primary sources under the right of quotation; we claim no rights to them. Licensing contact: the address in the “Join” section.

© 2008–2026 PREV_HASH · case open · node v0.2.0