How to Run a Bitcoin Node: Complete 2026 Guide

What does a Bitcoin node actually do?

A Bitcoin node is a computer running software that keeps a full copy of the blockchain and independently checks every single transaction against the consensus rules. It doesn't ask anyone for permission. It doesn't trust anyone's word. It verifies everything from scratch.

When a new block arrives, your node tears it apart. It checks that each transaction's signatures are valid, that no one is double-spending, that the block reward matches the current halving schedule, and that the proof-of-work meets the difficulty target. If anything is off by even one byte, your node rejects the block outright.

Your node also connects to other nodes across the globe. It receives new transactions from the mempool, relays them to peers, and propagates valid blocks. It's a participant in a global, leaderless network. There's no central server. Every node is equal.

Think of it this way: miners write new pages in the ledger. Nodes read every page and make sure nobody cheated. Without nodes, miners could write whatever they wanted.

As of early 2026, the Bitcoin network has roughly 18,000 to 20,000 reachable nodes. Thousands more run behind firewalls or Tor. The more nodes exist, the harder it becomes for any entity to push through rule changes that honest participants reject.

Why should you run your own node?

Let's get specific. There are four real reasons, and each one matters if you care about holding bitcoin properly.

Privacy. When you use someone else's node or a third-party server to check your balance, that server sees your addresses, your transaction history, and your IP. It's like handing a stranger your bank statement. Your own node keeps all of that local. No one else has to know which addresses belong to you.

Verification. "Don't trust, verify" isn't just a slogan. If you don't run a node, you're trusting that whatever server you connect to is telling you the truth. Maybe it is. Maybe it isn't. Maybe it's feeding you a different version of the blockchain. With your own node, you know for certain that a transaction is confirmed because you checked it yourself.

Censorship resistance. Imagine a scenario where a government pressures large node operators to reject certain transactions. If you run your own node, those transactions still get through to you. Your node applies the rules it knows, not the rules someone else dictates.

Sovereignty. This is the big one. Running a node means you don't depend on any company, any API, any hosted service. Your Bitcoin experience is fully under your control. If every public Electrum server went down tomorrow, you'd still have full access to the blockchain.

Honestly, if you're holding more than a few hundred dollars in bitcoin, running a node should be on your to-do list. It's the difference between hoping things are fine and knowing they are.

What hardware do you need?

Good news: you don't need much. An old laptop, a mini PC, or a Raspberry Pi will all work. Here's a breakdown of the components that matter.

The single biggest bottleneck is storage speed. An SSD makes initial sync dramatically faster and keeps your node snappy day to day. If you're buying one component for this project, make it a 1 TB SSD.

As for bandwidth, initial sync will download the full blockchain (600+ GB). After that, daily usage is around 200 MB to 500 MB depending on how many peers you serve. Metered connections can work if you set upload limits in your config file.

How do you set up Bitcoin Core on Linux, Windows, and Mac?

Bitcoin Core is the reference implementation. It's free, open-source, and battle-tested since 2009. Here's how to install it on every major operating system.

Linux (Ubuntu/Debian)

Open your terminal and run these commands. This downloads Bitcoin Core 27.x, verifies it, extracts it, and starts the daemon.

# Download Bitcoin Core
wget https://bitcoincore.org/bin/bitcoin-core-27.0/bitcoin-27.0-x86_64-linux-gnu.tar.gz

# Verify the SHA256 checksum
sha256sum bitcoin-27.0-x86_64-linux-gnu.tar.gz

# Extract
tar -xzf bitcoin-27.0-x86_64-linux-gnu.tar.gz

# Install binaries
sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-27.0/bin/*

# Start the daemon
bitcoind -daemon

# Check sync progress
bitcoin-cli getblockchaininfo

Bitcoin Core will start syncing the blockchain right away. Check progress by looking at the "verificationprogress" field. A value of 0.999999 means you're caught up.

Windows

Download the installer from bitcoincore.org. Run the .exe file, pick your data directory (make sure it's on a drive with at least 700 GB free), and click Start. The GUI will open and begin syncing.

A few tips for Windows users:

• Store the data directory on an SSD if your C: drive is a small HDD.
• Add Bitcoin Core to your Windows Firewall exceptions so peers can connect inbound.
• Set it to launch at login if you want it running 24/7.

macOS

Download the .dmg from the Bitcoin Core website. Drag it into Applications. On first launch, macOS will warn about an unidentified developer. Go to System Settings > Privacy & Security and click "Open Anyway."

Or use Homebrew:

brew install bitcoin

Then run bitcoind -daemon from the terminal, or open the Bitcoin-Qt GUI from Applications.

What are the best plug-and-play node options?

Not everyone wants to mess with terminal commands. Fair enough. Several companies sell pre-built node devices that come ready to go. Flash a microSD card, plug it in, and you're running.

Umbrel is the most popular option right now. Its app store makes adding Lightning, a block explorer, or a mempool visualizer as simple as clicking install. Start9 puts extra emphasis on privacy and data sovereignty. RaspiBlitz is a favorite among people who enjoy building things from parts.

All of these run on a Raspberry Pi 4 or a mini PC. Some, like Umbrel Home and Start9 Server Pure, sell custom hardware that looks nice on a shelf and comes pre-configured. If you'd rather not deal with any setup at all, those are solid picks.

How do you connect your wallet to your own node?

Running a node is only half the story. The real benefit kicks in when your wallet talks directly to your node instead of someone else's server. Here's how to do it with the most popular wallets.

Sparrow Wallet (via Electrum Server)

Sparrow is the gold standard for desktop Bitcoin wallets. To connect it to your node, you'll need an Electrum server running alongside Bitcoin Core. The two most common options are Electrs and Fulcrum.

• Install Electrs or Fulcrum on your node (Umbrel and Start9 have one-click installs).
• In Sparrow, go to Preferences > Server > Private Electrum Server.
• Enter your node's local IP address and port (typically 50001 for TCP or 50002 for SSL).
• Click Test Connection. If it turns green, you're done.

From this point on, every time Sparrow checks your balance or broadcasts a transaction, it goes through your own node. No third party involved.

BlueWallet (via LNDHub)

BlueWallet is a popular mobile wallet that supports both on-chain and Lightning. To connect it to your Lightning node, you'll set up LNDHub.

• Install LNDHub on your node (available as an Umbrel app).
• Open BlueWallet, go to Settings > Lightning Settings.
• Paste your LNDHub URL (something like lndhub://admin:password@yournode.local:3000).
• Save. New Lightning wallets you create will now use your own node.

Trezor Suite

Trezor Suite can connect to your own Electrum server or a full node running Blockbook. The setup is similar to Sparrow: go to Settings > Bitcoin > Custom backend and enter your server's address. This keeps your hardware wallet's address lookups private.

No matter which wallet you use, the pattern is the same. Run an indexing server on your node, point your wallet at it, and you're self-sovereign. Your addresses never touch anyone else's server.

Can you run a Bitcoin node over Tor?

Yes. And you probably should.

When your node connects to peers over the regular internet (clearnet), those peers can see your home IP address. That means anyone monitoring the network can figure out that your IP runs a Bitcoin node. If they also see your wallet connecting to that node, they can start linking your addresses to your physical location.

Running over Tor solves this. Your node gets a .onion address, and all peer connections are routed through the Tor network. Nobody can see your real IP. Your ISP can see you're using Tor, but they can't see what you're doing with it.

Setting this up is simple. Add these lines to your bitcoin.conf:

# Enable Tor proxy
proxy=127.0.0.1:9050

# Only connect through Tor
onlynet=onion

# Listen for Tor connections
bind=127.0.0.1

# Enable your .onion address
listenonion=1

Make sure Tor is installed and running on your system first. On Ubuntu, that's just sudo apt install tor. On plug-and-play nodes like Umbrel or Start9, Tor is enabled by default. You don't need to do anything extra.

One trade-off: Tor connections are slower. Initial sync over Tor can take much longer. A common approach is to sync over clearnet first, then switch to Tor-only mode once you're fully caught up. After that, the slower speeds don't really matter since you're just receiving new blocks every ten minutes.

What about Lightning on your node?

Once you have a Bitcoin full node running, adding the Lightning Network is a natural next step. Lightning lets you send and receive bitcoin instantly with tiny fees. It's a second layer built on top of the base chain, and it needs a full node to work properly.

The two main Lightning implementations are:

• LND (Lightning Network Daemon) - Built by Lightning Labs. It's the most popular implementation and has the best app ecosystem. Umbrel, MyNode, and most plug-and-play nodes ship with LND.
• CLN (Core Lightning) - Built by Blockstream. It's more modular and customizable, favored by developers and advanced users. Start9 supports CLN well.

Setting up Lightning involves opening payment channels with other nodes, which requires locking up some bitcoin on-chain. You then route payments through those channels. If you run a well-connected node with enough liquidity, you can earn small routing fees. But let's be real: most hobby Lightning nodes don't make meaningful money. The real value is being able to pay for things and receive payments without relying on a custodial wallet.

We've written a full guide on this topic. Check out our Bitcoin Lightning Network guide for a deep dive into channel management, liquidity, and connecting your wallet.

If you're running Umbrel or Start9, installing Lightning is literally one click. The software handles the connection between your full node and the Lightning daemon automatically. You can be up and running in under five minutes.

What are the most useful bitcoin.conf settings?

Your bitcoin.conf file controls how your node behaves. Here are the settings worth knowing about.

# Run in the background
daemon=1

# Prune old block data (value in MB, minimum 550)
# prune=550

# Limit upload bandwidth (in KB/s)
maxuploadtarget=5000

# Set max connections (default is 125)
maxconnections=40

# Enable Tor
proxy=127.0.0.1:9050
onlynet=onion
listenonion=1

# Set the data directory (useful on external drives)
# datadir=/mnt/ssd/bitcoin

# Enable the RPC server (needed for wallet connections)
server=1
rpcuser=yourusername
rpcpassword=yourstrongpassword

The config file lives at ~/.bitcoin/bitcoin.conf on Linux, ~/Library/Application Support/Bitcoin/bitcoin.conf on macOS, and %APPDATA%\Bitcoin\bitcoin.conf on Windows. If it doesn't exist yet, create it.

The maxuploadtarget setting is your best friend on metered connections. It limits how much data your node uploads to peers per day without affecting your own usage. Set it to something reasonable and you won't blow through your data cap.

For security, if you're enabling RPC access (needed for wallet connections), use strong credentials and only allow local connections. Don't expose your RPC port to the internet.

What mistakes should you avoid when running a node?

A few things trip up first-time node runners. Here's what to watch out for.

Using an HDD for initial sync. I get it, you have a spare hard drive sitting around. But syncing the full blockchain on a spinning disk can take over a week. Sometimes it never finishes because the disk can't keep up with verification. Spend the $60 on an SSD. You'll thank yourself.

Not backing up your wallet. If you use Bitcoin Core's built-in wallet, back up your wallet.dat file. Losing it means losing access to any bitcoin stored there. Copy it to a USB drive and keep it somewhere safe.

Running on Wi-Fi. It works, technically. But for a device that's supposed to run 24/7 and maintain connections with dozens of peers, a wired Ethernet connection is way more reliable. Plug in the cable.

Ignoring updates. Bitcoin Core releases updates a few times per year. These include bug fixes, performance improvements, and sometimes new features. You don't need to update on day one, but don't fall more than a couple versions behind.

Panicking during initial sync. The first sync takes time. Your computer might get warm. The progress bar might seem stuck at 80% for hours. That's normal. The most recent blocks are the hardest to verify because they contain the most transactions. Just let it run.

Frequently asked questions about running a Bitcoin node

Related guides