Running your own node — verify, don't trust

First, some plain definitions. The blockchain is Bitcoin's shared record book — every transaction since 2009, in order. A full node is a program that keeps its own copy of that record book and independently checks every transaction and block against Bitcoin's rules. Nothing gets accepted just because someone says so; your node verifies it.

Here's why that matters. When your wallet shows your balance, it has to get that number from somewhere. Most wallets quietly ask a company's server — often a website called a block explorer (a search engine for the blockchain, like mempool.space). You're trusting that server to tell you the truth about your own money. Run your own node and your wallet asks your computer instead. You stop trusting and start verifying.

There's a privacy win too. Every time your wallet asks someone else's server about your addresses, that server learns which addresses are yours and can build a picture of your holdings over time. Your own node keeps that between you and your own machine. The saying is "don't trust, verify" — a node is how you actually do it.

Let's be clear, because this trips people up: you do not need a node to have good self-custody. Controlling your own keys with a hardware wallet and a written-down backup is the heart of self-custody, and you already have that without a node.

A node adds two things on top: stronger independent verification, and better privacy. Those are real benefits, but they're a refinement, not a requirement, and plenty of careful, long-term Bitcoin holders take years to get here. What this course does ask you to keep is the habit the node automates: verify things yourself. The address on the device screen. The backup you actually restored. The balance you can confirm without asking a stranger. The machine can wait until you're curious — the habit starts now.

If you do decide to try it, you don't have to be a computer expert. There are two paths.

Plug-and-play kits do the hard parts for you. The main ones are Umbrel, Start9, and RaspiBlitz. You get a small dedicated device (or install their software on one), and a friendly screen walks you through setup and installs everything a wallet needs. Umbrel is generally the most beginner-friendly; Start9 leans hardest into privacy; RaspiBlitz is the community, do-it-yourself favorite. These are the right starting point for almost everyone.

The do-it-yourself path means running the core software (Bitcoin Core) directly on a small computer like a Raspberry Pi (an inexpensive hobbyist computer) or an old laptop you have lying around. It gives you the most control and costs the least if you already own the hardware, but there's no friendly setup wizard — you follow written instructions. It's a fine project if you enjoy tinkering; otherwise, start with a plug-and-play kit.

One tip either way: a node is happiest as its own little always-on device, separate from the laptop you use every day.

Before your node can help you, it has to catch up on all of Bitcoin's history. This one-time process is called the initial block download, or IBD — it's your node downloading the entire blockchain and checking every block from the very beginning.

Set your expectations: this is big and slow. As of 2026 the records are around 700 gigabytes, and the download usually takes somewhere between one and three days depending on your internet and hardware. The good news is you don't have to babysit it — most people start it on a weekend, leave it plugged in, and let it grind away in the background. After that first catch-up, it just keeps pace quietly with a few new blocks an hour, and you rarely think about it again.

Here's the part people forget: a node sitting in the corner does nothing for you until your wallet actually asks it questions. If you run a node but your wallet keeps quietly using a company's server, you got none of the benefit. So this step is what makes it real.

The good news is it's usually a one-time setting. In a wallet like Sparrow (a well-regarded desktop wallet with excellent support for this), you go into the server settings and point it at your own node instead of a public server. Your plug-and-play kit gives you the address to paste in. From then on, every balance check and every send goes through your machine.

The cleanest way to do this keeps your keys safe. You give your wallet only your xpub — your "extended public key." An xpub lets a wallet see all your addresses and add up your balance, but it cannot spend anything. A wallet set up this way is called watch-only: it can watch your funds through your own node all day long, while the actual keys that move money stay offline on your hardware wallet. Watching happens on the node; signing stays on the signing device.

After you connect, do one quick sanity check: compare the latest block number your wallet shows against the block number on your node's dashboard. If they match, your wallet is truly talking to your node. Loop closed.

A node lets you verify the rules yourself. There is a matching move on the signing side: you can approve a payment without your keys ever touching an internet-connected device at all. This is called air-gapping — keeping a literal gap of air between your keys and the network, so nothing online can reach them even in principle.

Here is the flow in plain terms. Your everyday app builds the unsigned transaction: it knows the amount and the destination, but it cannot approve anything on its own. It hands that unsigned transaction to your offline hardware wallet by QR code (you scan a black-and-white square off the screen) or by memory card (you physically carry the file across). The hardware wallet shows you the details, you verify the address on its own screen, and it signs. The signed transaction travels back the same way — another QR scan, or the card — and your app broadcasts it. Your keys never left the offline device, and no cable ever joined the two.

You may hear the term PSBT, short for Partially Signed Bitcoin Transaction. Don’t let it intimidate you: it is simply the file format that not-yet-signed transaction travels in as it passes back and forth. It pairs naturally with the watch-only setup from the section above — the online side holds only your xpub, so it can watch, build and broadcast but never spend, while every signature happens on a device that has never been online.

Like the node itself, it is optional. For most people a good hardware wallet used carefully is plenty. Air-gapping is the extra layer for larger holdings, or for anyone who would simply rather not take the USB cable on trust.