node
Bitcoin Knots vs Bitcoin Core: Which Node Should You Run? (2026)Bitcoin Knots vs Bitcoin Core 2026: same consensus rules, different mempool policy. Which node should you run? Full comparison of features, security, and use cases.
Running your own Bitcoin node is the most important thing you can do to participate in the Bitcoin network. A full node validates every transaction and block against Bitcoin's consensus rules — it doesn't trust anyone, including miners. When you use your own node, you're not relying on a third party's version of Bitcoin's history.
This guide walks through the full setup: hardware requirements, Bitcoin Core installation, initial sync, and connecting your wallet to your own node.
Why Run a Node?
Before the how, the why:
Sovereignty: When you broadcast transactions through someone else's node, that node operator knows your IP address, your transaction history, and can technically lie to you about Bitcoin's state. Your own node eliminates this dependency.
Privacy: Querying a third-party node for your wallet balance reveals which addresses you own. Your own node makes those queries locally — no one else learns anything.
Network security: Every node is a vote for the real Bitcoin consensus rules. More nodes = harder for miners or developers to change the rules without community consent. Running a node is how you support Bitcoin's decentralization.
Verification: When you receive Bitcoin, your node independently verifies the transaction is valid — no trust required. This matters most for large amounts.
For a deeper conceptual breakdown, see our why run a Bitcoin node guide.
Hardware Requirements
Minimum to run Bitcoin Core:
| Component | Minimum | Recommended |
|---|---|---|
| Storage | 700 GB SSD | 1 TB+ NVMe SSD |
| RAM | 4 GB | 8 GB |
| CPU | Any modern processor | Quad-core or better |
| Internet | 1 Mbps upload | 10+ Mbps |
| OS | Windows, macOS, Linux | Linux (Ubuntu/Debian) |
Important: The Bitcoin blockchain is approximately 650+ GB as of early 2026, growing by ~60-80 GB per year. A 1 TB SSD gives you 3-4 years of headroom. Avoid spinning HDDs — they're too slow for initial block download.
Best Hardware Options
Option 1: Old PC or laptop you already own The cheapest path. Any computer from the last 5 years with a 1 TB SSD works. Linux is ideal but Windows and macOS work fine.
Option 2: Dedicated Raspberry Pi setup A Raspberry Pi 4 (8 GB RAM) or Pi 5 with an external 1 TB SSD runs Bitcoin Core reliably and uses only 5-10W of electricity. Cost: ~$100-150 for Pi + SSD + case.
Option 3: Plug-and-play node box Products like Umbrel Home, Start9 Server One, or RaspiBlitz come pre-configured with node software and a web dashboard. Easiest setup — costs $200-500. See our Umbrel vs Start9 vs RaspiBlitz comparison.
Option 4: VPS in the cloud A cloud server (Linode, Vultr, Hetzner) with 1 TB storage can run a Bitcoin node for ~$10-20/month. Trade-off: the VPS provider knows your IP and can censor your node. Privacy-conscious users prefer local hardware.
Method 1: Bitcoin Core (Full Control)
Bitcoin Core is the reference implementation — written and maintained by Bitcoin's core developers. It's the most trusted, most complete node software.
Step 1: Download Bitcoin Core
- Go to bitcoincore.org/en/download/
- Download the installer for your OS (Windows:
.exe, macOS:.dmg, Linux:.tar.gz) - Verify the download — this step is critical:
- Download the SHA256SUMS file and SHA256SUMS.asc signature
- Verify the signature against the Bitcoin Core developer signing keys
- On Linux:
sha256sum -c SHA256SUMSandgpg --verify SHA256SUMS.asc - Do not skip verification — you're trusting the code that holds your money
Step 2: Install and Configure
On Linux (Ubuntu/Debian):
# Extract the download
tar -xzf bitcoin-26.x.x-x86_64-linux-gnu.tar.gz
# Move to /usr/local
sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-26.x.x/bin/*
Initial configuration: Create ~/.bitcoin/bitcoin.conf with:
# Data directory (optional, change if you want storage elsewhere)
#datadir=/mnt/external-ssd/bitcoin
# Enable transaction index (needed for some wallet software)
txindex=1
# Limit upload bandwidth (optional, in KB/s)
#maxuploadtarget=5000
# Enable server for wallet connections
server=1
rpcuser=yourusername
rpcpassword=a-long-random-password
# Prune mode (optional — reduces storage to ~10 GB, but limits some features)
#prune=10000
Prune mode vs. full node: A pruned node still validates all blocks during initial sync but discards old block data after processing. This reduces storage to ~10 GB but means you can't serve historical blocks to other nodes. For a fully contributing node, run without pruning.
Step 3: Initial Block Download (IBD)
Start Bitcoin Core: bitcoind -daemon
The Initial Block Download (IBD) synchronizes your node with the full blockchain from genesis. This is the longest part:
- On a fast desktop with NVMe SSD and good internet: 1-3 days
- On a Raspberry Pi 4 with USB SSD: 4-7 days
- On a slow HDD: potentially weeks (avoid this)
Monitor progress: bitcoin-cli getblockchaininfo — look at verificationprogress (0.0 to 1.0)
Do not interrupt the IBD if possible. If you must restart, it resumes from where it left off.
Step 4: Verify Sync
Once synced, bitcoin-cli getblockchaininfo should show:
"chain": "main""verificationprogress": 0.9999..."initialblockdownload": false
Your node is now live and validating Bitcoin's blockchain in real-time.
Method 2: Umbrel (Easiest)
If you want a node with a web dashboard and easy Lightning setup, Umbrel is the most beginner-friendly path.
Setup on Raspberry Pi:
- Download Umbrel OS from umbrel.com
- Flash to microSD card using Balena Etcher
- Insert SD card + connect external SSD + boot the Pi
- Navigate to
umbrel.localin your browser - Follow the setup wizard — Bitcoin node starts syncing automatically
Umbrel also lets you run Lightning, Mempool.space (local mempool visualization), BTCPay Server, and dozens of other Bitcoin apps from a single dashboard.
Umbrel trade-off: Umbrel OS is less configurable than bare Bitcoin Core. For sovereignty purists, running Bitcoin Core directly is preferred. For most users, Umbrel is excellent.
Connecting Your Wallet to Your Node
Running a node is most valuable when your wallet actually uses it. Here's how to connect common wallets:
Sparrow Wallet (Recommended)
Sparrow is the best desktop Bitcoin wallet for connecting to your own node.
- Open Sparrow → Preferences → Server
- Select Bitcoin Core (connects via RPC) or Private Electrum (if you're running Electrum Server)
- For Bitcoin Core: enter
127.0.0.1:8332(local) or your node's LAN IP - Enter your
rpcuserandrpcpasswordfrombitcoin.conf - Click "Test Connection" — green means connected
Electrum Wallet
- Start Electrum with your own server:
electrum --oneserver --server=your-node-ip:50001:t - Or in Electrum: Tools → Network → Server → uncheck "Select server automatically" → enter your Electrum Server address
Note: Electrum requires running Electrum Server (Fulcrum or Electrs) on your node, not just Bitcoin Core. Umbrel includes Electrum Server as an installable app.
Blue Wallet (Mobile)
- Blue Wallet → Settings → Network → Bitcoin Node
- Enter your node's address (use Tor or local network)
- For remote access: set up Tor Hidden Service on your node (Umbrel does this automatically)
Coldcard (Hardware Wallet)
Coldcard uses Electrum or Sparrow as a companion — connect those apps to your node as described above, then pair your Coldcard with the app.
Running a Node Over Tor
For maximum privacy, run your Bitcoin node behind Tor. This hides your IP address from peers and makes it harder to correlate your transactions with your location.
On Ubuntu:
sudo apt install tor
Add to bitcoin.conf:
proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
onlynet=onion
Restart Bitcoin Core. Your node will now exclusively connect to peers via Tor.
Umbrel: Tor is built-in. Enable it from the Umbrel dashboard — your node gets a .onion address you can use to connect mobile wallets from anywhere.
Maintenance and Monitoring
Regular checks:
bitcoin-cli getblockcount— should match current block height at mempool.spacebitcoin-cli getpeerinfo— should show 8+ active connectionsbitcoin-cli getnetworkinfo— check node version, connectivity
Updates: Check bitcoincore.org for new releases. Update promptly when security releases are announced.
Storage: Monitor disk usage — at ~60-80 GB/year growth, plan for storage expansion or add pruning.
Bandwidth: A full node with default settings uploads ~200-400 GB/month serving the network. If bandwidth is limited, set maxuploadtarget=5000 (5 GB/day) in bitcoin.conf.
Node Hardware Comparison
| Option | Cost | Difficulty | Privacy | Best For | |---|---|---|---| | Old PC / laptop | Free | Medium | High (local) | Most users with spare hardware | | Raspberry Pi DIY | ~$150 | Medium | High (local) | Tinkerers, low power usage | | Umbrel / Start9 box | $200-500 | Easy | High (local) | Non-technical users | | Cloud VPS | ~$15/mo | Medium | Lower (VPS knows you) | Users without spare hardware |
Frequently Asked Questions
How long does initial sync take?
Typically 1-7 days depending on hardware. A fast NVMe SSD and good internet connection syncs in 1-2 days. A Raspberry Pi with USB SSD takes 4-7 days. Progress can be monitored with bitcoin-cli getblockchaininfo.
Do I need to run a node 24/7? For full participation (serving peers), yes. For personal use only, you can run it when needed — it will sync missed blocks on restart. Full nodes that stay online help the network more.
How much bandwidth does a Bitcoin node use?
With default settings: ~200-400 GB/month upload. You can limit this with maxuploadtarget in bitcoin.conf without affecting your node's validation capability.
Can I run a Lightning node on the same machine? Yes. LND, Core Lightning, or Eclair can run alongside Bitcoin Core on the same machine. Umbrel makes this easy with a one-click Lightning node install that automatically connects to your Bitcoin Core backend.
Is running a node risky? Running a node carries minimal risk. You're not holding any Bitcoin in the node itself (unless you also run a Lightning channel or node wallet). The main risk is opening RPC ports to the internet — use strong passwords and don't expose port 8332 publicly.