Running your own bitcoin node.

A bitcoin node runs the network's full rule set. It downloads every block, checks every signature and consensus rule, and rejects anything invalid regardless of who sent it. A block from a miner with enormous hash power is refused just as firmly as one from a hobbyist if it breaks the rules.

It also keeps a mempool: the queue of transactions not yet in a block. From there it relays transactions to other nodes, which is how the network propagates without a central server.

What a node does not do is earn bitcoin. Nodes receive no reward. They produce autonomy, not income — and together they are the reason nobody can unilaterally change bitcoin's rules.

A full node stores and validates the entire chain. A pruned node validates everything but discards old block data afterwards, saving hundreds of gigabytes without weakening validation. An archival node keeps everything and is needed to query historical data.

A mining node is a full node plus hardware searching for blocks. Mining via a pool without your own node means trusting the pool about which transactions you help validate.

Most phone wallets are light clients that ask the provider's server for your balance. That works, but the server can lie to you and can see which addresses belong together. Point the wallet at your own node and both problems disappear.

First, verification. Without your own node you believe someone else about how much bitcoin exists, whether your transaction confirmed and whether the rules changed. With one, you check that yourself.

Second, privacy. Querying an external server tells that party which addresses are yours and which IP you use. Your own node breaks that link, especially over Tor.

Third, sovereignty during conflict. When a rule change or fork is disputed, your node decides which chain you follow — exactly the mechanism users relied on in 2017.

Hardware requirements are modest: a Raspberry Pi 5 with 8 GB of RAM, an old laptop or a small mini PC all work. Storage matters more than the CPU — use an SSD, never a spinning disk or USB stick.

Budget at least 1 TB for a full archive or 256 GB when pruning. A node uses roughly 10 to 30 GB of upload traffic per month.

Power draw is negligible: a Pi with SSD uses 5 to 10 watts, about €15 a year. Leave it running so it never has to catch up far.

Bitcoin Core is the reference implementation. Download it from bitcoincore.org and verify the release signatures — the one step you must not skip.

Point the data directory at your SSD and set your options in bitcoin.conf: prune=10000 for a pruned node, txindex=1 if you want full lookup, server=1 if a wallet will connect.

Then the Initial Block Download starts: your node fetches and validates the chain from block zero, typically one to three days. Interrupting is fine; it resumes.

Umbrel is a home-server OS that wraps Bitcoin Core, an explorer, an Electrum server and optional Lightning in a graphical dashboard. Flash the image, connect the Pi by cable, open umbrel.local, create an account and store the seed, then install Bitcoin Node from the app store.

Add Mempool for your own explorer and Electrs so wallets like Sparrow or BlueWallet can talk to your node.

Comparable alternatives are Start9 (StartOS), RaspiBlitz and myNode. Umbrel is the simplest; Start9 leans hardest into privacy.

Run Electrs or Fulcrum on top of your node so your wallet queries your own machine. Sparrow and Electrum let you enter the server manually; on mobile you typically use the Tor address your node OS generates.

Keep Bitcoin Core and the node OS updated, back up wallet files and Lightning channel state, and never expose the RPC port to the open internet. Port 8333 is the public peer port and is safe to open.

The three most common mistakes: a slow disk that makes syncing endless, unstable power during the initial download, and a wallet that quietly keeps using the vendor's default server.