12 entries
Satoshi Nakamoto's earliest known email. He contacts Adam Back to verify the correct citation for the Hashcash paper and shares a pre-release draft titled 'Electronic Cash Without a Trusted Third Party' (ecash.pdf).
Satoshi emails Wei Dai asking about the correct citation for b-money, revealing that he learned of b-money from Adam Back's reference. The email included a link to the pre-release draft 'Electronic Cash Without a Trusted Third Party' (ecash.pdf) hosted at upload.ae.
Hal Finney's famous tweet 'Running bitcoin' - marking him as the first known person besides Satoshi to run the Bitcoin software. The next day, he received the first Bitcoin transaction from Satoshi.
Dustin Trammell's first email to Satoshi Nakamoto after downloading and running the Bitcoin alpha release. Trammell reports on his experience running the software, mentions a public timestamp service, and asks about the coin maturity system after seeing generated coins showing 0.00 credit.
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.
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.
Laszlo Hanyecz contributed the first macOS port of Bitcoin and began exchanging emails with Satoshi Nakamoto about development, bug fixes, and technical improvements to the software.
Gavin Andresen begins corresponding with Satoshi Nakamoto after discovering Bitcoin in May 2010 and starts submitting code contributions. He creates the Bitcoin Faucet to give away free BTC and boost adoption.
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.
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.