October 29, 2025
Linked list? Linked fists!
How blocks are chained in a blockchain
Bitcoin's chain is a header hash — cue pedants, puzzled newbies, and Linked List jokes
TLDR: The post clarifies Bitcoin links blocks via the previous header’s hash, with zeros thanks to proof‑of‑work and quirky byte order. Comments erupted over “Bitcoin vs generic blockchain,” how distribution actually works, and a spicy “it’s just a linked list” meme, making the tech lesson a drama magnet.
Forget the neat “each block stores the last block’s hash” soundbite — the post shows it’s actually the hash of the previous block’s header, and those mysterious trailing zeros come from the proof‑of‑work puzzle plus the funky little‑endian display. Translation: it’s the block’s “front page” fingerprint, not the whole book. And yes, Satoshi’s magic number is just… a vibe. The community did not let that slide. a3w swung in first with a semantic smackdown: it’s not “a blockchain,” it’s the Bitcoin chain — other systems like Hyperledger Fabric don’t use this setup at all. Title police, assemble! Meanwhile, coolThingsFirst asked the civilian question everyone wonders: “Does every device hold the chain?” Cue explainer replies: many network nodes store it, not your toaster. Then a‑dub dropped the meme of the day, joking Bitcoin is basically “a linked list with an O(exp(n)) append cost,” while miners juggle timestamps, nonces (little one‑off numbers), and the coinbase to hit that zero‑heavy hash. The vibe: half the crowd loves the gritty hex dumps and Bitcoin nerdery; the other half is laughing at how arcane this all looks. Semantics vs practicality, jokes vs pedantry — classic crypto comment brawl, and we’re here for it.
Key Points
- •Bitcoin blocks store the double-SHA-256 hash of the previous block’s header, not the entire previous block.
- •A production Bitcoin block begins with a 4-byte magic number (0xf9beb4d9), so the header is bytes 5–84; some APIs omit the magic number.
- •The header hash is computed as SHA256²(header), demonstrated using an OpenSSL command pipeline.
- •Proof-of-work enforces a target with leading zero bits in the header hash; due to little-endian display, these appear as trailing zeros in printed hex.
- •The next block’s header includes the previous header’s hash after the 4-byte version field, and the header’s Merkle root ties the block body to the header.