How transactions become a shared ledger
Part 2 of 5. Thousands of computers end up agreeing on the exact same record by checking each other's work and chaining every page to the one before it.
Entries tagged with this topic. Spans across types and sources — explore connections between people, events, and themes.
8 entries
Bitcoin Institute ↔ Satoshi Nakamoto
Part 2 of 5. Thousands of computers end up agreeing on the exact same record by checking each other's work and chaining every page to the one before it.
After Len Sassaman's death (July 3, 2011), security researcher Dan Kaminsky embedded an ASCII-art tribute into the Bitcoin blockchain, announced July 30 and revealed at Black Hat USA 2011.
Mike Hearn reports progress on his Java SPV implementation, describes his approach to block storage on Android, and raises concerns about protocol ossification as the number of implementations grows.
Mike Hearn reports testing Bitcoin on Mac via Wine, asks about block counts, confirmation times for micropayments, proof-of-work coordination, and difficulty adjustment.
Hal Finney ↔ Satoshi Nakamoto, Jonathan Thornburg
Finney responds: Bitcoin has no single point of failure — 'no mint, no officers to subpoena.' The 'decentralized, irreversible transaction database' is the core innovation, foreshadowing blockchain.
Bitcoin Institute ↔ Satoshi Nakamoto, Craig Wright
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.
Bitcoin Institute ↔ Satoshi Nakamoto
How Bitcoin blocks are structured, how Merkle trees commit transactions to block headers, and how the most-work chain selection rule resolves forks.