Pseudonymous creator of Bitcoin
On October 31, 2008, Satoshi Nakamoto published the Bitcoin whitepaper. Two and a half years later, he sent his last known email and stopped. Approximately 1.1 million BTC mined under a single coordinated pattern in those first months have not moved since.
“Satoshi Nakamoto” is a pseudonym. The individual or group behind it has never been identified — the question the identity-hypotheses overview examines by weighing ten named candidates against the documented record compiled here.
New to Bitcoin? Start with the visual glossary — 30 terms across 8 chapters with diagrams, no prior knowledge assumed.
The earliest documented communication is the August 20, 2008 email to Adam Back asking about Hashcash citation format. The whitepaper followed on October 31, 2008, sent to the cryptography mailing list at metzdowd.com — nine pages describing how a chain of digital signatures, secured by proof-of-work, could resist double-spending without a trusted intermediary.
On January 3, 2009, Satoshi defined the parameters of Block 0. Embedded in its coinbase field, the front-page headline of The Times from that day:
“The Times 03/Jan/2009 Chancellor on brink of second bailout for banks”
Block 0 is hardcoded as a constant in the source — every node reconstructs it locally from the same parameters (see the genesis-block hardcode analysis). On January 8, Bitcoin v0.1 was released. Four days later, Block 170 carried 10 BTC from Satoshi to Hal Finney — the first person-to-person Bitcoin transaction.
Satoshi was active on the cryptography mailing list, the bitcoin-list mailing list on SourceForge, the BitcoinTalk forum (which Satoshi and Martti Malmi created), the P2P Foundation forum, and in private email. Direct correspondents included Adam Back, Wei Dai, Hal Finney, James A. Donald, Ray Dillinger, Dustin Trammell, Martti Malmi, Mike Hearn, Gavin Andresen, Laszlo Hanyecz, Jeff Garzik, and others. Across 2009–2010, Satoshi authored hundreds of forum posts and emails — explaining design choices, responding to technical objections, coordinating development.
By September 2010, Satoshi was telling Gavin Andresen privately that he was working on other projects — the earliest documented signal of withdrawal. Over the following months he transferred control of the Bitcoin source repository and the network alert key to Andresen, while continuing to communicate with a small circle of developers by private email.
The final public BitcoinTalk post was on December 12, 2010:
“I plan to pass the baton.”
Seven days later, Andresen publicly announced he would take over project management.
On April 23, 2011, Satoshi wrote to Mike Hearn:
“I’ve moved on to other things. It’s in good hands with Gavin and everyone.”
Three days later, on April 26, 2011, the final known email — alert key handover to Andresen:
“I wish you wouldn’t keep talking about me as a mysterious shadowy figure.”
No verified communication from Satoshi has been recorded since.
The P2P Foundation profile listed an April 5, 1975 birth date and a Japanese location — unverified and widely considered fictitious. Satoshi wrote in fluent English with conventions consistent with British or Commonwealth usage. Analysis of posting timestamps has been used to argue for various time zones; no conclusive location has been determined. The “Satoshi Nakamoto” pseudonym sits inside the recognizable techno-orientalist symbolic field of the 1980s–90s — examined as a structural observation about reception, independent of authorial intent, in the pseudonym-and-AKIRA analysis. Satoshi’s relationship to the cypherpunk movement and the alignment of his documented practice with its philosophical core are treated in the independent-arrival analysis.
Bitcoin v0.1 was built on Windows using Microsoft Visual C++ 6.0 SP6 and MinGW GCC 3.4.5. The initial release was Windows-only, distributed as a .rar archive — unusual for an open-source project. No version control system was used for v0.1; SVN was introduced later with help from Martti Malmi and Gavin Andresen.
From late 2009, Satoshi began porting Bitcoin to Linux (Ubuntu) with Malmi’s assistance. He personally set up Ubuntu test environments and debugged deep issues — pthread_cancel, MSG_DONTWAIT, Berkeley DB, GTK thread safety. Linux conventions themselves were unfamiliar territory: config file formats, daemon switch naming, startup scripts. On the forum in December 2009:
“That’s great because that’s where I have less expertise.”
In a December 2010 email to Andresen, he described Andresen as “technically much more Linux capable than me.” Mac support came entirely from Laszlo Hanyecz — Satoshi had no Mac to test on. BSD knowledge was conceptual (socket origins), not hands-on. Through 2010, cross-platform support for Linux, macOS, and FreeBSD expanded via community-contributed patches. A statistical analysis of Satoshi’s source code covers coding style, commit time patterns, and v0.1.0–v0.3.19 evolution.
Approximately 1.1 million BTC were mined under a single coordinated pattern in Bitcoin’s first months — the Patoshi pattern, attributed to Satoshi. None of those coins have moved.
.rar packaging, absence of version control, Hungarian-notation variable naming, OpenSSL dependency, the Dan Kaminsky 2011 security audit, and the foresighted-security-vs-informal-process distinction are examined in the v0.1 distribution and tooling anomalies analysis.Across mailing-list and forum messages, Satoshi explained design choices, responded to technical objections, and made operational decisions — declining the WikiLeaks donation push in December 2010, handing source-repository commit rights and the network alert key to Andresen in late 2010 and early 2011.
For the ideological lineage Satoshi designed inside — Hayek’s 1976 Denationalisation of Money, the 1990s Extropian milieu, the cypherpunk movement, and the bounded direct-influence claims supported by the primary record — see the Hayek-Extropian lineage entry and the companion analysis Satoshi was not a cypherpunk.
This biography is read in companion with the Satoshi self-statements inventory, which catalogues every place where Satoshi was the subject of his own sentence and reads them as a single body of evidence about what Satoshi said about himself — a complementary axis to the biographical documentary record collated here.
464 entries
Hayek's 1976 competing-currencies case, the 1995 Extropian 'Hayeks' thought-experiment, and Bitcoin's 2009 non-state issuance — one ideological lineage with bounded direct-influence claims.
On his Unenumerated blog, Nick Szabo asks for help implementing bit gold — his 1998 digital currency design. No one publicly responds. Six months later, Satoshi publishes the Bitcoin whitepaper.
Interactive D3 timeline of every documented Satoshi event — correspondence, mailing lists, BitcoinTalk, P2P Foundation, SourceForge — from August 20, 2008 to the disputed 2014 P2P Foundation post.
Inventory of every Satoshi self-reference in the public record (Aug 2008 – Apr 2011): identity claims, dev disclosures, operational state, farewells, authenticity-disputed. Each row anchored.
Satoshi Nakamoto's earliest known email. He contacts Adam Back to verify the Hashcash paper citation and shares a pre-release draft titled 'Electronic Cash Without a Trusted Third Party' (ecash.pdf).
The earliest known email from Satoshi Nakamoto: contacting Adam Back to verify the Hashcash citation and sharing a pre-release draft titled 'Electronic Cash Without a Trusted Third Party'.
Adam Back confirms the Hashcash citation and suggests Satoshi look at Wei Dai's b-money proposal. This referral led Satoshi to contact Wei Dai and cite b-money in the Bitcoin whitepaper.
Satoshi thanks Adam Back for the b-money reference and reveals he was not previously aware of Wei Dai's proposal. Historically significant line: 'my ideas start from exactly that point.'
Adam Back suggests Satoshi look at Ron Rivest's 1996 MicroMint paper on k-way hash collisions. Back admits he has not yet read the draft — a decision he later called 'probably my biggest mistake.'
The hypothesis that Wei Dai — b-money author (whitepaper ref [1]) and Crypto++ creator — was Satoshi. Counter: Aug 22, 2008 email reads as third-party reception; 2014 AALWA self-distinction.
Satoshi emails Wei Dai asking for the correct b-money citation, revealing he learned of it via Adam Back. The email linked the pre-release draft 'Electronic Cash Without a Trusted Third Party'.
An early draft of the Bitcoin whitepaper dated October 3, 2008, predating the final by ~a month. Shared privately before the Cryptography ML announcement on October 31, 2008.
The whitepaper's title names a payment system; section 6's gold is an issuance analogy. Satoshi designed one thing — hard issuance, cash use — whose scarcity later tilted it toward digital gold.
Editorial reading of Satoshi's relationship to cypherpunk, from three primary observations: he didn't know b-money, Wei Dai testified Satoshi was "not previously active," alignment with Hughes 1993.
Descriptive reading of the "Satoshi Nakamoto" pseudonym against the cyberpunk and techno-orientalist symbolic field of the 1980s-90s. Structural observations, not claims about authorial intent.
Recurring Satoshi candidates aligned across four independent layers — profile match, stylometric attribution, direct correspondence, and development environment.
Reads the asymmetry between public attempts to identify Satoshi, the surviving material trail, and the persistent identification gap. Companion entry to the identity-hypotheses overview.
Structural reading of how "Satoshi Nakamoto" remained unidentified across development, public phase, and withdrawal. Six layers: pseudonym, channels, language, env, genesis constants, handover.
Bitcoin v0.1 reuses one cypherpunk primitive (PoW from Hashcash), borrows general CS components (Merkle trees, linked timestamping), and synthesizes the rest (UTXO, mining, 21M cap, P2P, ECDSA).
Bitcoin chose a hard 21M cap; b-money (1998) proposed elastic supply; fiat runs central-bank discretion. The cypherpunk debate, Wei Dai's 2013 regret, and 15 years of cryptocurrency variants.
Bitcoin's 'digital gold' status rests on two layers of decentralization — system and people/organization — and six structural features no later cryptocurrency combines to the same degree.
Genealogy of every Bitcoin protocol fork that left a separate chain alive (Bitcoin Cash, SV, Gold) and the adjacent cryptocurrencies derived from Bitcoin (Namecoin, Litecoin, Dogecoin).
The final Bitcoin whitepaper, 'Bitcoin: A Peer-to-Peer Electronic Cash System,' published October 31, 2008. Hosted at bitcoin.org/bitcoin.pdf, announced on the Cryptography Mailing List.
Satoshi Nakamoto's first public announcement of Bitcoin on the Cryptography Mailing List. He introduces a peer-to-peer electronic cash system with no trusted third party.
The hypothesis that James A. Donald — first to respond to the Bitcoin white paper — was Satoshi. A stylometric lead drew Benjamin Wallace to him, who then excluded Donald in person on character.
Satoshi Nakamoto registered the 'bitcoin' project on SourceForge.net, establishing the first public repository and project page for Bitcoin's source code and releases.
Hal Finney's private email to Satoshi during pre-release code review, asking foundational scalability questions: 'How large do you envision it becoming? Tens of nodes? Thousands? Millions?'
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.
Satoshi Nakamoto's post: "[bitcoin-list] Welcome".
How Bitcoin uses elliptic-curve keys, digital signatures, hash functions, and deterministic derivation to secure ownership without trusted third parties.
How Bitcoin nodes agree on a single chain: SHA-256d proof of work, the difficulty adjustment algorithm, block validation rules, fork resolution, and probabilistic finality.
How Bitcoin blocks are structured, how Merkle trees commit transactions to block headers, and how the most-work chain selection rule resolves forks.
Cross-cutting architecture comparison across every subsystem: Satoshi's v0.1 (January 2009) side by side with modern Bitcoin Core v27+, with split diagrams and domain tables.
How Bitcoin's 21 million cap emerges from a geometric halving series, how block rewards transition from subsidy to fees, and how the incentive model sustains honest mining.
How Bitcoin nodes find each other, exchange transactions and blocks, and resist network-level attacks across the P2P gossip layer.
How the Bitcoin ecosystem layers above and around the base chain: Lightning payment channels, federated sidechains, L1 envelope extensions, and mining pool architectures.
How Bitcoin Core persists blocks, maintains the UTXO set, indexes chain state, manages the mempool, prunes historical data, and bootstraps via assumeUTXO.
Deep-dive into Bitcoin's transaction layer: UTXO lifecycle, transaction structure, Script evaluation, ECDSA and Schnorr signatures, SegWit, and Taproot.
Bitcoin's threat model mapped end-to-end: what the protocol trusts, what it defends against, how each attack is countered, and where open risks remain.
High-level system overview of Bitcoin's architecture, layer model, and data flow. Entry point to a 12-page design-document series covering every major subsystem.
How Bitcoin Core manages keys, constructs transactions, selects coins, estimates fees, and exposes functionality through RPC, REST, and ZMQ interfaces.
Technical analysis of Bitcoin's genesis block from v0.1 source: hardcode auto-construction, the five-day gap as timestamp artifact, two-layer authorship reading, PoW headroom, key possession.
Bitcoin's first block contains a Times bank-bailout headline — Satoshi's only personal voice inside the design, etched in the system's most permanent place. A reading of why he chose it.
Satoshi announces the release of Bitcoin v0.1, the first working implementation of the Bitcoin software. Available for Windows, with the source code included.
Satoshi personally notifies Hal Finney of the Bitcoin v0.1 release hours after the public Cryptography list post, sending the SourceForge link and pointing him to bitcoin.org for release notes.
Statistical analysis of Satoshi's Bitcoin source (v0.1.0–v0.3.19): coding-style fingerprint, commit times suggesting EST/CST, growth from 19,901 to 31,909 lines over 14 months, final-commit traits.
Editorial reading of Bitcoin v0.1's unusual distribution and tooling absences (.rar packaging, no version control, no tests), placed against Warez-scene conventions and Kaminsky's 2011 security audit.
Satoshi's difficulty retarget has an off-by-one: it measures 2,015 blocks instead of 2,016. A hashrate majority can exploit it via timestamp manipulation. The Great Consensus Cleanup proposes a fix.
On the public record, Satoshi developed Bitcoin on Windows exclusively for 27 months (design + release + early period); Linux engagement first appears as reactive support for Malmi's port.
Satoshi Nakamoto released Bitcoin v0.1, the first public release of the Bitcoin software, on SourceForge. This Windows-only release made it possible for anyone to run a Bitcoin node and mine coins.
Editorial forensic reading of Satoshi's operational environment during Bitcoin v0.1 launch week (Jan 8-12, 2009): "from where I am" in the Jan 10 email to Finney, and dense activity cadence.
Satoshi tells Finney that he cannot receive incoming connections from his location, revealing an operational constraint in the earliest days of the Bitcoin network.
Satoshi writes Adam Back for the final time, thanking him for paper suggestions and announcing the Bitcoin software launch. Includes Hal Finney's project overview from the Cryptography mailing list.
The first known tweet about Bitcoin. Hal Finney posted 'Running bitcoin' on the day Bitcoin v0.1 was released (January 10/11, 2009). He was the first known person other than Satoshi to run it.
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin v0.1.2 now available".
Dustin Trammell's first email to Satoshi after running the Bitcoin alpha. Reports usage, mentions a public timestamp service, and asks about coin maturity (generated coins showing 0.00 credit).
Trammell's first email to Satoshi after running the Bitcoin alpha. Shares a public timestamp service link and asks about coin maturity (generated coins showing 0.00 credit).
The first person-to-person Bitcoin transaction in history. Satoshi Nakamoto sent 10 BTC to Hal Finney in Block 170, confirming that Bitcoin's peer-to-peer electronic cash system worked as designed.
Satoshi replies to Dustin Trammell, explaining the coin maturity system and recommending an upgrade to version 0.1.3 which had stabilized the software.
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin v0.1 Alpha release notes".
Trammell tells Satoshi about his proof-hashes Google Group, gives feedback on the credit field display, reports running v0.1.1 and will upgrade, and offers to help test new features.
Trammell reports two issues upgrading from v0.1.0 to v0.1.3: the old process wouldn't exit, and all four generated coins showed 'Generated (not accepted)' — likely orphans from the communications bug.
Trammell asks what prevents the most powerful node from generating the majority of bitcoins — one of the earliest questions about mining centralization.
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin v0.1.3".
Satoshi informs Trammell that bugs are fixed in v0.1.3 and offers to send him some coins via the send-to-IP feature, one of the earliest known direct Bitcoin transfers.
Trammell provides his IP address for Satoshi to send coins, explains the proof-hashes group is open for posting, discusses Bitcoin's early vulnerability, and compares mining to a roulette wheel.
Trammell's detailed security analysis of Bitcoin's send-to-IP feature, identifying MITM vulnerabilities including ARP poisoning and ISP-level interception. Recommends always using Bitcoin addresses.
Satoshi discusses dynamic IPs, asks permission to CC the conversation to bitcoin-list and the Cryptography mailing list, and envisions Bitcoin use cases including pay-to-send email and micropayments.
Satoshi responds to Trammell's MITM analysis by classifying attacks into two types (chain-of-communication vs. anyone on the Internet), proposes a combined IP+address fix, and notes wallet encryption.
Trammell argues Bitcoin addresses are more secure than IP-based sending since they verify through multiple channels. He proposes an address-advertisement toggle and reports an exit socket bug.
Trammell confirms his IP is static, agrees to CC publicly, says he'll join bitcoin-list, reveals he started mining as an investment after Hal Finney's message, and discusses micropayment uptake.
Satoshi CC's his Trammell exchange to bitcoin-list and the Cryptography list, sharing his Bitcoin vision including the famous line 'It might make sense just to get some in case it catches on.'
Satoshi reveals the wallet location (%appdata%\Bitcoin), explains it uses a transactional database (DBM) safe from crash/power loss, and confirms socket cleanup code is added for the next release.
Satoshi Nakamoto's reply in the thread "[bitcoin-list] Bitcoin v0.1 released".
Trammell reports confusion about a 100 BTC transfer between his own two Bitcoin instances — the transaction details showed 'Satoshi' as a label, leading him to wonder if Satoshi had sent the coins.
Satoshi explains the 'Satoshi' label came from Trammell's own address book, that transactions show the receiving address (not the sender), and recommends per-payer addresses to identify payers.
Trammell realizes the confusing 'Satoshi' label was on his own receiving address, confirms he has multiple addresses at home, and asks if 'Satoshi' was the default since he doesn't recall setting it.
Satoshi explains the default address label is 'Your Address', suggests the mislabeling was a UI-driven user error, and acknowledges that per-payer receiving addresses have no real-world analogy.
Trammell admits the mislabeling was his error, suggests changing 'Received with' to 'Received payment to' for clarity, and draws a PayPal analogy as the closest parallel to multiple addresses.
Satoshi responds to Hal Finney's botnet/pay-per-send point, proposing that fake mailboxes could 'reverse-spam' spammers by harvesting their POW tokens. He also describes e-gold's 'dusting' problem.
Satoshi Nakamoto responds to Nicholas Bohm's report of problems running Bitcoin, asking for the debug.log file to diagnose the issue.
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin v0.1.5 released".
Satoshi announces Bitcoin on the P2P Foundation forum, describing the problems with conventional currency and how Bitcoin solves them through cryptographic proof instead of trust.
Satoshi introduces Bitcoin to the P2P Research mailing list, explaining trust-based currency problems and how Bitcoin uses cryptographic proof and a peer-to-peer network to solve double-spending.
Mike Hearn contacts Satoshi Nakamoto for the first time with questions about Bitcoin's scalability, mining hardware, inflation schedule, and coin denominations.
Mike Hearn asks Satoshi whether the Electronic Funds Transfer Act could apply to Bitcoin and if the inability to do chargebacks risks making it illegal.
Martti Malmi's first message to Satoshi: introduces himself as Trickstern from the anti-state.com forum, offers to help with Bitcoin development.
Satoshi's first reply to Martti Malmi, who had offered to help with Bitcoin. Satoshi praises Malmi's understanding of Bitcoin and asks him to help write website content and a FAQ.
Malmi agrees to develop the Bitcoin website and FAQ, proposes password-protected private keys, and reports running a Bitcoin node 24/7.
Satoshi addresses concerns about Bitcoin's energy consumption, arguing it would be far less than traditional banking while acknowledging the tension between economic liberty and conservation.
Satoshi reviews Malmi's FAQ draft and warns against framing Bitcoin as an investment, stating 'we can't pitch it as that' - a historically significant stance on Bitcoin's positioning.
Nicholas Bohm, a retired British solicitor and early Bitcoin user, writes to Satoshi that after installing a new router, his Bitcoin client can no longer connect to the network.
Satoshi advises Bohm to forward port 8333 on his new router so his Bitcoin node can receive incoming connections, explaining that without inbound-capable nodes online, the network fails to function.
Satoshi suggests using the word 'cryptocurrency' to describe Bitcoin and asks Malmi to remove investment language from the site - a key moment in Bitcoin's branding history.
Bohm reports to Satoshi that Bitcoin has failed to establish any connections for over a day, despite restarts. He had been maintaining 3-5 node connections prior to July 15th.
Satoshi's candid reply to Bohm's connectivity issue, admitting there may be no other nodes running at that moment. He encourages Bohm to keep his server online so new users have someone to connect to.
Satoshi follows up that he is connected to IP 70.113.114.209 and notes Bohm may have an outgoing-connection issue if not. The IP was later identified as likely Dustin Trammell's in Austin, Texas.
Malmi proposes creating a Bitcoin-to-fiat exchange service, detailing pricing formulas and profit mechanisms. This led to one of the first Bitcoin exchanges and the historic first BTC-to-USD sale.
Satoshi emphasizes that autostart with minimize-to-tray is 'a must-have feature' for network growth, comparing it to early file-sharing strategies. Implemented by Malmi for Bitcoin 0.2.
Complete record of all four developers who had commit access to Bitcoin's SourceForge SVN repository. 252 revisions were recorded from August 30, 2009 to September 13, 2011.
Satoshi responds to Liberty Standard's report of Bitcoin crashing under Wine, attributing it to Wine compatibility issues. Eugen Leitl also replied in the thread, asking about Debian packages.
Eugen Leitl contradicts Satoshi's claim that bitcoin.sourceforge.net was working, reporting the site is still down, and asks whether Debian (.deb) packages for Bitcoin are available.
Liberty Standard notifies Satoshi that the Bitcoin website is down, showing a bitweaver TEST mode warning instead of the normal page.
Satoshi Nakamoto's post: "Welcome to the new Bitcoin forum!".
Satoshi Nakamoto's post: "Repost: Bitcoin Maturation".
Satoshi Nakamoto's post: "Repost: Request: Make this anonymous?".
Satoshi Nakamoto's post: "Repost: How anonymous are bitcoins?".
Satoshi Nakamoto's reply in the thread "Repost: Linux/UNIX compile".
madhatter starts a discussion: A few suggestions.
SmokeTooMuch starts a discussion: Questions about Bitcoin.
Bitcoin v0.2 was released on SourceForge, introducing Linux support, multi-processor mining, proxy support for Tor, and GUI improvements contributed by Martti Malmi.
Satoshi Nakamoto's post: "Bitcoin 0.2 released!".
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin 0.2 released".
Satoshi Nakamoto's reply in the thread "Is my second Transaction working correctly?".
madhatter starts a discussion: 64bit support.
madhatter starts a discussion: TOR and I2P.
Satoshi Nakamoto's reply in the thread "Number of connections?".
riX starts a discussion: Bitcoin crash when sending coins.
Satoshi discusses the difficulty of applying traditional tax frameworks to Bitcoin, noting the similarities to trading precious metals or collectibles online.
Satoshi Nakamoto's reply in the thread "Blocks never stop generating?".
Satoshi Nakamoto's reply in the thread "Payment server".
Satoshi Nakamoto's reply in the thread "A newb's test - anyone want to buy a picture for $1?".
Sabunir starts a discussion: Questions about Addresses.
Satoshi Nakamoto's reply in the thread "Win32 CPU Cycles vs 'Live Protection' Engines?".
NewLibertyStandard proposes adopting the Thai baht symbol (฿) as Bitcoin's symbol and BTC as the three-letter code on BitcoinTalk, establishing the notation still in use today.
Satoshi Nakamoto's post: "Proof-of-work difficulty increasing".
Satoshi Nakamoto's reply in the thread "How divisible are bitcoins and other market/economic questions".
Martti Malmi (sirius) starts a discussion: Make your "we accept Bitcoin" logo.
Satoshi Nakamoto's post: "Bitcoin client and website translation".
Satoshi Nakamoto's reply in the thread "Simple to implement feature requests".
theymos starts a discussion: What's with this odd generation?.
nphyx starts a discussion: DEB Package?.
Satoshi Nakamoto's reply in the thread "Setting up multiple bitcoin machines behind NAT".
ec starts a discussion: URI-scheme for bitcoin.
Suggester starts a discussion: The current Bitcoin economic model doesn't work.
Satoshi Nakamoto's reply in the thread "Number of connections".
Satoshi Nakamoto's post: "Post your static IP".
Satoshi Nakamoto's post: "UI improvements".
NewLibertyStandard starts a discussion: Bitcoin Address Collisions.
Satoshi Nakamoto's reply in the thread "generation slowed down dramatically".
Satoshi Nakamoto's post: "Command Line and JSON-RPC".
Satoshi Nakamoto's post: "New icon/logo".
Satoshi Nakamoto's reply in the thread "wxWidgets 2.9.0".
Satoshi Nakamoto's reply in the thread "Money Transfer Regulations".
fergalish starts a discussion: bitcoin auto-renice-ing.
soultcer starts a discussion: On IRC bootstrapping.
Satoshi Nakamoto's post: "Idea for file hosting and proxy services".
Satoshi Nakamoto's reply in the thread "who is bitcoin.com".
Satoshi Nakamoto's reply in the thread "Exchange Methods".
Hanyecz recalls his Satoshi correspondence around the April 19, 2010 macOS port. The private emails are unreleased; quotes are from later interviews. He called Satoshi paranoid, bossy, and weird.
Hanyecz recalls Satoshi's private pushback on his May 10, 2010 BitcoinTalk GPU-mining announcement. The verifiable element is the announcement; Satoshi's side comes from Hanyecz's later interviews.
Satoshi Nakamoto's reply in the thread "Could the bitcoin network be destroyed...".
Satoshi Nakamoto's reply in the thread "For a website taking payments with bitcoins...".
Satoshi Nakamoto's reply in the thread "Exception: 9key_error error".
Satoshi Nakamoto's reply in the thread "removing bitcoin addresses".
Hanyecz recalls Satoshi reciprocating his GPU miner code by sharing his own GPU mining code, kept as defense against potential 51% attacks rather than for mining. From later interviews.
Satoshi Nakamoto's reply in the thread "Is there a way to automate bitcoin payments...".
Satoshi Nakamoto's reply in the thread "Ummmm... where did my bitcoins go?".
Satoshi Nakamoto's reply in the thread "We accept Bitcoins".
NewLibertyStandard starts a discussion: Bitcoin in Ubuntu 10.04.
HostFat starts a discussion: Website and software translations.
Satoshi Nakamoto's reply in the thread "Tracing a coin's lineage".
Satoshi Nakamoto's reply in the thread "CLI bitcoin generation".
Satoshi Nakamoto's reply in the thread "Odd amount of generated coins".
Gavin Andresen begins corresponding with Satoshi after discovering Bitcoin in May 2010 and starts submitting code contributions. He creates the Bitcoin Faucet to give away free BTC and boost adoption.
lachesis starts a discussion: Dealing with SHA-256 Collisions.
Satoshi Nakamoto's reply in the thread "Hostnames instead of IP Addresses".
Satoshi Nakamoto's reply in the thread "Technical clarifications".
Satoshi Nakamoto's reply in the thread "What is the incentive to collect transactions?".
Gavin Andresen starts a discussion: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG.
Satoshi Nakamoto's reply in the thread "new binary release?".
Satoshi Nakamoto's reply in the thread "Get 5 free bitcoins from freebitcoins.appspot.com".
Satoshi Nakamoto announces version 0.3 is almost ready and requests testing of the Mac version.
Satoshi Nakamoto's reply in the thread "How fast do the fastest computers generate bitcoins?".
llama starts a discussion: Major Meltdown.
Xunie starts a discussion: Bitcoin clients getting k-lined from the IRC bootstrapping channel.
Satoshi Nakamoto starts a discussion: Beta?.
Satoshi Nakamoto's reply in the thread "Bitcoin mobile.".
Satoshi Nakamoto's reply in the thread "Building BitCoin Client completely Headless".
Satoshi Nakamoto's reply in the thread "Bitcoin Faucet changes".
Satoshi Nakamoto's reply in the thread "IPv6, headless client, and more".
lachesis starts a discussion: Feature Request: Limiting Connections.
Satoshi critiques a Slashdot submission draft, rejecting the 'anonymous' framing and 'stable-with-respect-to-energy' claims, noting how hard it is to describe Bitcoin for general audiences.
Bitcoin v0.3 was released on SourceForge with JSON-RPC control, a daemon version, Mac OS X support, and 20% faster hashing, coinciding with the famous Slashdot posting.
Satoshi warns Malmi to de-emphasize Bitcoin's anonymity claims, distinguishing between anonymity and pseudonymity - a prescient warning about privacy expectations.
Satoshi Nakamoto's post: "Bitcoin 0.3 released!".
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin 0.3 released!".
m0mchil starts a discussion: bitcoin 0.3 win64 - broken access to APPDATA if non-latin characters in username.
Satoshi Nakamoto's reply in the thread "Anonymity".
Satoshi Nakamoto's reply in the thread "BTC Vulnerability? (Massive Attack against BTC system. Is it really?)".
Satoshi Nakamoto's reply in the thread "Security".
Slashdot, an influential tech news site at the time, publishes an article about Bitcoin v0.3. The Slashdot effect causes a surge in downloads — Bitcoin's first major mainstream tech media exposure.
jib starts a discussion: Scalability.
Mionione starts a discussion: Flood attack 0.00000001 BC.
knightmb starts a discussion: Runaway CPU usage for 64bit BitCoin (Linux Client).
andy_3_913 starts a discussion: resource hog.
Giulio Prisco starts a discussion: They want to delete the Wikipedia article.
Satoshi Nakamoto's reply in the thread "No blocks downloaded... why?".
Satoshi Nakamoto's reply in the thread "stopped prodicing coins".
Satoshi Nakamoto's reply in the thread "Building Bitcoin 0.3".
Satoshi Nakamoto's reply in the thread "Stuck on 513 blocks".
Satoshi Nakamoto's reply in the thread "Error on Ubuntu 10.04".
Satoshi Nakamoto's reply in the thread "Warning this block was not received by any other nodes".
Satoshi Nakamoto's reply in the thread "Hash/sec Throttling for Democracy".
Satoshi Nakamoto starts a discussion: Bitcoin 0.3.1 released.
EricJ2190 starts a discussion: "SetIcons(): icon bundle doesn't contain any suitable icon".
AndrewBuck starts a discussion: Source code documentation.
Satoshi Nakamoto's reply in the thread "[Bitcoin 0.3.0] Runtime error".
Satoshi Nakamoto's reply in the thread "Static Linux x86_64 bins for those having libcrypto troubles".
singpolyma starts a discussion: Assertion Failure - Ubuntu Lucid.
Satoshi Nakamoto's reply in the thread "Donations to freebitcoins.appspot.com needed!".
Satoshi Nakamoto's reply in the thread "Fedora 13 libcrypto".
Satoshi Nakamoto's reply in the thread "Resending transaction".
Satoshi Nakamoto's reply in the thread "Hash() function not secure".
Satoshi Nakamoto's reply in the thread "Request: expected bitcoins per day display".
Insti starts a discussion: Bitcoin snack machine (fast transaction problem).
Satoshi Nakamoto's reply in the thread "The dollar cost of bitmining energy".
Satoshi Nakamoto's reply in the thread "Website integration for bitcoin".
Satoshi Nakamoto's post: "Sample account system using JSON-RPC needed".
Satoshi Nakamoto's reply in the thread "A New Currency System for the World".
wobber starts a discussion: Nenolod, the guy that wants to prove Bitcoin doesn't work..
Satoshi Nakamoto's reply in the thread "BUG Report: Rounding glitch".
Satoshi Nakamoto's reply in the thread "Privacy versus Safety: handling change".
Satoshi Nakamoto's post: "Bitcoin 0.3.2 released".
Satoshi Nakamoto's reply in the thread "Network Size".
Satoshi Nakamoto's post: "JSON-RPC password".
Satoshi Nakamoto's reply in the thread "MSVC build & SHA-256".
Satoshi Nakamoto's reply in the thread "Did block generation crawl to a halt?".
Satoshi Nakamoto's post: "Warning: don't use -server or bitcoind where you web browse (v0.3.2 and lower)".
mtgox starts a discussion: bitcoind not responding to RPC.
Satoshi Nakamoto's post: "Faster initial block download (5x faster)".
Satoshi Nakamoto's reply in the thread "JSON-RPC Multiple Invocations".
Satoshi Nakamoto's post: "Version 0.3.2.5 -- please test!".
Satoshi Nakamoto's reply in the thread "Reading/Writing Blocks and FLATDATA".
lfm starts a discussion: a simple traffic load test run.
Red starts a discussion: Stealing Coins.
Satoshi Nakamoto's post: "Bitcoin 0.3.3 released -- PLEASE UPGRADE".
Satoshi Nakamoto's reply in the thread "md5?".
Olipro starts a discussion: Bitcoin x86 for Windows.
Satoshi Nakamoto's post: "bitcoind without wxWidgets".
Satoshi Nakamoto's reply in the thread "Bitcoin x64 for Windows".
xc starts a discussion: Bitcoin does NOT violate Mises' Regression Theorem.
psyvenrix starts a discussion: Having problems specifing -datadir.
Odin starts a discussion: Linux distribution download.
Satoshi Nakamoto's reply in the thread "Build error SVN r115 on my Mac: workaround".
Satoshi Nakamoto's reply in the thread "Difficulty".
Satoshi Nakamoto's reply in the thread "Scalability and transaction rate".
Satoshi Nakamoto's reply in the thread "wiki registration email?".
Satoshi Nakamoto's post: "*** ALERT *** Upgrade to 0.3.6".
Satoshi Nakamoto's reply in the thread "Implementation bug prior to 0.3.6".
Satoshi Nakamoto's reply in the thread "Transaction disappeared in the void...".
Satoshi Nakamoto's post: "[bitcoin-list] Alert: upgrade to bitcoin 0.3.6".
Olipro starts a discussion: A proposal for a semi-automated Escrow mechanism.
tcatm starts a discussion: 4 hashes parallel on SSE2 CPUs for 0.3.6.
Satoshi Nakamoto's reply in the thread "Bug: "Immature" coins lost in wallet.dat during transaction".
Satoshi Nakamoto's reply in the thread "[PATCH] implement 'listtransactions'".
Satoshi Nakamoto's post: "Webpage idea: Next predicted difficulty change".
bytemaster starts a discussion: Multiple Wallets, one computer (multiple accounts).
Satoshi Nakamoto's reply in the thread "Linux version => No GUI after upgrade. WTF?".
Satoshi Nakamoto's reply in the thread "Mac Client Problems Outlined...".
Satoshi Nakamoto's reply in the thread "Protocol Buffers for Bitcoin".
nimnul starts a discussion: Bitcoind x86 binary for CentOS.
MoonShadow starts a discussion: Bitcoin Watchdog Service.
Satoshi Nakamoto's reply in the thread "Builds for Ubuntu?".
Satoshi Nakamoto's reply in the thread "Content-Length header and 500".
Satoshi Nakamoto's reply in the thread "What happens when network is split for prolonged time and reconnected?".
Satoshi Nakamoto's post: "Please upgrade to 0.3.8!".
Satoshi Nakamoto's reply in the thread "Building initial transaction trust through "coin ripping"".
gridecon starts a discussion: Bitcoin minting is thermodynamically perverse.
Satoshi Nakamoto's reply in the thread "Who's the Spanish jerk draining the Faucet?".
Satoshi Nakamoto's reply in the thread "bitcoind transaction to ip address".
Satoshi Nakamoto's reply in the thread "Transaction Overload Solution".
Satoshi Nakamoto's reply in the thread "latency and locality".
lfm starts a discussion: bitcoin generation broken in 0.3.8? (64-bit).
Satoshi Nakamoto's post: "Escrow".
Satoshi Nakamoto's post: "Version 0.3.8.1 update for Linux 64-bit".
Satoshi Nakamoto's reply in the thread "What could be the transition plan to Y2038 compliant Bitcoin?".
Red starts a discussion: Not a suggestion.
Satoshi Nakamoto's post: "Connection limits".
Satoshi Nakamoto's reply in the thread "Compile error in SVN r127".
dkaparis starts a discussion: BSD detection.
Satoshi Nakamoto's reply in the thread "Lost large number of bitcoins".
Satoshi Nakamoto's reply in the thread "Where is the separate discussion devoted to possible Bitcoin weaknesses.".
Satoshi Nakamoto's post: "Bugfixes in SVN rev 130".
Satoshi Nakamoto's post: "Version 0.3.9 rc1, please test".
Satoshi Nakamoto's reply in the thread "Proposed change to sendtoaddress API call".
gebler starts a discussion: Potential disaster scenario.
Structural reading of the 2010-08-15 overflow incident — soft-fork rescue mechanics, why a 5-hour response was only achievable then, transaction-shape forensics, and the centralization paradox.
Emergency release of Bitcoin v0.3.10 to fix a value overflow vulnerability exploited to create 184 billion bitcoins in a single transaction. Satoshi coordinated the rapid soft-fork deployment.
Satoshi Nakamoto starts a discussion: tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10.
lfm starts a discussion: overflow bug SERIOUS.
Original thread starter post. The content was later deleted by the author.
An integer overflow bug (CVE-2010-5139) was exploited to create 184 billion BTC in Block 74638. Satoshi published a fix within 5 hours; the corrected chain overtook the invalid one within 15 hours.
Satoshi Nakamoto's post: "[bitcoin-list] ALERT - we are investigating a problem".
Satoshi Nakamoto's post: "Version 0.3.10 - block 74638 overflow PATCH!".
mkrogh starts a discussion: checkpointing the block chain.
Quoted post by satoshi in BitcoinTalk topic 832.
Satoshi Nakamoto's post: "blocks minus 1".
Satoshi Nakamoto's post: "Checking the block chain on load".
kosovito starts a discussion: 28 days without generation, i have 4200khash/s.
Satoshi Nakamoto's reply in the thread "New screenshots to the front page?".
Satoshi Nakamoto's reply in the thread "Difficulty: More nodes active, or faster nodes?".
Satoshi Nakamoto's reply in the thread "Convert Bitcoin to GTK: Yes? No? wx is better?".
Satoshi Nakamoto's reply in the thread "HOWTO: Compiling Bitcoin on Ubuntu 10.04 (Karmic)".
Satoshi Nakamoto's post: "Need a post writing up some things users should know".
Satoshi Nakamoto's reply in the thread "Hypothetical question on lost coins / transfers".
Satoshi Nakamoto's post: "Development of alert system".
Satoshi Nakamoto's reply in the thread "integrating digital payments into p2p protocols".
Jeff Garzik starts a discussion: RFC: remove DB_PRIVATE flag.
nelisky starts a discussion: auto backing up of wallet.dat.
Satoshi Nakamoto's reply in the thread "Gentoo Linux Ebuild".
Satoshi Nakamoto's reply in the thread "New web service: obtain dump of bitcoin block NNNN".
Satoshi Nakamoto's reply in the thread "Bitcoins are most like shares of common stock".
Satoshi Nakamoto's post: "Version 0.3.11 with upgrade alerts".
Satoshi Nakamoto's reply in the thread "Big endian code problems".
icaro starts a discussion: Warning : Check your system clock (help me).
In September 2010, Satoshi privately tells Andresen he is working on other projects — the earliest documented signal of his intent to step back. He soon handed Andresen the repository and alert key.
Satoshi Nakamoto's reply in the thread "CryptoPP Assertion Error".
Jeff Garzik starts a discussion: Always pay transaction fee?.
Satoshi Nakamoto's reply in the thread "HTTP status codes from the JSON-RPC api".
Satoshi Nakamoto's reply in the thread "bitcoind as daemon in OSX".
Bitcoin v0.3.12 was released on SourceForge with important bug fixes and improvements including key pool feature for safer wallet backups and various network stability enhancements.
Satoshi Nakamoto's post: "Version 0.3.12".
Satoshi Nakamoto's reply in the thread "Bitcoin Blogger: Is It Better To Buy Or Generate Bitcoins?".
Satoshi Nakamoto's post: "Auto-detect for 128-bit 4-way SSE2".
Original thread starter post. The content was later deleted by the author.
Satoshi Nakamoto's reply in the thread "Running on a port other than 8333".
Satoshi Nakamoto's reply in the thread "Switch to GPL".
eurekafag starts a discussion: Memory leak.
Satoshi Nakamoto's reply in the thread "Issues building bitcoin on Windows 7".
Satoshi Nakamoto's reply in the thread "Bug? /usr/bin/bitcoind """.
Satoshi Nakamoto's reply in the thread "The case for removing IP transactions".
Satoshi Nakamoto's reply in the thread "Message Encryption as a built-in feature?".
Satoshi Nakamoto's post: "Internal version number".
Satoshi Nakamoto's reply in the thread "How divisible are bitcoins - the technical side".
Satoshi Nakamoto's reply in the thread "How To Make a Distributed BitCoin Escrow Service".
kermit starts a discussion: I broke my wallet, sends never confirm now..
Jeff Garzik starts a discussion: Prioritized transactions, and tx fees.
Satoshi Nakamoto's post: "0.3.13 RC1 for Windows, please test".
Satoshi Nakamoto's reply in the thread "BitCoin Wikipedia page DELETED!!!".
Satoshi Nakamoto's reply in the thread "Remote RPC access".
Satoshi Nakamoto's post: "Version 0.3.13, please upgrade".
m0mchil starts a discussion: python OpenCL bitcoin miner.
Jeff Garzik starts a discussion: [PATCH] increase block size limit.
Satoshi Nakamoto's reply in the thread "How to overthrow the GPU Oligarchs".
Satoshi Nakamoto's reply in the thread "Tor connections not working reliably, many seednodes offline".
Satoshi Nakamoto's reply in the thread "The Niche List".
Satoshi Nakamoto's post: "Key pool feature for safer wallet backup".
Dhaw starts a discussion: ERROR - PLEASE HELP ME!.
Satoshi Nakamoto's post: "Version 0.3.14".
Odin starts a discussion: Win7 64bit since last patch Tues now crashes.
Satoshi Nakamoto's reply in the thread "Suggestion: Allow short messages to be sent together with bitcoins ?".
genjix starts a discussion: Wikileaks contact info?.
Satoshi Nakamoto's reply in the thread "Some testing that I did on the testnetwork, my findings.".
Satoshi Nakamoto's post: "Version 0.3.15".
appamatto starts a discussion: BitDNS and Generalizing Bitcoin.
Satoshi Nakamoto's reply in the thread "Need OP_BLOCKNUMBER to allow 'time' limited transactions".
Jeff Garzik starts a discussion: Transaction / spam flood attack currently under way.
Satoshi Nakamoto's post: "New getwork".
Jeff Garzik starts a discussion: RFC: ship block chain 1-74000 with release tarballs?.
Satoshi Nakamoto's post: "Version 0.3.17".
Satoshi Nakamoto's reply in the thread "New demonstration CPU miner available".
Satoshi Nakamoto's reply in the thread "Cooperative mining".
Satoshi Nakamoto's reply in the thread "Is safe running bitcoins with the same wallet on more computers simultaneously?".
When Malmi asks who should take over Bitcoin development, Satoshi recommends Gavin Andresen as 'responsible, professional' — early signal of the transition formalized by the December 12 SVN handover.
Bitcoin v0.3.18 was released on SourceForge, one of Satoshi's last releases, featuring wallet compatibility fixes and Gavin Andresen's accounts-based JSON-RPC commands.
davux starts a discussion: JSON-RPC method idea: list transactions newer than a given txid.
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin 0.3.18 is released".
Satoshi Nakamoto's post: "Version 0.3.18".
Satoshi Nakamoto's reply in the thread "Automated nightly builds".
Satoshi Nakamoto describes a possible design for transaction replacement — a higher-fee double-spend replacing the original. Later known as Replace-by-Fee (RBF). Peter Todd replied ~1.5 hours later.
Satoshi Nakamoto's post: "Accounts example code".
One of Satoshi's last posts. After WikiLeaks begins accepting Bitcoin donations, Satoshi expresses concern that Bitcoin has 'kicked the hornet's nest' too early.
Satoshi Nakamoto gives Gavin Andresen control of the source code repository and endorses him to lead the Bitcoin project. Andresen publicly announces the transition on the Bitcointalk forum.
Satoshi's last known public post on BitcoinTalk. He discusses software updates and then disappears from public communication.
Satoshi Nakamoto's post: "[bitcoin-list] Bitcoin 0.3.19 is released".
Bitcoin v0.3.19 was released on SourceForge as Satoshi Nakamoto's final release, adding DoS protections and removing safe mode alerts before his departure.
Gavin Andresen announces on BitcoinTalk topic 2367 he is taking over active project management of Bitcoin with Satoshi's blessing. Same day, he creates the bitcoin/bitcoin GitHub repo.
Gavin Andresen publicly announces taking on active project management for Bitcoin with Satoshi's blessing, creating the bitcoin/bitcoin GitHub staging tree and proposing a development process.
Gavin warns that distributing the forum database would betray registered users' trust, supports daily PGP-encrypted backups, and offers to pay for Amazon S3 storage if backups stay under a gigabyte.
When correspondents wished Satoshi merry Christmas, predicted Bitcoin at $10M per coin, or hoped he was doing well, his replies opened on the technical topic and never returned. Five-pattern audit.
Mike Hearn asks about the origin of the 21 million coin limit, the 10-minute block target, and the 500KB block size limit while working on a Java SPV implementation for Android.
Satoshi's last email in the Malmi archive (Feb 22, 2011). Reply to Gavin (Martti in third person), handing over the bitcoin-list mailman password as PGP blocks to each.
Mike Hearn announces the open-source release of BitcoinJ under the Apache 2 license, and asks about merkle branch verification, scripting language ideas, and why transaction replacement was disabled.
Mike Hearn describes his work on Google's abuse team and proposes using Bitcoin as collateral against accounts for spam prevention, asking about time-locking coins.
One of the first major print magazine features on Bitcoin. Greenberg interviews Andresen, who calls Bitcoin "better gold than gold." The mainstream attention may have driven Satoshi's withdrawal.
Mike Hearn's private email correspondence with Satoshi Nakamoto, in which Satoshi stated he had 'moved on to other things' and that Bitcoin was 'in good hands with Gavin and everyone.'
Gavin Andresen replies to Satoshi's final email, accepting the alert key and disclosing that he has been invited to present Bitcoin to US intelligence agencies. Satoshi never replies to this message.
Satoshi's final known private messages: April 23, 2011 to Mike Hearn — "in good hands with Gavin." April 26 to Andresen, transferring the alert key and saying he would probably be unavailable.
Satoshi's last known private email. He transfers the Bitcoin network alert key to Gavin Andresen, asks him to stop portraying him as a 'mysterious shadowy figure,' and says he has moved on.
Gavin Andresen announces he has been invited to give a presentation about Bitcoin at the CIA, which may have contributed to Satoshi's subsequent withdrawal from the project.
Nick Szabo's May 2011 blog post on why digital cash took thirteen years between bit gold (1998) and Bitcoin (2009). Names libtech as the private list where bit gold and b-money developed in parallel.
WikiLeaks announces Bitcoin donations, bypassing the Bank of America/Visa/MasterCard/PayPal/Western Union blockade. Satoshi had warned against this six months earlier, fearing government attention.
The hypothesis that Len Sassaman (cypherpunk cryptographer, died July 3, 2011) was Satoshi. Frame: timing argument and cypherpunk credentials. Counter: no direct documentary link, no widow comment.
The Bitcoin Forum, set up by Martti Malmi at bitcoin.org/smf, migrates to the independent bitcointalk.org domain in August 2011. Theymos managed the migration; all posts and accounts were preserved.
Security researcher Dan Kaminsky tries to find vulnerabilities in Bitcoin and fails. "I came up with beautiful bugs. But every time I went after the code there was a line that addressed the problem."
On November 20, 2011, Bitcoin v0.5 shipped with the Crypto++ SHA-256 subset removed and replaced by OpenSSL. Wei Dai's library, a direct codebase dependency since v0.1, was gone.
Benjamin Wallace's Wired feature — an early major mainstream article on Bitcoin. Traces the whitepaper, mining boom, Mt. Gox hack, and growing pains, ending with Garzik's "We really don't care."
Hal Finney's famous retrospective on his early involvement with Bitcoin, his interactions with Satoshi, and his battle with ALS. One of the most celebrated posts in Bitcoin history.
Sergio Demian Lerner published The Well Deserved Fortune of Satoshi, identifying a distinctive mining pattern (later named Patoshi) linking ~22,000 blocks (~1.1M BTC) to a single miner.
The Japanese-language hypothesis that Isamu Kaneko (Winny P2P developer, prosecuted from 2004, died July 2013) was Satoshi. Counter: criminal-case scrutiny, English-register difference.
Five months after his ExtraNonce analysis, Lerner discovered Satoshi's nonce values had a non-random LSB distribution — a second fingerprint of custom mining software with nonce partitioning.
The hypothesis that Nick Szabo (Bit Gold creator, "smart contracts" coiner) was Satoshi. Frame: Skye Grey 2013 stylometric article. Counter: Szabo's 2008 Bit Gold help request and self-denials.
On December 1, 2013, blogger Skye Grey published Satoshi Nakamoto is (probably) Nick Szabo — the first public stylometric study naming Szabo as Satoshi, reported by TechCrunch on December 5.
Wei Dai's LessWrong Q&A reflections: Satoshi did not read the b-money paper before reinventing the idea, and Dai had grown disillusioned with cryptoanarchy by the time he wrote it up.
The 2014 Newsweek cover story naming Dorian Nakamoto as Satoshi on his birth name alone. He denied it, the Satoshi account posted 'I am not Dorian Nakamoto,' and no technical link exists.
Newsweek publishes 'The Face Behind Bitcoin,' identifying Dorian Prentice Satoshi Nakamoto, a 64-year-old Japanese-American man living in Temple City, California, as Bitcoin's creator.
About 24 hours after Newsweek named Dorian Nakamoto as Bitcoin's creator, Satoshi's dormant P2P Foundation account posted a one-sentence denial. The post's authenticity has been debated since.
Editorial reading of how the 2014 'Bitcoin Core' rebrand reshaped Bitcoin's authority vocabulary — PR #3408 internal disagreement, the 2015-2017 fork episodes, and Hearn's 2025 retrospective regret.
The hypothesis that Hal Finney — RPOW author and Dorian Nakamoto's Temple City neighbor — was Satoshi. Frame: Greenberg 2014 Forbes "Nakamoto's Neighbor." Counter: April 18, 2009 race-day alibi.
March 25, 2014 Forbes feature by Andy Greenberg visiting Hal and Fran Finney in Temple City, examining the Hal-as-Satoshi geographic theory and publishing the April 18, 2009 race-day alibi photos.
Aston University Centre for Forensic Linguistics released Project Bitcoin (April 2014): a stylometric study under Jack Grieve naming Szabo as the most likely whitepaper author among 11 candidates.
Weighing the 'Blockstream controls Bitcoin' charge against the record: where it comes from, the facts behind it, and the counter-facts — Lightning's authorship, funding spread, a shrinking Core role.
On May 15, 2015, the New York Times published Nathaniel Popper's Decoding the Enigma of Satoshi Nakamoto — a Digital Gold excerpt naming Bit Gold designer Nick Szabo as Satoshi. Szabo denied it.
Why Bitcoin's 2015-2017 fork wars ran as identity contests, not OSS disputes: the post-2011 authority vacuum, the economic weight on rule choices, and the three layers that bound code to currency.
BIP 125 formalized opt-in Replace-by-Fee (RBF), tracing directly to Satoshi's December 2010 BitcoinTalk replacement mechanism — the thread where Peter Todd made his second-ever forum post.
Mike Hearn published The Resolution of the Bitcoin Experiment, declaring Bitcoin had failed due to governance breakdown and the block-size stalemate. He sold all his coins and left the project.
On January 15, 2016, Bitcoin Core v0.12 replaced OpenSSL with libsecp256k1 — Wuille and Maxwell's custom elliptic-curve library — for consensus-critical ECDSA verification.
The only Satoshi claim made by its own subject: Craig Wright's 2016 self-identification, its reused-signature 'proof,' and the 2024 COPA ruling that he is not Satoshi and forged evidence.
Craig Wright publicly declared himself Satoshi in BBC, Economist and GQ interviews. His blog cryptographic proof was quickly debunked — he had reused a 2009 transaction signature.
Gavin Andresen, who was given commit access to Bitcoin by Satoshi and became the lead developer, recalls his interactions with Satoshi and the transition of leadership.
Satoshi Nakamoto's P2P Foundation profile shows login activity in late 2016, years after the 'I am not Dorian Nakamoto' post in 2014, sparking renewed speculation about the account's security.
Mike Hearn publishes his private email correspondence with Satoshi Nakamoto, providing valuable insights into Satoshi's thinking about Bitcoin's technical future.
Ray Dillinger's retrospective on his role in Bitcoin's earliest days: reviewing the blockchain code, his division of labor with Hal Finney, and his reflections on Satoshi's integrity.
A 2017 blog post by a former SpaceX intern claimed Elon Musk is Satoshi. It rests on personality and skill pattern-matching with no forensic link, and Musk denied it within a week.
Tim Swanson's comprehensive interview with Ray Dillinger for the Bitcoin whitepaper's 10th anniversary. Dillinger reveals technical details of his code review, including the floating-point discovery.
Jeff Garzik, one of Bitcoin's earliest core developers, reflects on his work with Satoshi. He discovered Bitcoin via a July 2010 Slashdot post and became one of the top three contributors.
Evan Ratliff's 2019 The Mastermind named Paul Le Roux — E4M author turned criminal kingpin — as a Satoshi candidate, on capability, covertness, and motive. No link to Bitcoin in the record.
Six years after his original analysis, Lerner published The Return of the Deniers and the Revenge of Patoshi, coining the term Patoshi and proving a single PC clock via timestamp-inversion evidence.
Whale Alert independent analysis confirmed Satoshi mined 1,125,150 BTC across 22,503 of the first 54,316 blocks, claiming ~48 computers (later disputed by Lerner's single-PC simulation).
Lerner published The Patoshi Mining Machine, using re-mining simulation to prove Satoshi mined on a single high-end CPU with 5 parallel threads — refuting the Whale Alert claim.
Doncho Karaivanov analyzes 742 activity instances across Satoshi's posts, commits, and emails, plus The Times headline and British spelling, to argue Satoshi was based in London.
CoinDesk published previously unseen Satoshi-Finney emails (obtained via widow Fran Finney): Finney's November 2008 scalability question and Satoshi's personal v0.1 release notice on January 8, 2009.
Multiple blockchain analyses estimate that Satoshi Nakamoto mined approximately 1.1 million bitcoins in Bitcoin's earliest days, with none of these coins having ever been spent.
On February 22, 2021, Evan Hatch published Len Sassaman and Satoshi: a Cypherpunk history on Medium — the most-cited public articulation of the Sassaman = Satoshi Nakamoto hypothesis.
Craig Wright sued bitcoin.org operator Cobra over Bitcoin whitepaper copyright. Cobra refused to reveal his identity, resulting in a default judgment ordering bitcoin.org to remove the whitepaper.
Reykjavik University researchers published the first peer-reviewed PLOS ONE study of the Patoshi pattern, identifying two nonce anomalies (P and Z) and finding the P anomaly in all 64 first blocks.
In a podcast interview, security researcher Dustin Trammell (Druid) describes being possibly the second node on the Bitcoin network — seeing only one other node for hours after first connecting.
Jameson Lopp shows Satoshi deliberately throttled mining capacity, earning ~1.1M BTC when full capacity could have yielded ~2.19M BTC. Anyone claiming Satoshi was greedy hasn't done the math.
SerHack analyzed a pre-release Bitcoin genesis block dated September 10, 2008 — found in source code Satoshi shared in November 2008. The date matched Lehman's $3.9B loss report.
Bitcoins mined in the earliest weeks of Bitcoin's existence in January 2009 are moved for the first time, sparking intense speculation about whether Satoshi Nakamoto is spending coins.
Jameson Lopp argues Hal Finney could not have been Satoshi: on April 18, 2009, Finney was running a 10-mile race in Santa Barbara during a window of Satoshi network activity.
Adam Back reflects on his August 2008 email exchange with Satoshi, his regret at not reading the whitepaper carefully, and his COPA v Wright testimony where the complete chain became public.
During Day 13 of COPA v Wright, Martti Malmi testified via video link and submitted 260 emails (140,000 words) exchanged with Satoshi between May 2009 and February 2011, published on GitHub.
Mike Hearn testifies at the COPA v Wright trial, recounting his direct interactions with Satoshi and describing how Wright failed his technical check questions at a 2016 dinner.
On April 13, 2024, Bas van Dorst published Where is Satoshi?, a large-scale stylometric corpus comparing Satoshi against 75,000+ cryptography mailing-list authors and 70,000+ Reddit commenters.
The COPA v Wright record revealed that Nicholas Bohm — previously known only for a January 2009 bitcoin-list bug report — also exchanged a private series of troubleshooting emails with Satoshi.
Forensicxs published a line-by-line walkthrough of Bitcoin v0.1's 31,794 lines of source code — one of the most detailed public analyses of Satoshi's original codebase, covering all 31 files.
Pete Rizzo investigates the unexplained ~5-day, 8-hour gap between the Genesis Block (January 3, 2009) and Block 1 (January 9, 2009), framing it as one of Bitcoin's enduring unsolved mysteries.
The Peter Todd = Satoshi hypothesis from HBO 2024 "Money Electric." Frame: a Dec 2010 BitcoinTalk thread where Todd seemed to complete a Satoshi post. Counter: Todd was 22 and an undergrad in 2007.
HBO documentary Money Electric (Cullen Hoback) named Peter Todd as a Satoshi candidate, citing a 2010 BitcoinTalk reply about RBF and Todd's later BIP 125. Todd called the claim ludicrous.
Early Bitcoin developer Jeff Garzik released videos detailing his time working with Satoshi, describing the creator as a self-taught, solitary genius who never revealed any personal information.
In a CoinGeek interview, Mike Hearn offers rare reflections on Satoshi's personality — observing he enjoyed experimenting but appeared to grow frustrated when evangelical personalities arrived.
Attorney James A. Murphy filed a 2025 FOIA suit seeking DHS files on Agent Rana Saoud's 2019 claim that investigators interviewed four people believed to be behind Bitcoin.
In an April 2025 interview, P2P Foundation founder Michel Bauwens recalled receiving several emails from Satoshi (who offered him a few bitcoins) and gave a retrospective on Bitcoin's significance.
The hypothesis that Adam Back (Hashcash inventor, first Satoshi contact) was Satoshi. Frame: April 2026 NYT stylometric investigation by Carreyrou. Counter: Back's 2024 COPA v Wright sworn testimony.
On April 8, 2026, the New York Times published John Carreyrou's investigation naming Adam Back as the most likely Satoshi based on stylometric analysis. Back denied the identification.
Finding Satoshi (Tooley / Miele, April 2026) names Hal Finney and Len Sassaman as Bitcoin co-creators — Finney coded, Sassaman wrote the paper. Lopp and Back disputed the timing.
Bitcoin Institute reanalysis of van Dorst's stylometric corpus for the five most-cited candidates. Finding: Szabo top at 4.67th percentile of 12,739 authors; 594 unnamed rank closer; corpus is noisy.
What Satoshi's design assumed about a fee-only future, and the documented debate over whether transaction fees alone can sustain proof-of-work security after the block subsidy ends around 2140.
Which Bitcoin assets are at risk from a cryptographically relevant quantum computer, and what the timeline and migration debate around post-quantum cryptography looks like.
Beginner's visual guide to Bitcoin — 30 terms across 8 chapters, each with a diagram. Coins as UTXOs, transactions as flows, blocks chained by hashes, mining, mempool, longest-chain consensus.
Where Bitcoin's current reality has drifted from Satoshi's design intent: four axes — mining (one-CPU-one-vote to ASIC oligopoly), custody (own keys to exchange IOUs), governance, and scaling.
An anonymous plaintiff sues 39,069 dormant Bitcoin addresses holding ~3.8M BTC under New York's lost-property statute (March 2026). Galaxy Digital ties 21,923 of them to the Patoshi pattern.