Running a Bitcoin Node: Don't Trust, Verify It Yourself
In May 2017, a group of exchanges and miners representing more than 80 percent of Bitcoin's hashpower signed an agreement in New York to change Bitcoin's rules. Six months later, on November 8, the plan was called off in a short email. No court stopped it. No CEO vetoed it. What killed it was a swarm of ordinary computers — full nodes, run by people whose names nobody knows — that simply refused to follow the new rules. If you want to understand who actually controls Bitcoin, start there.
What a full node actually does
A full node is a computer running Bitcoin software — usually Bitcoin Core — that downloads every block ever produced, from the genesis block on January 3, 2009 to the current tip, more than 900,000 blocks later. It doesn't take anyone's word for any of it. It checks every signature, confirms every coin was created on schedule, and rejects anything that violates the rules: no double spends, no inflated supply, no exceptions.
This is the part most people get backwards: miners don't decide what Bitcoin is. Miners propose blocks. Nodes validate them. A miner who produces an invalid block — say, one that pays them a larger reward than the schedule allows — doesn't get debated or outvoted. Every node on the network silently drops the block as if it never existed, and the miner eats the electricity bill. The 21 million cap isn't enforced by hashpower. It's enforced by tens of thousands of machines that check the math.
Today there are more than 20,000 reachable nodes on the network, with many more running quietly behind home firewalls. Each one holds a complete, independently verified copy of the ledger.
Why "don't trust, verify" is more than a slogan
If you don't run a node, your wallet talks to someone else's. That has two costs.
You're trusting their ledger. When your wallet shows a balance, that number came from a server you don't control. It's almost certainly honest — but "almost certainly honest" is the exact standard Bitcoin was built to replace. With your own node, the balance on your screen is something your own hardware verified against the full history of the chain.
You're leaking your privacy. A wallet that queries a third-party server tells that server which addresses you're interested in, tied to your IP address. That's a map of your holdings handed to a stranger. Your own node queries nobody. It already has the whole chain.
There is no official Bitcoin server, no API in the sky, no company headquarters. The network is nothing more than the sum of the nodes that enforce its rules. Running one isn't a power-user flex; it's participating in the thing itself.
The proof: when nodes beat 80 percent of hashpower
Back to 2017. The New York Agreement proposed doubling the block size via a fork called SegWit2x, backed by the overwhelming majority of miners and the biggest companies in the industry. Users responded with BIP 148 — a user-activated soft fork — and a wave of newly spun-up nodes signaling they would reject non-SegWit blocks. SegWit locked in and activated at block 481,824 in August 2017. The 2x hard fork, facing a network of nodes that would treat its blocks as invalid, was abandoned that November without ever launching.
Hashpower proposes; nodes dispose. We wrote the full story in The Block Size Wars: How Bitcoin Users Beat the Miners. The short version: the people running $200 computers outranked the people running $2 billion mining operations, because validation — not work — is where Bitcoin's rules live.
What it actually costs
Less than you think. You do not need to own a single sat to run a node, and you don't need serious hardware.
- Disk: the full chain is several hundred gigabytes and growing, so budget a 1 TB SSD if you want the whole archive. Short on space? Bitcoin Core's pruned mode validates every block in full but keeps only recent data — it runs in as little as about 10 GB.
- Hardware: an old laptop works. A Raspberry Pi with an SSD works. Packaged node-in-a-box options like Umbrel or Start9 turn a small single-board computer into a plug-and-play node for roughly $150–250 all-in.
- Time: the initial sync — downloading and verifying the entire history — takes anywhere from several hours on a fast desktop to a few days on a Pi. After that, staying in sync is a trickle.
- Bandwidth: modest ongoing usage; you can cap it in settings if your connection is metered.
Run one this weekend
A concrete path for your first node:
- Pick a machine. Spare laptop, desktop, or a Raspberry Pi with a 1 TB SSD.
- Install the software. Download Bitcoin Core from bitcoincore.org and verify the download signature, or flash Umbrel/Start9 onto a Pi for a guided setup. Enable pruning if disk space is tight.
- Let it sync. Start it, leave it plugged in, and let it chew through the chain. This is the machine independently confirming 17 years of monetary history.
- Point your wallet at it. Connect a wallet like Sparrow to your own node so your balance checks and broadcasts never touch a third-party server again.
When the sync finishes, you'll hold a complete, self-verified copy of the most consequential ledger on earth — and the network will be one node harder to capture.
The quiet uniform
Node runners don't announce themselves. There's no leaderboard, no yield, no airdrop — just a machine in the corner enforcing the rules for everyone. That ethic is the culture BitCloset makes clothing for: heavyweight, understated, built for people who verify instead of trust. Browse the current drop at bitcloset.shop.