How to Run a Bitcoin Node (2026 Guide)
“Don't trust, verify.” Running a Bitcoin node means you enforce the rules yourself. No third party can lie to you about your balance, create fake Bitcoin, or censor your transactions. Here's how to set one up.
What Does a Bitcoin Node Actually Do?
A Bitcoin full node downloads every block in Bitcoin's history and independently verifies that every transaction follows the rules. It checks that nobody created Bitcoin that didn't exist, that every digital signature is valid, and that no coin was spent twice.
When a miner finds a new block and broadcasts it to the network, your node checks it against the rules before accepting it. If the block violates any rule, your node rejects it. You don't ask anyone else's opinion. You verify it yourself with the code on your machine.
This is what makes Bitcoin different from a bank. A bank can tell you your balance is zero when it isn't, freeze your account, or inflate the supply. A Bitcoin node can't be lied to. It checks the math. If the math is wrong, the block is rejected, regardless of who found it.
As of 2026, there are roughly 15,000-20,000 reachable Bitcoin nodes globally. Every one of them enforces the same rules independently. This distributed verification is what makes Bitcoin censorship-resistant. To change the rules, you'd need to convince every node operator to upgrade. Good luck with that.
Why Should You Run Your Own Node?
Privacy
When you broadcast a transaction through someone else's node, they see your IP address and can link it to your wallet addresses. Your own node means your transactions leave your network, not a third party's server.
Sovereignty
You verify your own transactions and balances. No exchange, no wallet provider, and no third-party API can deceive you. If your node says your transaction is confirmed, it is.
Network health
Every node that enforces the rules makes Bitcoin harder to attack. Running a node is a direct contribution to Bitcoin's decentralization. It has no monetary reward, but it matters.
The most practical reason: you can connect your hardware wallet directly to your own node. When you use Sparrow Wallet or Electrum with your hardware wallet, those applications connect to someone's server to check your balances and broadcast transactions. If that server is yours, your financial data stays private. Nobody else knows what addresses you hold or what transactions you make.
What Hardware Do You Need?
You have three main options. All three work. The right choice depends on your budget and how much you want to tinker.
| Option | Cost | Power | IBD speed | Best for |
|---|---|---|---|---|
| Raspberry Pi 5 + 2TB SSD | $220-260 | 5-8W | 2-4 days | Budget, quiet, 24/7 |
| Mini PC (NUC/Beelink) | $150-350 | 10-20W | 12-24h | Fast, more RAM |
| Dedicated plug-and-play (Umbrel Home) | $299 | 15W | 1-2 days | Easiest setup |
Raspberry Pi 5 (recommended for most)
The Pi 5 is a significant upgrade over the Pi 4 for node use. Better I/O throughput means initial block download is 2-4x faster. Pair it with a USB 3.0 SSD enclosure and a 2TB SSD. Don't use a microSD card for the blockchain data. They fail under the constant read/write load. Use a proper SSD.
Estimated cost: $220-260 all-in. Power: ~6W (roughly $3-5/month electricity)
Mini PC (fastest option)
A used Intel NUC, Beelink, or similar mini PC with an NVMe SSD gives you the fastest initial sync. Most can do IBD in under 24 hours. More RAM (16GB+) helps if you plan to add Lightning or other services. These often come with Windows pre-installed; run Ubuntu or Debian on top.
Estimated cost: $200-350 with SSD. Power: ~15W (roughly $8-12/month)
Storage requirements
The full Bitcoin blockchain is ~600GB and grows ~50GB/year. Get a 2TB drive. Use an SSD, not a hard drive. The constant reading and writing will kill an HDD within months. USB 3.0 external SSDs work fine with Raspberry Pi. NVMe internal drives are faster for mini PCs.
Bitcoin Core or a Node Package?
You have two paths: install Bitcoin Core directly, or use a pre-packaged node stack like Umbrel or RaspiBlitz.
Bitcoin Core (direct)
- +Maximum control
- +No extra software
- +Lightest footprint
- +Best for learning
- -Command-line setup required
- -No GUI dashboard
- -Manual configuration
Umbrel / RaspiBlitz
- +Web dashboard
- +Lightning pre-installed
- +App store (Mempool, BTCPay, etc)
- +Beginner-friendly
- -More bloat
- -Less control
- -Extra attack surface
For learning: start with Bitcoin Core directly. Understanding what it does at the command line teaches you how Bitcoin actually works. For a home server where you want Lightning, Mempool, and BTCPay running alongside your node: Umbrel or RaspiBlitz saves you hours of setup time.
Step-by-Step Setup Guide (Bitcoin Core on Linux)
This guide covers Bitcoin Core on Ubuntu/Debian, the most common setup for both Raspberry Pi and mini PCs. Adjust as needed for your hardware.
Install the operating system
For Raspberry Pi: use Raspberry Pi Imager to flash Ubuntu Server 24.04 LTS to your microSD card. For mini PC: download Ubuntu Server 24.04 LTS and boot from a USB drive. Headless server installs (no monitor) work fine once you have SSH access.
Format and mount your SSD
Connect your 2TB SSD. Format it as ext4 and create a mount point at /mnt/bitcoin. Add it to /etc/fstab so it mounts automatically on reboot. This is where the blockchain will live.
Download and verify Bitcoin Core
Go to bitcoincore.org/en/download. Download the latest version and its SHA256 hashes file. Verify the hash before installing. This step is not optional. Never install software from unknown sources without verification.
Configure bitcoin.conf
Create ~/.bitcoin/bitcoin.conf and set your data directory to your SSD mount point, set txindex=1 if you want full transaction indexing, and configure RPC access if you plan to connect wallets. A minimal config works fine to start.
Start initial block download (IBD)
Run bitcoind -daemon to start syncing. Initial sync downloads and verifies all ~600GB of blockchain history. On a Pi 5 with SSD: 2-4 days. On a fast mini PC with NVMe: 12-24 hours. Don't interrupt it. Check progress with bitcoin-cli getblockchaininfo.
Set up as a system service
Create a systemd service file so Bitcoin Core starts automatically on reboot. This turns your device into a proper server that runs 24/7 without manual intervention.
After sync completes
Run bitcoin-cli getblockchaininfo and look for "verificationprogress": 0.9999.... When it hits 1.0, your node is fully synced and enforcing the rules. Welcome to sovereignty.
How Do You Connect Your Hardware Wallet to Your Node?
Sparrow Wallet is the best option for connecting a hardware wallet to your own Bitcoin node. It supports Trezor, Ledger, Coldcard, BitBox02, and most other hardware wallets. Setup takes about five minutes.
Open Sparrow Wallet → Preferences → Server
Select Private Electrum or Bitcoin Core as your server type. Enter your node's IP address and RPC port (default 8332 for Bitcoin Core, or 50001/50002 if using Electrum Server).
Connect and test
Click Test Connection. If it succeeds, Sparrow now routes all wallet queries through your node. No third party sees your addresses.
Import your hardware wallet
Connect your hardware wallet via USB, select New Wallet in Sparrow, and import the xpub. Your wallet now shows balances fetched directly from your node.
For Coldcard users: the air-gap PSBT workflow with Sparrow works perfectly. Create unsigned transactions on Sparrow (connected to your node), sign on the Coldcard via microSD, broadcast via Sparrow. See our Coldcard review for the full workflow.
Should You Add Lightning Network to Your Node?
Once your Bitcoin node is running, adding Lightning Network is a natural next step. A Lightning node routes payments, earns small routing fees, and gives you the ability to send and receive payments without touching the blockchain.
The main Lightning implementations are LND (Go, developed by Lightning Labs) and Core Lightning (C, developed by Blockstream). Both run on top of Bitcoin Core. LND has more tooling and is easier to start with. Core Lightning is more flexible for advanced setups.
Running a routing node is not trivial. It requires managing liquidity (inbound and outbound channel capacity), monitoring uptime, and rebalancing when channels get one-sided. If you just want Lightning payments rather than routing other people's transactions, a custodial or Phoenix wallet is simpler. If you want to run full infrastructure, LND or Core Lightning on top of your node is the way.
Common Problems and Fixes
IBD stalled or very slow
Check if your SSD is running on USB 3.0 (not 2.0). Run "df -h" to confirm the blockchain is on your SSD, not the system microSD. Check "bitcoin-cli getnetworkinfo" to verify peers are connected.
Node uses too much RAM
Add "dbcache=1024" (or lower for Pi) to bitcoin.conf. This controls how much RAM Bitcoin Core uses for the database cache. Default is 300MB; during IBD it helps to increase this, then lower it for steady-state operation.
Can't connect Sparrow to the node
Check your firewall allows port 8332 (Bitcoin Core RPC) or 50001 (Electrum Server). Make sure rpcallowip in bitcoin.conf includes your computer's local IP. The default config only allows localhost connections.
SSD filling up faster than expected
Run "bitcoin-cli getblockchaininfo" and check the chain size. Consider enabling pruning if you don't need historical data. Add "prune=550" to bitcoin.conf to keep only the last 550MB of blocks (you keep the UTXO set and can still fully validate).
Node out of sync after downtime
This is normal. When you restart Bitcoin Core after the device was off, it will catch up with any blocks missed. It usually takes a few minutes to hours depending on how long it was offline. Just wait.
Frequently Asked Questions
What does running a Bitcoin node actually do?
Running a full node means your computer downloads every Bitcoin block since 2009 and independently verifies that each transaction follows the rules. It checks that no Bitcoin is created out of thin air, that every signature is valid, and that no coins are spent twice. You don't trust anyone else's verification. You do it yourself. This is what 'don't trust, verify' means in practice.
Do I need to run a node to use Bitcoin?
No. Most people use Bitcoin through exchanges and wallets without running a node. But running a node improves your privacy (your transactions aren't broadcast through someone else's node), improves your security (you verify transactions yourself), and contributes to the network's decentralization. It's optional but valuable.
How much does it cost to run a Bitcoin node?
A Raspberry Pi 5 costs about $80-100. An 2TB SSD costs $90-130. Add a case, power supply, and microSD card for another $30. Total hardware cost: around $200-260. Electricity costs roughly $3-8 per month at typical US residential rates. A used mini PC (Intel NUC or similar) is another option for $150-300 all-in. The cheapest ongoing cost is electricity.
How much storage does a Bitcoin node need?
The full Bitcoin blockchain is currently around 600GB and grows by about 50-60GB per year. You need at minimum 1TB of storage to run a full archival node. For a pruned node (which verifies everything but deletes old data), you can get by with 10-20GB, but you lose the ability to serve historical data to others. Most people use a 2TB drive to have headroom for several years.
What is a pruned node vs a full archival node?
A full archival node stores the complete blockchain history. It can answer any query about any Bitcoin transaction ever made. A pruned node verifies every block but deletes old block data, keeping only the UTXO set (the current unspent outputs). Pruned nodes still validate the rules as rigorously as archival nodes. They just can't serve historical data. For personal use, a pruned node is fine. For supporting the network fully, run archival.
Can I run a Bitcoin node on my main computer?
Yes, but most people don't recommend it for two reasons. First, Bitcoin Core needs to run 24/7 to stay synced. Shutting down your computer means your node goes offline. Second, initial block download (IBD) takes 1-5 days and uses significant CPU and disk I/O, which slows your computer for other tasks. A dedicated low-power device (Raspberry Pi, mini PC) is the cleaner approach.
What is the difference between Bitcoin Core and node packages like Umbrel?
Bitcoin Core is the reference implementation of Bitcoin, just the node software, no extras. Umbrel, RaspiBlitz, Start9, and MyNode are software stacks that install Bitcoin Core plus Lightning, BTCPay Server, Mempool visualizer, and other tools in a user-friendly package. For learning, start with Bitcoin Core directly. For an all-in-one home server, Umbrel or RaspiBlitz are excellent.
Do I need to open ports to run a node?
No. You can run a fully functional node without opening any ports. Your node will connect out to other nodes and download the blockchain. Opening port 8333 on your router lets your node accept incoming connections, which helps the network by allowing other nodes to connect to you. It's not required, but it's better for Bitcoin's health if you do it.
Can I connect my hardware wallet to my own node?
Yes, and this is one of the main reasons people run nodes. When you use a hardware wallet with third-party software, your transaction data goes through someone else's server. Connecting your Trezor, Ledger, or Coldcard to your own node via Sparrow Wallet or Electrum Server means your address balances and transaction history stay private. Nobody else sees what you own.
How long does initial sync take?
On modern hardware (NVMe SSD, fast internet), initial block download (IBD) takes 12-48 hours. On a Raspberry Pi 4 with an SSD, it takes 2-5 days. On a slow mechanical hard drive, it can take weeks. Use an SSD, not a spinning disk. The Raspberry Pi 5 is much faster than the Pi 4 for IBD due to better I/O throughput.
Ready to Verify for Yourself?
Running a node works best when your Bitcoin is in cold storage. Connect your hardware wallet to your node for full sovereignty.