Bitcoin only.
No altcoins. No tokens. No "crypto." Other coins have other sites. We have one.
The Bitcoin School
For people who want to understand Bitcoin. Not flip it.
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, no newsletter pitch.
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.
New on the site.
Rabbit Hole 40 min
Rat Poison, Tulips and a Pet Rock: Everything Bitcoin's Been Called (so far)
Bitcoin is dead, they said, and a Ponzi scheme, a tulip bubble, rat poison and money for drug dealers and terrorists. Every label, who said it and when, which ones can actually be scored, and what happened next, including the calls that held up and the ones our own side got wrong.
Rabbit Hole 14 min
The 2013 Chain Fork
On 11 March 2013 a software upgrade split Bitcoin into two chains. Developers, pool operators and exchanges argued it out in a public chat room and put it back together in under eight hours. This is the log, with the timestamps.
Rabbit Hole 15 min
How Taproot Actually Works
One key, two doors. How a Taproot output is built, why every one looks the same until it is spent, what Schnorr signatures changed, what Tapscript left open for the future, and what has actually been done with it since 2021, inscriptions included.
Down the rabbit hole.
All rabbit holesHard Questions
The strongest objections, including where the critics are right.
- Quantum and Bitcoin
- Bitcoin and Energy
- Rat Poison, Tulips and a Pet Rock: Everything Bitcoin's Been Called (so far)
Corrected in public.
All corrections-
Automatic bans ended with 0.20.1 in 2020, when discouragement replaced them, and 28.0 (2024) dropped the score, so one offense means disconnection and discouragement. Under the old system a consensus-invalid transaction cost the full 100 points, and since 30.0 it is not punished at all. Bans are set only by hand, and Bitcoin Core's code says neither bans nor discouragement protect against denial of service.
What was wrong -
By default -whitelist applies only to incoming connections, so it does nothing for peers added with -addnode or -connect unless its out flag is set. Those peers are already never disconnected or discouraged for misbehavior, and current Bitcoin Core has no ban score.
What was wrong -
There is no score or automatic ban: a peer that breaks certain protocol rules is disconnected after one offense and its address discouraged, and bans are set only by hand. Outbound peers are limited to one per address group (/16 for IPv4) and spread across reachable networks. Grouping by network operator needs -asmap, which stays off by default even though 31.0 embeds the map, and nothing selects peers by geography.
What was wrong