Today is the 17th anniversary of the Bitcoin white paper. Satoshi Nakamoto published it on October 31, 2008. The title is Bitcoin: A Peer to Peer Electronic Cash System. It is a nine page document with under three thousand words including references. It explains a system for direct online payments without banks. It solves the double spending problem with a network of computers using proof of work. Many people talk about Bitcoin today. But few read the full paper. Media add ideas and terms that are not there. This created myths and missconceptions. The paper is simple and focused on technical details like hashing, signatures, and CPU power. It uses exact words for its concepts. Here are 21 things people now associate with Bitcoin that are not in the paper. No word blockchain. The word block appears 37 times, often as "block of items" or "block header." The word chain appears 24 times, like in "chain of digital signatures." But blockchain as one word never appears. The paper presents the core idea in different ways to build trust in transaction order. It starts with a timestamp server that hashes a block of items to timestamp them. Then it describes hashing transactions into an ongoing chain of hash based proof of work, forming a record that cannot be changed without redoing the proof of work. It calls this a proof of work chain, where the longest chain serves as proof of the sequence of events. In a figure caption, it shows the solution to the double spending problem as a chain of blocks. The term timechain appears once, referring to the proof of work chain that timestamps transactions. These phrases describe the linked structure without a single buzzword. The modern term blockchain as a single word, now used for many techs beyond Bitcoin, came years later. No claim of total invention. People often say Bitcoin invented digital cash from scratch. But the paper cites earlier work to show it builds on them. The references section lists eight sources, like Wei Dai's 1998 b money paper which proposed a distributed system for creating and transferring digital cash without a central authority. Adam Back's 1997 Hashcash for proof of work to stop email spam by requiring computation. Others include Merkle trees for timestamping from 1987, and digital cash ideas from 1983 and 1993. The abstract says "we propose a solution to the double spending problem using a peer to peer network." This humility shows Bitcoin as an improvement on unsolved issues in prior systems, not a lone genius idea. No word decentralized. Bitcoin is hailed as the ultimate decentralized money. But the paper never uses "decentralized." It describes a "peer to peer distributed timestamp server" to generate proof of chronological order. The network has "minimal structure," with no central authority. Nodes broadcast messages on a "best effort basis" and can leave or rejoin at will, accepting the longest proof of work chain as what happened while gone. This setup avoids trust in one party but focuses on technical reliability, not politics. No mining. Miners are central to Bitcoin stories now, with rigs and farms. But the paper says nodes "generate new coins" as the first transaction in a block, owned by the creator. This happens by solving proof of work, which requires scanning for a nonce so the block hash starts with zero bits. It adds incentive to support the network. No "mining" term, no rewards explained beyond new coins. The analogy to gold mining appears only briefly. No full anonymity. Bitcoin is often called anonymous money for dark web use. But the paper says "the necessity to announce all transactions publicly precludes full anonymity." It keeps public keys anonymous so people see amounts sent but not who. Public keys act as pseudonyms, and using a new key pair per transaction breaks links. But multi input transactions can reveal if inputs belong to the same owner. This basic pseudonymity is like stock trade tapes showing size and time but not names. No 21 million cap stated. Bitcoin's fixed supply of 21 million is a key selling point for scarcity. But the paper mentions "once a predetermined number of coins have entered circulation," then incentives shift to fees for inflation free system. No number given, no math for total. The 21 million comes from later code: starting at 50 coins per block, halving every 210,000 blocks (50 210,000 (1 + 1/2 + 1/4 + ... ) = 21 million). The paper implies a cap but leaves details out, focusing on incentives. No specific coin issuance schedule or halving events. The paper talks of "steady addition of a constant amount of new coins," like gold miners adding to circulation via CPU and electricity. It transitions to fees after the predetermined number. But no initial 50 coins, no halving every four years, no block count like 210,000. These are in the 2009 source code, represented as a mathematical formula where reward = 50 >> (blocks / 210000). The paper keeps it high level for the incentive model. No Sybil attacks term. Proof of work is said to stop fake node floods now called Sybil attacks. But the paper explains it prevents subversion if majority was "one IP address one vote," as anyone could allocate many IPs. Instead, proof of work is "one CPU one vote." The majority is the longest chain with greatest effort. No "Sybil" word, coined in 2002 for network fakes. This IP focus shows early internet threats; the broader Sybil idea applied to Bitcoin later in academic papers. No unbreakable security guarantee. Bitcoin is touted as unhackable. But the paper assumes "honest nodes collectively control more CPU power than any cooperating group of attacker nodes." Security holds if honest majority exists. Section 11 models attacker catch up as binomial random walk, like gambler's ruin. Probability of catching from z blocks behind is (q/p)^z, where q is attacker fraction, p honest (over 0.5). It drops exponentially. Without majority, an attacker could rewrite history for his transactions. The "unbreakable" hype ignores this conditional security, that bitcoin is secure as long majority of honest nodes exist. No store of value focus. Bitcoin as "digital gold" for holding is huge now. Nations are considering startegic reserve of it. But the paper calls it "electronic cash" for peer to peer payments, protecting from fraud with irreversible transactions. The gold analogy is only used to describe incentives: steady new coins like miners adding gold via resources. Satoshi's vision was peer to peer spending, not HODLing. No forks defined. Forks split the chain in debates now. The paper says if two blocks arrive at once, nodes save the other branch and switch to the longer one later. This resolves ties naturally. But no "hard fork" (rule change) or "soft fork" (backward compatible) terms. Those arose later, where groups disagreed on rules and created new versions, such as Bitcoin Cash, for example. No wallets. Wallets are everyday Bitcoin tools now, like apps or hardware for keys. But the paper describes electronic coins as "a chain of digital signatures," where owners transfer by signing the previous transaction with their private key and adding the next owner's public key. No software, no seed phrases, no hot/cold storage. Transactions use new key pairs for privacy. No exchanges. Trading Bitcoin for dollars on centralized trading platforms is core now. But the paper focuses on direct peer to peer transfers: send payment by broadcasting a signed transaction to the network. No buying/selling markets, no order books, no fiat on ramps. It assumes users hold coins for spending. Exchanges started in 2010 with Bitcoin Market, exploding post 2013 with Mt. Gox and others, turning Bitcoin into a tradable asset class. No smart contracts. Bitcoin scripts enable basic conditions now, but full DeFi apps are core to some other cryptocurrencies that are not compatible with Bitcoin. The paper covers only simple value transfers via signatures, with inputs/outputs to split/combine amounts. The paper says transactions are irreversible once confirmed in the chain. The idea of smart contracts, which are automatic agreements that run on computer code, was first named in 1996 by Nick Szabo. Bitcoin has a basic version using OP codes. These are small commands built into Bitcoin transactions, but those are still simple and limited. No NFTs. Unique digital art on Bitcoin via Ordinals is trendy now. But the paper treats coins as fungible units in signature chains, all identical. No unique tokens, no metadata in transactions. Fungibility is key for cash like use. A satoshi is the smallest part of a bitcoin, like one hundred millionth of a coin. In 2023, Ordinals started a new way to number each satoshi and add data like pictures or text to one satoshi. This makes that tiny piece unique, like a special collectible card. Some call it a hack because it uses Bitcoin's old rules in a new way to store this data on the main network, not planned in the white paper. No mempool. Unconfirmed transactions wait in the "mempool" now, causing fees spikes. But the paper says nodes relay transactions and add to blocks if valid. No queue term, no spam protection details. It assumes honest relay. Mempool concept from 2010 code, debates on full/rb mempools in 2015 scaling wars, where too many waiting transactions clogged the system and raised costs. No difficulty adjustment. Block times drift now, adjusted every 2016 blocks. But the paper targets 10 minute intervals via proof of work difficulty, scanning nonces until hash meets zeros. No formula for retargeting. Adjustment in 2009 code to stabilize, preventing too fast/slow blocks as more computers joined, keeping the network steady over time. No SegWit or upgrades. Segregated Witness, or SegWit, is a change from 2017 that fixed a problem called malleability, causeing issues for building other tools on Bitcoin. The white paper uses simple transaction IDs based on hashing the whole transaction. Transactions have inputs and outputs with scripts for signatures. SegWit fixed the ID change problem by moving the signature data to a separate part. This makes transactions safer because IDs no longer change easily. It also lets more transactions fit in each block by counting the separate data differently. No quantum resistance. Everyone talks about how quantum computers threaten ECDSA keys now. But the paper relies on SHA 256 for hashing and ECDSA for signatures, top standard in 2008. No future proofing. Quantum risks discussed later, as faster computers could break old math locks. No green energy debate. Proof of work's power use is criticized often by green washers. But the paper sees electricity as proof cost, like gold mining, assuming Moore's Law scales computation. No environmental angle. With hashrate growth, the electricty consumtion peaked, as total energy consumed by the bitcoin network matched some countries. No KYC or regulations. Bitcoin ETFs and licenses are top news now. But the paper assumes consensus on valid blocks via honest majority, no legal nods. Nodes verify independently. Regulations hit 2013 with FinCEN guidance, evolving to 2024 ETF approvals and MICA, forcing users to prove identity for trades. The paper went to the cypherpunk mailing list for privacy advocates. It was not sent to Wall Street or journalists. Bitcoin's simplicity is facinating, but all the complicated stuff came from the Wall Street speculants and mainstream media. Read the nine pages, if you want to understand, it's the real Bitcoin origin.