The Night Wikileaks Got Bitcoin
In December 2010, Visa, Mastercard, PayPal, and Bank of America all froze payments to WikiLeaks within 72 hours of each other. Julian Assange's organization was effectively cut off from the traditional financial system.
Bitcoin was 14 months old. Most people hadn't heard of it. But someone—Satoshi himself, by most accounts—pointed WikiLeaks at a Bitcoin address and said "try this."
It worked. Not because it was magical. Because there was no CEO to call, no compliance department to pressure, no server farm in a single jurisdiction to subpoena. The payment happened across 7,000 miles of infrastructure nobody controlled.
That's the moment you should understand what Bitcoin's decentralization actually is: not a software feature, but a geographic and political reality. The ledger survives because you can't walk into a building and turn it off.
The Three-Layer Problem
Most people who talk about Bitcoin's decentralization are talking past each other. They're conflating different layers of the system that work completely differently.
Layer 1: The node network. Every full node maintains a complete copy of the Bitcoin blockchain and independently verifies every transaction. There are roughly 17,000-18,000 reachable nodes at any given time, spread across an estimated 100+ countries. No single node is essential. If you wiped out every node in the United States tomorrow, Bitcoin would keep processing transactions. That's not theoretical—it's load-tested infrastructure.
Layer 2: The miners. Proof-of-work miners compete to bundle transactions into blocks. They spend real money on electricity to do this, which creates an economic cost to attacking the network. The miners aren't the same as nodes—many miners run full nodes, but many don't. This separation is important. A miner can try to include invalid transactions, but every full node in the world will reject them instantly.
Layer 3: The consensus rules. This is the part that most people miss. Bitcoin's rules aren't determined by developers, CEOs, or miners. They're determined by the collective behavior of nodes deciding which blocks they'll accept. If developers released a client tomorrow that changed the inflation schedule, nodes would simply ignore their blocks. The developers have zero enforcement power. The miners have zero enforcement power. Only nodes matter for rule enforcement, and there are thousands of them.
This is why "Bitcoin can be changed" is technically true but practically irrelevant. Yes, consensus rules can change—but only if nearly every participant agrees simultaneously. That's coordination across hundreds of thousands of independent actors with misaligned incentives, spread across every jurisdiction on earth, who would need to coordinate for the first time in history without a central leader.
Try that. Then tell me Bitcoin isn't decentralized.
Why Geographic Distribution Is the Real Story
Here's a test: ask someone what "decentralized" means for Bitcoin. They'll probably say something about blockchain technology, distributed ledgers, or nodes running worldwide.
Then ask them to name five countries where major Bitcoin node clusters exist.
Most people can't. That's a problem because where the nodes are matters as much as that they exist.
If every Bitcoin node existed in AWS us-east-1, the network would be technically decentralized in a narrow sense and practically centralized in a meaningful one. A well-aimed regulatory action, a natural disaster, a targeted infrastructure attack—any of these could create a temporary consensus failure that the network would survive but users would feel.
The real answer is messier and better. According to node surveillance data, Bitcoin nodes run on residential ISPs, corporate data centers, university networks, and home connections across six continents. Russia has historically had more nodes than many people expect. So has Iran. Countries with adversarial relationships with the West often have surprisingly robust Bitcoin infrastructure, partly because Bitcoin is a way to move value outside the reach of their own governments.
This geographic sprawl isn't accidental. It's the natural result of a system where:
- Running a node costs maybe $100-200/month for a VPS
- The software is open source and can't be copyrighted into compliance
- No license is required
- The economic incentive to run one is primarily self-defense (you can verify your own transactions)
The network gets more resilient as the price goes up because more people have economic reason to run full verification, which means more independent verification of the same history from more physical locations.
The Bear Market Stress Test
Here's where current conditions make this relevant. Bitcoin sitting at $76,000 in a bearish sentiment environment isn't just a price story. It's an infrastructure story.
Every major crypto exchange has been hacked, imploded, or frozen withdrawals at some point in the last decade. Coinbase. FTX. Mt. Gox. Celsius. The list is long and it includes the "too big to fail" institutions that people told me were safe because they had regulatory compliance.
When sentiment turns bearish, the first casualties are always the intermediate custodians. Not because they're more likely to get hacked (though they are), but because their business model depends on people trusting them. When trust breaks, withdrawals stop. When withdrawals stop, you can't access your assets regardless of what Bitcoin's price does.
Self-custody through your own full node isn't paranoia. In a bear market, it's operational necessity. You're not just protecting against theft—you're protecting against the possibility that your exchange becomes insolvent, gets regulatory shutdown, or simply restricts withdrawals "temporarily."
The irony is that people who most need to understand Bitcoin's decentralization—those holding on exchanges during a bear market—are usually the ones who understand it least.
The Counterarguments Nobody Addresses
Let me be direct: Bitcoin's decentralization has real costs and real vulnerabilities. Anyone who tells you otherwise is selling something.
The mining concentration problem. China briefly had 65-75% of Bitcoin's hashrate before the 2021 crackdown. That sounds terrifying. It was less terrifying in practice because: a) the hashrate migrated elsewhere within months, b) miners are location-agnostic given cheap electricity, c) hashrate concentration doesn't give miners control over the rules themselves. But it's a genuine attack surface.
The infrastructure layer. If 80% of Lightning Network liquidity routes through three major nodes, that's a different kind of centralization risk. If major cloud providers start deplatforming node operators at scale, that's a real threat. These aren't theoretical—Amazon AWS has already terminated some crypto infrastructure customers.
The developer concentration problem. While no single dev team controls Bitcoin, the actual code is written by a relatively small group of people who have earned commit access through social reputation. This is a soft form of centralization that nobody has a clean solution for.
These aren't fatal flaws. They're the actual trade-offs of running a system that's more decentralized than anything that came before it, but still built by humans with all the normal human constraints.
What This Means for Your Positions
Here's the actionable part. Understanding Bitcoin's decentralization should change how you hold Bitcoin.
If you're holding on an exchange during a bear market, you're not holding Bitcoin. You're holding an IOU from a company that has your Bitcoin and may or may not be able to give it back to you. The distinction sounds pedantic until your exchange freezes withdrawals.
Running your own node isn't optional if you're serious. A full node lets you verify that the Bitcoin you think you have actually exists in the blockchain, that nobody has double-spent it, that the rules haven't changed without your knowledge. It's not complicated—Bitcoin Core has installer wizards now—and it costs less than $15/month on a VPS.
The geographic argument cuts both ways. If you're running a node on a cloud provider in a single datacenter, you've partially defeated the purpose. Hardware wallets that connect to your own node via Tor offer better geographic resilience. If you care about censorship resistance, your infrastructure should reflect that.
For traders: the settlement finality question matters. Bitcoin's confirmation times are a feature of decentralization—faster settlement requires more trust. If you're making large trades, understanding when your transaction is actually final (and what "final" means in a probabilistic system) is basic operational security.
The Sovereign Individual Angle
Every financial system before Bitcoin required a trusted third party. Your bank. Your government. Your broker. These institutions provided useful services—custody, verification, record-keeping—but they also had the power to exclude you, freeze your funds, devalue your currency, or collapse while holding your assets.
Bitcoin's ledger doesn't care about your citizenship, your credit score, your political opinions, or whether your government is currently allied with the government of whoever runs the servers you're connecting through. This isn't abstract philosophy. It has real implications for anyone operating in jurisdictions with capital controls, unstable currencies, political instability, or simply a desire to hold wealth outside the reach of any single government's decisions.
The trade-off is personal responsibility. With self-custody, there's no 24/7 support line. There's no FDIC insurance. There's no password recovery if you lose your keys. Bitcoin gives you sovereignty and demands you handle the consequences.
That's the actual deal. Take it or leave it.
The Takeaway:
Bitcoin's decentralization isn't a perfect guarantee—it's a probabilistic, economic, and geographic reality that makes the system exceptionally hard to shut down or control. Understanding why requires understanding nodes, miners, consensus rules, and infrastructure distribution—not as abstract concepts, but as physical systems that do (or don't) exist in specific places controlled by specific people.
If you're holding on an exchange during a bearish market, you don't own Bitcoin—you own a promise. Run a node. Hold your keys. Understand what "censorship resistant" actually means when your government or your exchange tries to stop you.