A key is just a very large number
Strip away the mystique and a Bitcoin private key is one thing: a number, chosen at random, between 1 and roughly 1.16 × 10⁷⁷ (2²⁵⁶, give or take). Nobody assigns it to you. Nobody registers it anywhere. It isn't looked up in a database when you "own" it — it's generated, usually by a wallet, and from that moment it either exists somewhere you control or it doesn't exist at all as far as the network is concerned.
From that private key, a short piece of one-way math derives a public key, and from the public key, a Bitcoin address. "One-way" is the load-bearing phrase: it is computationally routine to go private key → public key → address, and computationally infeasible to go backward. Knowing an address — and every address that has ever received bitcoin is sitting in public view on the blockchain — gives an attacker precisely nothing about the private key that controls it. This is the same trapdoor-function idea that secures ordinary web logins; Bitcoin just puts the output of that math in charge of moving money instead of authenticating a session.
What "owning" bitcoin actually means
There is no ledger entry anywhere that says a person's name next to a coin. Ownership, in Bitcoin, is entirely reducible to one fact: whoever can produce a valid digital signature from a private key can spend the coins associated with its address. That's it. Not "whoever the exchange's database says owns the account." Not "whoever can answer a security question." Whoever holds the key.
This cuts both ways, and the downside is the part people learn about the hard way. A bank can reverse a fraudulent transfer, freeze a compromised account, or reset a forgotten password because a bank is a company with a database it controls and a legal process behind it. Bitcoin has no equivalent, by design — no customer-support line, no "forgot password," no fraud department, because there is no central party who could do any of that without also being able to move everyone else's coins. A signature that satisfies the protocol's rules is final the moment it's broadcast and confirmed. There is nobody to appeal to.
Not your keys, not your coins — the oldest phrase in Bitcoin, and still the most literally true one.
The only rule
Everything else in this book is arithmetic you can double-check. This one is a practice, not a formula, and it has a single form: never let your private key or seed phrase (the human-readable backup of it, usually 12 or 24 words) exist anywhere someone else can read it — not typed into a website, not photographed, not pasted into a chat message, not read aloud on a phone call, no matter how official the request sounds. Anyone who possesses those words possesses the coins, instantly and irreversibly, with no way for the rightful holder to contest it after the fact.
Scams exploit this rule's one weak point: it depends entirely on the human following it. "Support" agents who ask you to "verify your wallet" by entering your seed phrase, browser extensions that request it to "sync," QR codes that decode to a phishing site's fake recovery flow — the mechanism is always the same trick wearing a different costume, because the actual cryptography has no known shortcut. Nobody has ever broken Bitcoin's signature scheme. Attackers don't need to; it's far easier to ask.
The rule breaks just as badly without any trick at all — a convenient habit is enough. In 2022, the password manager LastPass was breached, and attackers copied customers' encrypted vault backups, including any seed phrases someone had saved there "just to have a backup." Because the vaults were encrypted, the theft wasn't immediate: attackers spent years afterward guessing weak master passwords offline, with no way for LastPass to lock them out once the copies were already gone. By late 2025, the blockchain-forensics firm TRM Labs had traced more than $35 million in stolen cryptocurrency across 150-plus victims directly back to those 2022 vault copies — including a single $150 million theft in January 2024 from Ripple co-founder Chris Larsen. None of those victims had their wallet software or hardware compromised. Their keys were only ever as safe as the weakest password guarding whichever place a copy of them had been allowed to sit.
Why it can't be delegated — including to this site
This is worth making concrete rather than abstract. The tip jar on this site's front page shows a Bitcoin address, an Ethereum address, and a Lightning address — all public, all generated once, all pasted into the page's source as plain receive-only text. There is no code anywhere on why21million.com that asks for, stores, or has ever seen a private key or seed phrase, because a static site with a tip jar has no legitimate reason to want one; it only ever needs an address to receive to, the same way a store only needs your mailing address, not your house key.
That's not a special virtue of this particular site — it's the only honest design for something that doesn't need custody. Any service that does ask for your keys is asking you to trust its servers, its staff, and its solvency the way you'd trust a bank, without a bank's regulatory backstop. Some of the largest losses in Bitcoin's history — Mt. Gox in 2014, roughly 850,000 BTC gone; FTX in 2022, billions in customer funds — were custodial failures, not failures of Bitcoin's cryptography. The coins were never actually "in" the exchange the way cash sits in a vault; the exchange held the keys and the promise. When the promise broke, the coins didn't disappear from the blockchain — they moved to whoever controlled the keys at the time, which by then was no longer the customers who thought they owned them.
None of this makes exchanges categorically unsafe for every purpose — buying and selling still generally requires one. It does mean that "an exchange holds it for me" and "I hold it" are two entirely different risk models wearing the same balance-on-a-screen. Self-custody trades the convenience of a customer-support line for removing the single point of failure that line exists to fix.
What this chapter isn't
This chapter argued for a rule, not for a specific product. It deliberately didn't cover the actual mechanics of hot versus cold, or custodial versus non-custodial, storage — a later chapter takes on that taxonomy directly, and this site's hardware wallet comparison already covers the specific cold-storage devices for readers ready to act on the rule above today. Nor is this legal or financial advice about which custody arrangement suits your situation — that's a judgment only you can make, informed by how much is at stake and how much convenience you're willing to trade for how much finality.