Run a Bitcoin Full Node on Umbrel (and Why You Should)

Running your own Bitcoin node is one of the most meaningful things you can do as a bitcoiner. It means you verify every transaction and block yourself — you don’t trust Coinbase, Binance, or any block explorer to tell you the truth. Your node, your rules.

This guide picks up after your Umbrel is up and running (see Setting Up an Umbrel). By the end you’ll have Bitcoin Core synced, Electrs indexed, and Sparrow Wallet talking directly to your own node. No third-party servers. No address leakage. Just you and the chain.

The whole process takes 35 minutes of your time, then your node does the heavy lifting for 1–3 days in the background.

What you’ll need

Umbrel device with umbrelOS 0.5 or later, fully set up
SSD — 1 TB minimum, 2 TB strongly recommended (the chain is ~650 GB and growing ~1.5 GB/day)
Sparrow Wallet installed on your computer
Your computer on the same local network as Umbrel (for LAN setup)
Tor Browser (optional — only needed for remote sovereign access)

Step 1 — Install Bitcoin Node from the Umbrel App Store

Open your Umbrel dashboard (usually http://umbrel.local or the device’s IP address). Go to App Store and search for Bitcoin Node.

You’ll see the official app by Umbrel — currently version 1.2.2, powered by Bitcoin Core under the hood. Tap Install. The app is ~200 MB to install; the blockchain data download happens after.

Tip: Bitcoin Node is a dependency for many other Umbrel apps (Lightning, Electrs, Mempool). Install it first and let it sync before adding anything else.

Step 2 — Understand what you just installed

Bitcoin Node is Bitcoin Core with a clean Umbrel interface on top. Bitcoin Core is the reference implementation — the same software that enforces the consensus rules of the network. When your node says a transaction is valid, that’s the final word. No trust required.

The app gives you:

Real-time peer map and block tracking
Charts for mempool, fees, and network health
Over 20 configurable settings including Tor/I2P, mempool size, and pruning
Direct bitcoin.conf editing for power users

Step 3 — Understand the Initial Block Download (IBD)

After install, Bitcoin Core starts downloading every block from the genesis block (January 2009) to today. This is called the Initial Block Download, or IBD.

Realistic Aussie timings:

Connection	Estimated IBD time
NBN fibre 250+ Mbps	1–2 days
NBN fibre 100 Mbps	2–3 days
NBN HFC / Fixed wireless	3–5 days
ADSL / slow connection	5–7 days

The bottleneck is usually disk write speed, not just bandwidth. A fast NVMe SSD will finish IBD noticeably faster than a slow spinning drive or cheap USB stick. This is why SSD hardware matters.

Warning: Do not unplug or restart Umbrel repeatedly during IBD. It slows things down significantly each time. Let it run.

Your node is fully operational only after IBD is complete and the progress bar hits 100%. Until then, it cannot validate new blocks or serve wallet queries.

Step 4 — Install Electrs (critical for wallet privacy)

The Bitcoin Node app alone does not let your wallet query your node privately. For that you need Electrs — an Electrum-compatible server that indexes every transaction by address.

Without Electrs, Sparrow Wallet has to ask a public Electrum server to look up your addresses. That server sees every address you query and can link them to your IP. Not great.

Go back to App Store, search for Electrs (currently version 0.11.0), and install it. Electrs requires Bitcoin Node to be installed — it indexes the chain you’ve already downloaded.

Tip: Electrs takes an additional 12–24 hours to build its index after Bitcoin Core finishes IBD. Plan for the whole process to take 2–4 days end-to-end before your wallet is fully connected.

Step 5 — Note your connection details

Once Bitcoin Node is synced and Electrs is running, you need two pieces of information to connect Sparrow:

Option A — LAN (faster, home use only):

Open the Electrs app in Umbrel and go to Connect Wallet. You’ll see a local address in the form:

<your-umbrel-ip>:50001

For example:

192.168.1.100:50001

Option B — Tor onion (works from anywhere, private):

In Bitcoin Node settings, enable Tor. After a few minutes, your node gets a .onion address. Electrs also exposes a .onion address shown in its Connect Wallet screen. Use this with Sparrow when you’re away from home.

Step 6 — Connect Sparrow Wallet to your node

Open Sparrow Wallet on your computer.

Go to File → Preferences → Server
Select Private Electrum
Enter your Electrs address:
- For LAN: 192.168.1.100 (your Umbrel IP), port 50001, SSL off
- For Tor: paste the .onion address, port 50001, SSL off (Tor handles encryption)
Click Test Connection

A green tick means Sparrow is now talking to your own node. Every balance check, transaction broadcast, and address lookup goes through your hardware — no third-party server ever sees your addresses.

Tip: If you’re using Tor, you need Tor running on your computer. Either run Tor Browser in the background, or install the Tor daemon. Sparrow has built-in Tor support — check the Use Proxy option and point it to 127.0.0.1:9050.

Step 7 — Verify a received payment yourself

This is the payoff. When someone sends you bitcoin, instead of trusting a block explorer:

Copy the receiving address from Sparrow
In Sparrow, go to Transactions — you’ll see the incoming transaction
Right-click the transaction → Show Transaction to inspect the raw data
Check the block height and confirmations directly — your node confirmed it, nobody else

You are now verifying payments the way Satoshi intended. No trusted third party. No block explorer knowing your address. Just you, the chain, and mathematics.

Step 8 — Review your resource usage

Running a full node has ongoing costs worth knowing:

Resource	Requirement
Disk (initial)	~650 GB (April 2026)
Disk growth	~1.5 GB/day
RAM	2–4 GB (Bitcoin Core + Electrs)
Bandwidth (ongoing)	~20–50 GB/month
Power (Raspberry Pi 5)	~5–8W continuous

On most Australian NBN plans, 20–50 GB/month is negligible. Power cost for a Pi 5 running 24/7 at 8W is roughly $1.50–$2 AUD/month at typical residential rates. It’s cheap infrastructure.

Step 9 — Consider the pruning tradeoff

Pruning lets Bitcoin Core discard old block data, keeping only a small window (e.g. 20 GB) rather than the full 650 GB chain. This is tempting if you’re tight on disk.

The catch: Electrs cannot run on a pruned node. Electrs needs the full chain to build its transaction index. If you prune, you lose the ability to connect Sparrow to your own node for wallet queries.

If disk space is the problem, buy a larger SSD. It’s cheaper than the privacy cost of using someone else’s server.

You can enable pruning in Bitcoin Node → Settings → Pruning if you genuinely just want a validating node with no wallet connectivity.

Step 10 — Enable Tor for full sovereignty

For the strongest privacy posture:

Open Bitcoin Node → Settings
Enable Tor connectivity
Wait 5–10 minutes for your .onion address to be assigned
Your node now connects to peers over Tor and has a .onion address that never reveals your home IP

This means:

Peers you connect to don’t see your IP address
You can share your .onion address with other node operators safely
Remote wallet connections via Tor (Step 6 Option B) work without port-forwarding your router

Tip: Running Tor does add some overhead. Peer connections are slower, and initial block download should be done on clearnet first. Enable Tor after IBD is complete.

Step 11 — Confirm everything is working

Checklist before you’re done:

Bitcoin Node shows Synced and block height matches mempool.space
Electrs shows Indexed with a transaction count (several hundred million)
Sparrow Wallet → Server shows Connected with a green tick
A test receive address shows the correct balance in Sparrow
(Optional) Tor .onion address is visible in Bitcoin Node settings

Troubleshooting

IBD seems stuck or very slow Check your SSD health and available space. Bitcoin Core writes intensively during IBD. If the drive is nearly full, it will stall. Also check that Umbrel isn’t also running a Lightning node during IBD — that adds disk and CPU pressure.

Electrs index never completes Electrs can only index after Bitcoin Core is fully synced. If Bitcoin Node still shows a sync percentage, Electrs will wait. Give it time.

Sparrow shows “Could not connect” Double-check your Umbrel IP hasn’t changed (set a static DHCP lease in your router for the Umbrel MAC address). Also confirm Electrs is running, not just installed. On the Umbrel dashboard, the Electrs app tile should show an active status.

Tor connection is very slow This is normal — Tor adds latency. For everyday wallet use on your home network, use the LAN connection. Reserve Tor for remote access.

“No route to host” when connecting Sparrow over Tor Make sure Tor Browser or the Tor daemon is running on the machine where Sparrow is installed. Sparrow’s proxy setting needs to point to 127.0.0.1:9050.

What’s next

You’ve got the foundation: a sovereign, self-validating Bitcoin node that your wallet trusts instead of a stranger’s server. Here’s where to go from here:

Setting Up an Umbrel — if you skipped the hardware setup, start here
Run Lightning on Umbrel — open Lightning channels and start routing payments through your own node
Bitcoin Node hardware at Shop Bitcoin Australia — pre-configured hardware if you want a plug-and-play setup

Frequently Asked Questions

How long does the initial block download take in Australia?

On a decent NBN fibre connection (100 Mbps+) expect 1–3 days. On slower ADSL or congested fixed wireless it can stretch to a week. The bottleneck is disk write speed as much as bandwidth, so a fast SSD helps significantly.

Do I need Electrs, or is the Bitcoin Node app enough?

The Bitcoin Node app alone does not let your wallet query your node privately. Electrs (v0.11.0) indexes every transaction so Sparrow Wallet can look up your addresses without broadcasting them to a public server. If wallet privacy matters to you — and it should — install Electrs.

What happens to my node when the power goes out?

Bitcoin Core is designed to resume cleanly after an unclean shutdown. It replays any unfinished block validation automatically. A UPS (uninterruptible power supply) is a nice-to-have, not a hard requirement.

Can I prune the blockchain to save disk space?

Yes, but with tradeoffs. Pruning lets you keep only the most recent blocks (e.g. 20 GB instead of 650+ GB), which is enough to validate new transactions. The downside: you can no longer serve historical data to peers or use Electrs — Electrs requires a full, non-pruned chain. If you want to use Sparrow with your own node, don't prune.

Is a 1 TB SSD really enough?

Barely, as of April 2026. The full chain is around 650 GB and growing at roughly 1.5 GB/day. A 1 TB drive gives you roughly 8–12 months of headroom. Buy 2 TB if you can — it's not much more expensive and saves you an upgrade headache.

What is the Tor onion address for and should I use it?

When Tor is enabled in the Bitcoin Node settings, your node gets a .onion address. This lets you connect Sparrow Wallet to your node from anywhere in the world without exposing your home IP. It's slower than a LAN connection but significantly better for privacy if you travel or connect remotely.