LearnBitcoin

The Bitcoin School

For people who want to understand Bitcoin. Not flip it.

Start the Journey

Plain language. Sourced chapters. Live on-chain data from a real node. Huge glossary, Rabbit Holes, and one opinionated Journey from "what is money?" to running a full node. No altcoins, no affiliate links, and no signup needed to read any of it.

From the glossary

Address Reuse

Paying the same Bitcoin address more than once. It hands your full history, in one place, to anyone watching, puts every coin at the address behind one key, and, once that key has signed, leaves later deposits sitting in the open. Modern wallets avoid it by default.

Read full entry

New on the site.

Bitcoin only.

No altcoins. No tokens. No "crypto." Other coins have other sites. We have one.

No bullshit.

No price predictions. No affiliate-bait. No fear marketing. Every chapter cites its sources, and the live on-chain numbers come straight from a full Bitcoin node.

Have fun.

Interactive, opinionated, well-crafted. Rabbit-hole vibes. Built by Bitcoiners for people who want to actually understand.

Down the rabbit hole.

All rabbit holes

Corrected in public.

All corrections
  • Use It Once: Why Reusing a Bitcoin Address Is Dangerous

    It now says fresh addresses shrink the damage without repairing the generator: if a wallet's random numbers were bad, every key it made with them is suspect, which is why the bitcoin.org alert of 11 August 2013 called for new keys from 'a repaired random number generator', not just for new addresses.

    What was wrong
  • Vanity Address

    The requester publishes a public point, the searcher returns an offset, and the requester adds the two to get the full private key, which only the searcher never learns; the entry says so and tells the reader to check the address before funding it. 1BitcoinEater is described as the opposite construction (hand-written text with a computed checksum, no key search, no key) and linked to the burn-address entry, with BitMEX's 3BMEX deposit addresses as the genuine example. The tools are VanitySearch and vanitygen++, with a note that the original vanitygen is Base58-only. Taproot prefixes take the same number of tries but cost more per try, and a service hands over a private key, not a seed.

    What was wrong
  • BIP 360 (Pay-to-Merkle-Root)

    BIP-360 says a P2MR output becomes vulnerable to long-exposure attacks whenever one of its scripts reveals a public key, so the protection depends on not reusing keys. P2MR is a destination for coins that move to it and does nothing for keys that stay exposed. Neither BIP mentions the other, and BIP-361 lists a post-quantum signature BIP as its requirement, which P2MR is not. The entry now says all three.

    What was wrong
Edit this page on GitHub