Keyword reference — entries that mention this term in body prose.
25 entries reference this keyword in body prose.
Cross-cutting reading of iconic Bitcoin losses by mechanism: forgotten password (Thomas), physical disposal (Howells), custody-collapse (QuadrigaCX, Mt. Gox, FTX). Tied to Bitcoin's irreversibility.
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.
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.
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.
James Howells discarded a hard drive with 7,500 BTC in 2013. It is buried in a Newport, Wales landfill. A UK High Court rejected his £600M excavation suit in January 2025.
Stefan Thomas was paid 7,002 BTC in 2011 for a Bitcoin explainer video, stored the keys on a 10-attempt IronKey, and lost the password. By the 2021 NYT report, 2 of 10 attempts remain.
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.
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.
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.
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 blocks are structured, how Merkle trees commit transactions to block headers, and how the most-work chain selection rule resolves forks.
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 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 uses elliptic-curve keys, digital signatures, hash functions, and deterministic derivation to secure ownership without trusted third parties.
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.
Deep-dive into Bitcoin's transaction layer: UTXO lifecycle, transaction structure, Script evaluation, ECDSA and Schnorr signatures, SegWit, and Taproot.
How Bitcoin Core manages keys, constructs transactions, selects coins, estimates fees, and exposes functionality through RPC, REST, and ZMQ interfaces.
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.
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.
How Bitcoin Core persists blocks, maintains the UTXO set, indexes chain state, manages the mempool, prunes historical data, and bootstraps via assumeUTXO.
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).
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).
Adam Back replies to Wei Dai on Cypherpunks, identifying seven monetary-design issues in b-money and proposing Hashcash as the minting mechanism — a substantive analysis ten years before Bitcoin.