Cryptographer who was the first to respond to the Bitcoin white paper
Two days after Satoshi Nakamoto posted the Bitcoin whitepaper to the cryptography mailing list on October 31, 2008, James A. Donald became the first person to publicly respond:
We very, very much need such a system, but the way I understand your proposal, it does not seem to scale to the required size.
His skepticism pulled some of Satoshi’s most detailed early architectural explanations into the public record — simplified payment verification, the trust and double-spend model — including one of the few replies in which Satoshi’s conviction showed, a moment taken up again in the genesis-block entry.
Donald is a cryptographer and libertarian commentator long active in the cypherpunk community; he maintained the website jim.com on cryptography, political philosophy, and economics.
Donald argued in his November 2 reply that the system would require every node to process every transaction, making it impractical for widespread use.
Across November 2008, Satoshi answered the scaling objection point by point: not every node need process every transaction — simplified payment verification would let lightweight clients confirm payments without storing the full chain.
Days later, in a November 9 message, Donald coined a name for a bitcoin bank — a “bink” — and cast bitcoins as a settlement layer beneath account money, the way gold sat beneath the gold standard; it anticipated the exchanges and custodians that would later dominate. The shape Donald described — a settlement layer beneath stacked exchange, ETF and Lightning custodians — is the shape the running system took as it drifted from the whitepaper.
Pressed on trust and double-spending, Satoshi spelled out the model in unusual detail. On November 13, still pressing the same agreement problem underneath the currency, Donald gave it its classical name — the Byzantine Generals Problem — and Satoshi answered by recasting the proof-of-work chain as a solution to it.
Donald’s critical engagement with the white paper forced Satoshi to articulate Bitcoin’s scalability model and trust assumptions in a public forum. He stayed skeptical of Bitcoin’s feasibility — but a doubter asking the first hard questions is exactly why some of Bitcoin’s earliest design rationale sits in the public record at all.
Donald’s place at the origin of the public record, his cypherpunk profile, and a rare word he shared with Satoshi have made him a recurring Satoshi candidate — the strongest lead Benjamin Wallace pursued in The Mysterious Mr. Nakamoto (2025) before excluding him in person. The case for and against — including Satoshi answering him as a third party, and Wallace’s character-based exclusion — is laid out in the James A. Donald = Satoshi hypothesis, and he is among the named candidates in the identity-hypotheses overview.
20 entries / 1 thread
James Donald tied the issue he pressed Satoshi on to the 1982 Byzantine Generals Problem. Satoshi said Bitcoin solved it in a network anyone could join, and explained it with a king's wi-fi password.
Doubters called it unscalable in 2008. A famed hacker failed to break the code. A judge, a dictionary, and a Nobel nominator weighed in. What others said about Satoshi, read as one record.
Eight pages posted to a mailing list on October 31, 2008 — a report on a working system that had been 18 months in the making. It met silence first, then doubts about scale.
The first person to answer the Bitcoin whitepaper, James Donald was also the only other person known to use a rare word of Satoshi's, making him Benjamin Wallace's top lead. The evidence, weighed.
Hal Finney to Satoshi during pre-release code review, asking how large the P2P node network might grow — tens to millions — and whether clients could scale to all world financial transactions.
Twelve recurring Satoshi candidates, compared across four independent layers: profile match, stylometric attribution, direct correspondence and development environment.
James A. Donald responds to Satoshi's Bitcoin announcement, raising the question of how the system scales and how nodes agree on a single transaction history.