Satoshi ↔ Hal Finney Correspondence
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.
Entries tagged with this topic. Spans across types and sources — explore connections between people, events, and themes.
53 entries
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.
Martti Malmi's first message to Satoshi: introduces himself as Trickstern from the anti-state.com forum, offers to help with Bitcoin development.
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.
Liberty Standard notifies Satoshi that the Bitcoin website is down, showing a bitweaver TEST mode warning instead of the normal page.
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).
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 12 email to Finney, and dense activity cadence.
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?'
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.
Satoshi tells Finney that he cannot receive incoming connections from his location, revealing an operational constraint in the earliest days of the Bitcoin network.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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 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.
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.
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.
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 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.
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.
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.
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.
Satoshi warns Malmi to de-emphasize Bitcoin's anonymity claims, distinguishing between anonymity and pseudonymity - a prescient warning about privacy expectations.
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.
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.