Raspiblitz Setup Tutorial 2026

Why Build a RaspiBlitz Node?

Running your own Bitcoin and Lightning node gives you financial sovereignty. No third party validates your transactions. No corporate server sits between you and the network. A RaspiBlitz puts you in full control on hardware you own, and this tutorial walks through every step from unboxing to opening your first Lightning channel.

The RaspiBlitz project, started by Christian Rotzoll (rootzoll) and developed in the open by a community of contributors, packages Bitcoin Core, LND, and dozens of additional services into a Raspberry Pi-based node with an LCD display and a clean web interface. Unlike Umbrel or Start9, RaspiBlitz gives you raw access to the command line and configuration files, making it the preferred choice for users who want to understand what their node actually does.

Hardware Bill of Materials

The current RaspiBlitz release is v1.12.1, from March 2026, and it is still the latest in November 2026. It runs on a Raspberry Pi 5 or a Pi 4, and its developers recommend the Pi 5 (RaspiBlitz’s hardware page).

Required Components

• Raspberry Pi 5 with 8 GB of RAM — The board RaspiBlitz recommends. A Pi 4 still runs RaspiBlitz, but its developers no longer recommend one: it is slower, and it can’t take an NVMe drive.
• MicroSD card (64 GB minimum) — Holds the operating system (on a Pi 5 with an NVMe drive, it only installs it), never the blockchain. RaspiBlitz has asked for at least 64 GB since v1.12.0. A Class 10 / A2 rated card from Samsung or SanDisk is sufficient.
• A 2 TB drive — A synced node took about 900 GB in October 2026 and Electrs adds about 80 GB (its index can reach about 155 GB at the end of the first build, just before it compacts), so RaspiBlitz has recommended 2 TB since v1.12.0. On a new setup it also keeps the first 65 GB of the drive for its system, and formatting keeps about 7% of the rest, so a 1 TB drive can no longer hold a synced node. On a Pi 5, use an NVMe drive on an NVMe base board (RaspiBlitz’s hardware page lists tested ones); the Pi 5 can then run everything from it. On a Pi 4, use a 2.5-inch SATA SSD in a USB 3.0 case.
• USB 3.0 to SATA adapter or enclosure (for a SATA SSD) — Connects the SSD to the Pi. RaspiBlitz switches off UASP, a faster USB transfer mode, on adapters it hasn’t tested, because a poorly supported adapter can freeze the system with it; an untested adapter then runs stable but slower. RaspiBlitz’s hardware page links the case it recommends.
• Official Raspberry Pi power supply — 5V / 3A USB-C for Pi 4, 5V / 5A for Pi 5. Underpowered supplies cause random crashes during blockchain sync.
• Ethernet cable — Wi-Fi can be set up, but RaspiBlitz recommends a cable because it removes a possible source of network errors. A wired connection keeps the sync and your Lightning channels steadier.
• LCD display (optional) — The RaspiBlitz 3.5" LCD HAT provides status info directly on the device. The web UI works fine without it.
• Heatsink case or fan — The Pi throttles under sustained load. RaspiBlitz’s hardware page uses a heatsink case on a Pi 4 and the Active Cooler on a Pi 5, which Raspberry Pi says keeps a Pi 5 at a comfortable temperature even under heavy load.

We don’t list prices because they moved a lot in 2026: Raspberry Pi has raised the price of its boards with 2 GB or more of memory several times since December 2025, as memory became more expensive (Raspberry Pi’s announcement). Check current prices before you buy. If you are deciding between node hardware options, the home Bitcoin node guide covers broader considerations.

Step 1: Flash the RaspiBlitz Image

Download the latest image from the RaspiBlitz download page. In November 2026 that is v1.12.1, in two versions: the fatpack image (about 11 GB), with the web interface and faster app installs, which RaspiBlitz suggests for beginners, and a minimal image for experienced users who do everything over SSH. Check the download twice before you flash it: the SHA-256 checksum proves your copy is complete and undamaged, and the signature proves it was built by RaspiBlitz’s lead developer.

# Download the image and its signature
wget https://raspiblitz.fulmo.org/images/raspiblitz-fat-v1.12.1-2026-03-01.img.gz
wget https://raspiblitz.fulmo.org/images/raspiblitz-fat-v1.12.1-2026-03-01.img.gz.sig

# Checksum: compare it with the SHA-256 on the download page
shasum -a 256 raspiblitz-fat-v1.12.1-2026-03-01.img.gz

# Signature: import the lead developer's public key, then verify
curl --tlsv1.2 --proto '=https' https://keys.openpgp.org/vks/v1/by-fingerprint/92A746AE33A3C186D014BF5C1C73060C7C176461 | gpg --import
gpg --verify raspiblitz-fat-v1.12.1-2026-03-01.img.gz.sig raspiblitz-fat-v1.12.1-2026-03-01.img.gz

Look for “Good signature” and a main key fingerprint ending in 1C73 060C 7C17 6461. A warning that the key is not certified with a trusted signature is normal (RaspiBlitz’s FAQ). Our lesson on verifying Bitcoin software explains why the signature matters.

Flash the image to your microSD card using Balena Etcher, Raspberry Pi Imager, or the command line:

# Identify your SD card device (BE CAREFUL - wrong device = data loss)
lsblk

# Flash the image (replace /dev/sdX with your actual device)
gunzip -c raspiblitz-fat-v1.12.1-2026-03-01.img.gz | sudo dd of=/dev/sdX bs=4M status=progress conv=fsync

On macOS, lsblk does not exist: run diskutil list, find the external card by its size, unmount it with diskutil unmountDisk /dev/diskN, then write to /dev/rdiskN (raw disk, much faster) in place of /dev/sdX. On Windows, Balena Etcher handles the compressed image directly.

Step 2: Assemble and Boot

1. Insert the flashed microSD card into the Raspberry Pi.
2. Connect the drive: an NVMe drive on its base board (Pi 5), or the SSD’s USB 3.0 case to one of the blue USB 3.0 ports.
3. Attach the LCD display to the GPIO header if you have one.
4. Plug in the Ethernet cable to your router.
5. Connect the power supply last — the Pi boots immediately when powered.

During the first boot, one reboot is normal. If you have the LCD, it displays the RaspiBlitz logo followed by the device’s IP address. Without the LCD, find the IP from your router’s DHCP client list or use a network scanner:

# Find the RaspiBlitz on your network (Linux/macOS)
sudo nmap -sn 192.168.1.0/24 | grep -B2 "Raspberry"

Step 3: Initial SSH Setup

Connect to your RaspiBlitz via SSH. The default credentials are user admin with password raspiblitz.

ssh admin@192.168.1.XXX

The setup wizard launches automatically on first login. It walks you through:

1. Naming your node — Pick a name for your Lightning node. This is publicly visible on the network.
2. Lightning implementation — The default is LND. CLN (Core Lightning) is available as an alternative. This guide assumes LND.
3. Setting passwords — You set three passwords, called A, B and C: A logs you in over SSH, B protects Bitcoin Core’s RPC interface and is the login for apps such as RTL, and C unlocks the Lightning wallet each time LND starts. You can set new passwords A and B later, but you can change C only if you know it: without it, you restore the Lightning wallet from your 24 words and a channel backup, which closes your channels. Use at least 8 characters, without spaces or special characters, and make each one unique. Write them down and store them with your seed phrase backup.
4. Your 24 seed words — After 10 to 30 minutes of setup, LND shows the 24 words that recover your Lightning wallet, and RaspiBlitz waits until you confirm you wrote them down. Write them on paper or steel.
5. Blockchain sync method — If the drive holds no blockchain yet, choose SYNC to download and check every block yourself, which takes several days (see Step 4), or COPY to copy the blockchain over your home network from a computer or another RaspiBlitz that already has it, which takes hours. Copy only from a node you run: your RaspiBlitz relies on the checks that machine did. If you copy from a computer, quit Bitcoin Core there first, as RaspiBlitz’s instructions say.

Step 4: Wait for Blockchain Sync

The initial block download is the longest part of the setup. With SYNC, Bitcoin Core downloads and validates every block since January 2009. Expect several days: roughly two to four on a Pi 5, and longer on a Pi 4, where RaspiBlitz’s guide says three to six. With COPY, the hours went into the transfer: your RaspiBlitz took over the blocks and the chainstate (the UTXO set) the source had already checked, and now validates only newer blocks.

Monitor progress through the LCD, the web UI, or SSH:

# Check Bitcoin sync status
bitcoin-cli getblockchaininfo | grep -E "blocks|headers|verificationprogress|initialblockdownload"

The verificationprogress field shows an estimate between 0 and 1. Your node is synced when blocks equals headers, verificationprogress is 1 or a hair under it and initialblockdownload shows false. Bitcoin Core 29.2, which RaspiBlitz v1.12.1 runs, usually shows something like 0.99999 even when synced; from Bitcoin Core 30 it shows exactly 1. During sync, keep the Pi powered on. If you must stop it, shut it down cleanly first, with sudo shutdown now over SSH: a clean shutdown is safe and the sync picks up where it stopped, but a sudden power cut can corrupt the card or Bitcoin Core’s data.

For a deeper understanding of what your node does during this process, Bitcoin Core software verification explains the validation mechanics.

Step 5: Access the Web Interface

Once Bitcoin Core syncs (or even during sync), access the RaspiBlitz web UI by navigating to https://192.168.1.XXX in your browser. Your browser warns that the certificate is self-signed. That is expected: the node made it itself. Before you accept it and log in with password A, check that it is your node’s: in your SSH session, print the certificate’s SHA-256 fingerprint and compare it with the one your browser shows for it.

sudo openssl x509 -in /mnt/hdd/app-data/nginx/tls.cert -noout -fingerprint -sha256

The web dashboard shows:

• Bitcoin blockchain sync status and block height
• Lightning node status, channels, and balances
• System resource usage (CPU, RAM, disk, temperature)
• Installed services and their status

The web UI provides most functionality you need for daily operations. For advanced configuration, SSH remains necessary.

Step 6: Fund Your Lightning Wallet

After blockchain sync completes and LND initializes, you need on-chain bitcoin to open Lightning channels.

# Generate a new on-chain receiving address
lncli newaddress p2wkh

# Check your on-chain balance after sending bitcoin
lncli walletbalance

Send a small amount first (50,000–100,000 sats) to verify everything works. Once it confirms, send enough to cover the channels you plan to open in Step 7, plus some extra for on-chain fees. Wait for at least 3 confirmations before opening channels. The Lightning node operation guide covers funding strategies in more detail.

Step 7: Open Lightning Channels

Lightning channels are the payment rails of the network. Opening a channel locks bitcoin in a 2-of-2 multisig with another node. Channel capacity caps how much can move through it. A channel you fund yourself starts with all the funds on your side, so at first you can send over it but not receive. You gain room to receive as you spend, or when another node opens a channel to you.

Finding Good Peers

Connect to well-connected, reliable nodes. Use sites like Amboss, 1ML, or LightningNetwork+ to find peers. Look for nodes with:

• High uptime (99%+)
• Multiple existing channels
• Reasonable fee policies
• Geographic and network diversity

Opening a Channel

# Connect to a peer (get their pubkey@host:port from Amboss or 1ML)
lncli connect 03e7156ae33b0a208d0744199163177e909e80176e55d97a2f221ede0f934dd9ad@1.2.3.4:9735

# Open a channel with 500,000 sats capacity
lncli openchannel --node_key 03e7156ae33b0a208d0744199163177e909e80176e55d97a2f221ede0f934dd9ad --local_amt 500000

# Check pending channels
lncli pendingchannels

# List active channels after confirmation
lncli listchannels

Start with 2–3 channels of 500,000–2,000,000 sats each. Very small channels are poor value because on-chain fees for opening and closing take a disproportionate share. For advanced channel strategies, see the Lightning channel management guide.

Step 8: Install Additional Services

RaspiBlitz supports dozens of optional services. Access them through the SSH menu or the web UI. Common additions include:

• Ride The Lightning (RTL) — A web-based Lightning node manager with a polished interface for channel management, payments, and invoices.
• ThunderHub — An alternative web interface with strong analytics and accounting features.
• BTC-RPC-Explorer — A self-hosted block explorer that queries your own node. No privacy leakage to third-party explorers.
• Electrs or Fulcrum — Electrum server implementations that let you connect hardware wallets like Coldcard or Sparrow Wallet directly to your own node.
• Mempool.space — Self-hosted mempool visualizer and fee estimator.
• LNbits — A Lightning accounts system for creating wallets, payment links, and point-of-sale interfaces.

# Install services via SSH menu
raspiblitz

# Or install directly
config.scripts/bonus.electrs.sh on
config.scripts/bonus.btc-rpc-explorer.sh on

Step 9: Connect Your Wallet to Your Node

The real power of a RaspiBlitz emerges when you connect your daily wallets to it. Instead of trusting Electrum’s public servers or a hardware wallet vendor’s backend, every transaction query goes through your own validated copy of the blockchain.

To connect Sparrow Wallet to your RaspiBlitz Electrs instance:

1. Install Electrs on your RaspiBlitz (see Step 8) and let it build its index, which can take several hours.
2. In Sparrow, open Settings and select the Server tab.
3. Select Private Electrum.
4. Enter your RaspiBlitz IP and port 50002 with SSL enabled.
5. Test the connection and apply.

Away from home, Sparrow can use Electrs’s .onion address over Tor instead, without exposing your home IP address. The Remote Access via Tor section below explains how.

Maintenance and Backups

A running node requires minimal ongoing maintenance, but a few tasks keep things healthy:

• Update RaspiBlitz — Nothing updates by itself, and releases can be months apart (v1.12.0 came out in September 2025, v1.12.1 in March 2026), so check the download page now and then. To update, choose UPDATE → RELEASE in the SSH menu, write the new image to a card (a second 64 GB card is best) and start from it: RaspiBlitz finds your data on the drive and carries on, without closing channels. v1.12.1 runs Bitcoin Core 29.2, a series that reached its end of life on 27 October 2026. Until the next RaspiBlitz release, UPDATE → BITCOIN → TESTED installs 30.0, the version the RaspiBlitz team tested, but neither 29.2 nor 30.0 has the security fixes Bitcoin Core released on 28 October 2026. Choose CUSTOM in the same menu and type 30.4, the patched 30.x release: RaspiBlitz checks its signatures before installing it, though it isn’t the version its team tested.
• Monitor disk space — The blocks grow about 80 GB a year, and Bitcoin Core’s other data and Electrs’s index grow with them: about 100 GB a year together. On RaspiBlitz a 1 TB drive can no longer hold a synced node; a 2 TB drive leaves room for about eight years. Check usage with df -h.
• Back up Lightning channels — LND rewrites its static channel backup, channel.backup, each time a channel opens or closes. RaspiBlitz can copy each new version to Nextcloud or a small USB stick; keep at least one copy off the node. With your 24 words and a recent copy, a new node gets back the settled balance of each channel: each peer, once online, closes its channel, and your balance returns on-chain. If the old node still exists, keep it off for good. Never restore an old copy of the channel database itself, such as an old lnd-rescue file: an out-of-date balance can cost you the whole channel. Our lesson on Lightning backups and watchtowers walks through a restore.
• Monitor temperature — High CPU temperatures (above 80°C) cause thermal throttling. The web UI shows current temps. If consistently high, improve cooling.

# Check system temperature
vcgencmd measure_temp

# Check disk usage (the drive with the blockchain)
df -h /mnt/disk_storage

# Export a fresh static channel backup, then copy it off the node
lncli exportchanbackup --all --output_file /tmp/channel-backup.bak

Security Hardening

Your RaspiBlitz is a financial server. Treat it accordingly with basic security measures:

• Change the default SSH port — RaspiBlitz’s firewall lets SSH in only on port 22, so open the new port first: sudo ufw allow 2222/tcp. Then change Port 22 to Port 2222 in /etc/ssh/sshd_config, check it with sudo sshd -t and run sudo systemctl restart ssh. Keep that session open and test a new login with ssh -p 2222 admin@192.168.1.XXX before you close port 22 with sudo ufw delete allow ssh. This reduces automated SSH brute-force attempts from bots scanning your network.
• Disable password authentication — After setting up SSH key-based authentication, disable password logins entirely. This prevents all password-based attacks.
• Keep the Pi behind your router’s firewall — Do not expose any ports to the public internet unless you specifically need them for Lightning routing. Tor hidden services handle remote access securely without port forwarding.
• Use a dedicated network segment — If your router supports VLANs, isolate the RaspiBlitz from IoT devices and guest networks. This limits lateral movement if another device on your network is compromised.

RaspiBlitz sets up UFW (Uncomplicated Firewall) to deny incoming connections by default and to open only the ports of its own services, such as SSH, Bitcoin, Lightning and the web interface. Verify the firewall status with sudo ufw status and ensure only necessary ports are open.

Troubleshooting Common Issues

Pi won’t boot after flashing

Re-flash the SD card. Verify the SHA-256 hash matches the published checksum. Try a different SD card — cheap cards fail silently.

Bitcoin sync stalls

Check your internet connection and available disk space. Restart Bitcoin Core with sudo systemctl restart bitcoind. If sync consistently stalls at the same block height, your SSD adapter may have compatibility issues — try a different USB-to-SATA enclosure.

LND fails to start

Check logs with sudo journalctl -u lnd -f. Common causes include insufficient disk space, Bitcoin Core not fully synced, or wallet password issues. The RaspiBlitz SSH menu has a repair option under REPAIR that handles most LND issues.

Cannot connect to the web UI

Verify the Pi’s IP address has not changed (set a static IP or DHCP reservation on your router). Try accessing via a different browser. An update does not change the web certificate: RaspiBlitz keeps it on the data drive and makes a new one only if you reset it (CONNECT, then RESET-TLS in the SSH menu) or set up a new drive. If your browser shows a certificate you did not expect, check its fingerprint over SSH, as in Step 5, before you log in.

Remote Access via Tor

RaspiBlitz runs behind Tor from the start. It gives the web interface, your Lightning node and the apps you install, such as Electrs or RTL, a .onion address (an address that only works through Tor), so you can reach your node from anywhere in the world without exposing your home IP address or opening ports on your router. SSH and Bitcoin RPC get an onion address only if you ask: SSH with the command below, Bitcoin RPC from CONNECT in the SSH menu.

To add the SSH address and find your Tor addresses:

# Add an onion address for SSH (once). The last number is the local SSH port:
# if you moved SSH to 2222, run it with ssh 22 2222 (the address stays the same)
bash /home/admin/config.scripts/tor.onion-service.sh ssh 22 22

# Show the onion addresses of the web interface and of SSH
sudo cat /mnt/hdd/tor/web80/hostname
sudo cat /mnt/hdd/tor/ssh/hostname

Use these .onion addresses with a Tor-capable browser or SSH client (e.g., torsocks ssh admin@your-onion-address.onion). Tor access is slower than local network access but provides strong privacy and security for remote management.

Zeus can connect to your LND node over Tor, giving you full Lightning wallet functionality on your phone backed by your own node rather than a third-party server: in the SSH menu, choose CONNECT, then MOBILE, and scan the QR code it shows. Treat that QR code like a key: it gives full control of your Lightning node.

Frequently Asked Questions

How much does it cost to run a RaspiBlitz monthly?

Mostly electricity. A Raspberry Pi with its drive draws roughly 5–10 watts. Running all month, that is about 3.7–7.3 kWh: at $0.20 per kWh, about $0.75–$1.50 a month. Put in your own price; a cheap watt meter at the plug tells you the real draw. Add your internet connection (which you likely already pay), and check its upload allowance: a node commonly uploads 200 GB or more a month unless you limit it.

Can I run RaspiBlitz on a Raspberry Pi 5?

Yes, and it is now the recommended board. RaspiBlitz has supported the Pi 5 since v1.11.0 (April 2024), and since v1.12.0 it can run entirely from a 2 TB NVMe drive on a Pi 5. Use the official 27 W power supply (5 V, 5 A).

Is RaspiBlitz better than Umbrel or Start9?

It depends on your priorities. RaspiBlitz gives you more direct control over the underlying system and is preferred by users who want to learn the command line. Umbrel and Start9 offer smoother graphical interfaces with app-store models. All three achieve the same core goal: running your own full Bitcoin node.

Do I need a static IP address?

Not for basic operation. RaspiBlitz configures Tor hidden services automatically, which work behind NAT without port forwarding or a static IP. If you want to run a public-facing Lightning node for routing, a static IP or dynamic DNS setup helps with uptime and peer connectivity.

What happens if my RaspiBlitz goes offline?

Your Bitcoin node stops and catches up when power returns, but LND stays locked until you enter password C, unless you turned on Auto-Unlock, which stores C on the node. Your Lightning channels stay open but can’t send, receive or route payments while you are offline or locked, and a long absence can lead a peer to close a channel on its own. The real risk is a peer publishing an old channel balance while you are away: on LND’s defaults your node has 144 blocks, about a day, to answer on channels under about 1.2 million sats, and up to two weeks on the largest. If your node might be off longer, add a watchtower that runs on another machine, and switch on your node’s watchtower client when you open your first channel, not just before you go offline: it only guards balances replaced after you switch it on.

Can I migrate from Umbrel to RaspiBlitz?

Not directly. RaspiBlitz v1.12.0 dropped migration from Umbrel, myNode and Citadel because of its new drive layout. Treat the move as a fresh start: on Umbrel, close your Lightning channels and check that you have your 24 words; then set up RaspiBlitz on its drive and let it sync again. Move your bitcoin over, or restore your words on the new node, and open new channels. Our lesson on comparing node platforms covers switching in more detail.