On-chain artifacts hiding in plain sight
Discovered by scanning a local archival node at block 950,000+. Every artifact here is independently verifiable on any full node, no API keys, no third-party trust.
Bitcoin is mostly numbers. But scattered across fifteen years of blocks are intentional acts of preservation: a newspaper headline, a whitepaper, the first transaction, an absurdly expensive pizza, and hundreds of bitcoin sitting in scripts whose private keys are likely gone forever.
These are not opinions. They are byte sequences any full node will return when you ask for the right block. The scanner that surfaced them is open and reproducible.
Aside on OP_RETURN. The OP_RETURN opcode for arbitrary data did not become a standard relay path until Bitcoin Core v0.9 in March 2014, around block 278,000. Anything labelled as an "OP_RETURN message from 2011" is encoded by a non-canonical channel: fake multisig (like the whitepaper above), fake P2PKH addresses, or coinbase scriptSig payloads. The whitepaper embedding pre-dates standard OP_RETURN by eleven months and used fake multisig precisely because there was no clean primitive yet.
The scan tool is scripts/bitcoin-gems.js, which calls getblockhash(height) and getblock(hash, 2) against a local archival node. No txindex required, because full-block fetch returns every transaction inline.
For each block the scanner classifies every output by script type, totals the P2PK value as a "potentially lost" ledger, and reassembles any data pushes in nonstandard outputs to look for embedded files. The PDF magic byte sequence is how the whitepaper surfaced automatically. No special pattern matching, just bytes.
Every fact on this page is reproducible against any archival Bitcoin full node. The companion tool, scripts/bitcoin-explorer.js, sweeps the chaintip for protocol traffic in modern blocks: OP_RETURN tags, Ordinals inscriptions, sidechain peg messages.