Lightning Network & Layer 2

How to Run a Lightning Node at Home

A small home computer connected to an external drive on a walnut shelf, the size of node you can run at home.

Security advisory (5 November 2026): a flaw in the Linux kernel, CVE-2026-98432, affects home Lightning nodes running on Linux. The demonstrated attack needs a Multipath TCP listener, which LND 0.20.x and 0.21.x, Lightning Terminal, Loop and Alby Hub opened by default. Update LND to 0.21.6 or 0.20.7, and Lightning Terminal, Loop or Alby Hub if you run them; on Umbrel, update umbrelOS to 2.0.1 and then the Lightning Node app. Install your system’s kernel update now if it is out (Debian and Raspberry Pi OS have it); until then, turn Multipath TCP off. LND says the kernel patch is the only fix. The fixed versions and the exact commands are in the steps of our Lightning node advisory.

Affiliate disclosure: the Umbrel Home link below is an affiliate link (we may earn a commission). The Start9 Server One link is not. Building your own node, as this guide describes, is what we recommend for most readers.

What You Need to Run a Lightning Node

Running a Lightning node at home puts you in control of your own payment infrastructure. You verify your own transactions, route payments for others, and interact with the Bitcoin network without relying on any third party. This is the practical meaning of financial sovereignty.

This guide walks you through every step — from choosing hardware to opening your first channels. No prior server administration experience required, though basic comfort with a command line helps for troubleshooting.

Hardware Requirements

Your Lightning node runs 24/7, so hardware selection matters for reliability and cost. Here are the three main tiers:

Budget Option: Raspberry Pi 4/5

ComponentMinimumRecommendedEstimated Cost
BoardRaspberry Pi 4 (4GB)Raspberry Pi 5 (8GB)$55 - $80
Storage2TB SSD (USB 3.0); 1TB is nearly full already2TB NVMe via HAT$60 - $120
PowerOfficial USB-C PSUUPS-backed PSU$10 - $50
CoolingPassive heatsink caseActive cooling case$10 - $25
MicroSD32GB (umbrelOS runs from it)32GB+ Class A2, known brand$8 - $12

Total: $143 - $287

The Raspberry Pi remains the most popular choice for home nodes due to its low power consumption (5-15W) and extensive community support. The Pi 5 with its PCIe interface offers significantly better storage performance than the Pi 4’s USB 3.0, making initial blockchain sync faster.

On storage: Bitcoin’s blocks took about 780 GB on 28 October 2026 and grow about 80 GB a year; with its undo data and chainstate, Bitcoin Core 32.1 asks for about 900 GB, so a 1 TB drive is nearly full today. Buy 2 TB. The cost ranges in these tables date from when we first wrote this guide, so check current prices.

Three storage devices drawn to the same scale. The 32 GB microSD card, from which umbrelOS and its apps run, is a thin sliver: it could never hold the chain. Bitcoin Node needs about 900 GB: the blocks alone were about 780 GB in October 2026, and the rest is the undo data and chainstate Bitcoin Core keeps beside them, plus a small margin. On a 1 TB SSD that leaves room for one more year of blocks, about 80 GB, and then it is full. On a 2 TB SSD there is room for years of growth. Move Bitcoin Node to the SSD as soon as you install it.
Buy 2 TB: Bitcoin Node already needs about 900 GB. The blocks grow about 80 GB a year, so a 1 TB drive is nearly full on day one. On a Raspberry Pi, umbrelOS runs from the 32 GB card and Bitcoin Node moves to the SSD.

Mid-Range Option: Mini PC

ComponentRecommended SpecsEstimated Cost
Mini PCIntel N100/N95, 16GB RAM, NVMe slot$150 - $250
Storage2TB NVMe SSD$80 - $120

Total: $230 - $370

Mini PCs like the Beelink S12 Pro or MeLE Quieter series offer more processing power than a Raspberry Pi at a modest cost increase. They include built-in NVMe slots, more RAM, and draw 10-25W under load. If you plan to run additional services alongside your node (Electrum server, BTCPay Server, Nostr relay), a mini PC provides headroom a Pi cannot match.

Umbrel and Start9 also sell pre-assembled boxes with their node OS installed: the Umbrel Home[#aff], from $499, and the Server One, from $899 to $1,399 (all four versions for sale on 8 November 2026). Both cost more than the mini-PC build above ($230–$370 in our table). If you buy one, the 2 TB advice still applies. The “from” prices are for each box’s cheapest configuration.

Repurposed Hardware

An old laptop or desktop with at least 4GB RAM and a USB 3.0 port for an external SSD works perfectly. The main concern is power consumption — a full desktop might draw 60-100W, costing $50-100/year in electricity. An old ThinkPad running Ubuntu is an excellent and cost-effective option.

Choosing Your Node Software

Two main approaches exist for running a node at home: packaged node platforms and manual installation. For most home users, packaged platforms provide the best balance of functionality and simplicity.

Packaged Node Platforms

PlatformLightning ImplementationInterfaceBest For
UmbrelLND (default) or CLNWeb dashboardBeginners, app ecosystem
Start9 (StartOS)LND or CLNWeb dashboardPrivacy-focused users
RaspiBlitzLND or CLNTerminal + webHands-on learners
myNodeLNDWeb dashboardSimplicity

Citadel, which this table used to list, has been archived on GitHub since 2023, so we have taken it out. StartOS installs on your own x86-64, ARM64 or RISC-V machine, or on a Raspberry Pi 4. Its docs say other Pi models, the Pi 5 included, are not supported.

For a side-by-side comparison of the two, see Umbrel vs Start9: Which Node Software?

Step-by-Step Setup with Umbrel

This walkthrough uses Umbrel as the reference platform due to its widespread adoption and accessible interface. The principles apply to any platform.

The six steps of setting up a Lightning node on Umbrel. 1 Flash umbrelOS onto a microSD card or a USB drive. 2 Boot: 2 to 5 minutes. 3 Sync: Bitcoin Core downloads the whole chain and checks every block itself, which takes 1 to 7 days. 4 Lightning: install the Lightning Node app in 1 to 2 minutes and back up its seed. 5 Fund: send bitcoin to the node and wait about 30 minutes for confirmations. 6 Open channels and wait a few confirmations. The sync takes 3 to 7 days on a Raspberry Pi 4, 2 to 4 days on a Raspberry Pi 5 and 1 to 3 days on a mini PC with an Intel N100. Every other step takes minutes.
Six steps, and only one of them takes days. Bitcoin Core has to download and check the whole chain before Lightning can start. Every other step takes minutes.

Step 1: Flash the Operating System

  1. Download umbrelOS from umbrel.com/downloads. It is a standalone operating system, and since umbrelOS 1.0 it cannot be installed on top of an existing Ubuntu or Debian system.
  2. For Raspberry Pi (Umbrel recommends the Pi 5; a Pi 4 works too): flash umbrelos-pi.img.zip to a microSD card of 32 GB or more with Raspberry Pi Imager or balenaEtcher. On a Pi 4, update the bootloader first, as Umbrel’s Raspberry Pi guide explains.
  3. For Intel or AMD machines: Umbrel’s default is to flash umbrelos-amd64.img.xz to a USB drive of 32 GB or more and leave it plugged in, so every internal drive stays free for apps and data. If you would rather not keep a USB drive plugged in, its USB installer puts umbrelOS on an internal drive instead (Umbrel’s amd64 guide).
  4. On a Pi, leave USB drives unplugged for the first boot and add your SSD once setup is done. On a mini PC, put the SSD inside the machine, because umbrelOS only uses internal SATA and NVMe drives as main storage. Drives plugged in over USB show up as external storage.

Step 2: Initial Boot and Configuration

  1. Connect your device to your router via Ethernet (Wi-Fi is not recommended for a node).
  2. Power on the device and wait 2-5 minutes for initial setup.
  3. Navigate to umbrel.local in your browser (or find the IP address via your router’s admin panel).
  4. Create your account with a name and a strong password. Umbrel keeps the account only on the device and cannot recover a lost password, so save it in a password manager. Your Lightning wallet’s seed comes later, in Step 4.

Step 3: Bitcoin Core Sync

Before Lightning can operate, Bitcoin Core must sync the entire blockchain, which came to about 780 GB of blocks on 28 October 2026. Install Bitcoin Node from the Umbrel App Store to start it. On a Raspberry Pi, plug in your SSD first and move Bitcoin Node onto it as soon as it is installed: in the app’s settings, choose Storage, then App storage, then Move. The drive must be formatted as ext4 (Umbrel’s external storage guide), and a 32 GB card cannot hold the chain.

  • Raspberry Pi 4: 3-7 days for initial sync
  • Raspberry Pi 5: 2-4 days
  • Mini PC (Intel N100): 1-3 days

During sync, your device is CPU and I/O intensive. Avoid interrupting the process. Monitor progress through the Umbrel dashboard. For a deeper understanding of what your node does during sync, read our guide on Bitcoin Core verification.

Step 4: Install the Lightning App

  1. Once Bitcoin Core is synced, navigate to the Umbrel App Store.
  2. Install “Lightning Node” (LND). Installation takes 1-2 minutes.
  3. Open the Lightning Node app. Your LND instance will initialize and create a Lightning wallet.
  4. Back up your Lightning wallet seed. It recovers your on-chain funds but not your channels, which also need Static Channel Backups (see Backup Strategy below).

Step 5: Fund Your Node

  1. In the Lightning dashboard, click “Deposit” to generate an on-chain Bitcoin address.
  2. Send bitcoin from your exchange or existing wallet to this address. Start with a moderate amount — 500,000 to 2,000,000 sats is reasonable for getting started.
  3. Wait for 3 confirmations (approximately 30 minutes). Your on-chain balance will appear in the Lightning wallet.

Step 6: Open Your First Channels

This is the most important step. Your channel choices determine your routing capabilities and fee costs.

  1. Research well-connected nodes on sites like 1ML, Amboss, or LightningNetwork+ (for balanced channel swaps).
  2. In the Lightning dashboard, click “Open Channel.”
  3. Enter the node’s public key or use the node URI (pubkey@host:port).
  4. Set the channel capacity. Minimum viable channel size is 100,000 sats, but 1,000,000+ sats provides better routing utility.
  5. Set the on-chain fee rate for the funding transaction. Check mempool.space for current rates — no need to overpay during low-congestion periods.
  6. Confirm and wait for the funding transaction to confirm. Your peer decides how many confirmations it needs: LND’s default is 3 on channels under about 8.4 million sats, rising to 6 on the largest.

Recommended First Channels

NodeWhy ConnectCapacity Suggestion
ACINQMore channels than any other public node, and among the largest by capacity (mempool.space, November 2026)1,000,000+ sats
A merchant or service you pay often (Bitrefill, for example)Your payments to it need no route500,000+ sats
LightningNetwork+ peersBalanced channels (inbound liquidity)500,000+ sats

Open 3-5 channels initially. Each channel opening costs an on-chain transaction fee, so batch your opens during low-fee periods when possible.

Network Configuration

Port Forwarding

For other nodes to reach your node at your IP address, rather than only through Tor, forward port 9735 (Lightning’s default port) on your router to your node’s local IP address.

  1. Access your router’s admin panel (typically 192.168.1.1 or 192.168.0.1).
  2. Find the port forwarding or NAT settings.
  3. Create a rule: External port 9735 → Internal IP of your node, port 9735, TCP.
  4. Save and verify using a port checker tool.

Tor Configuration

Alternatively, you can run your node exclusively over Tor. Umbrel’s Lightning Node app turns Tor on by default; on StartOS 0.4, Tor is an optional service you install from its marketplace. Tor nodes are reachable without port forwarding, though with higher latency. Running over Tor provides significant privacy advantages — your home IP address is never exposed to the Lightning Network.

For best results, consider a hybrid approach, which Umbrel’s Lightning Node app calls Hybrid Mode and turns on for new installs: your node keeps its Tor onion address and also connects directly to clearnet peers. Direct connections are faster and more stable, but the peers at the other end see your IP address. To be reachable at your IP address too, forward port 9735 as above and announce that address (LND’s externalip setting).

Three ways other Lightning nodes can reach the node in your home. Tor only: your node connects out to the Tor network, and other nodes reach it there at its onion address; no port is opened on your router and no peer sees your IP address, but connections are slower. Hybrid Mode, Umbrel's default: other nodes still reach you through Tor, and your node also dials clearnet peers directly, which then see your IP. Direct: other nodes dial your IP address on port 9735, which you must forward on your router to your node and announce, so anyone can see your IP.
Through Tor, your node reaches out, so nothing has to be opened at home. Umbrel’s Hybrid Mode also dials clearnet peers directly, and they see your IP. Forward port 9735 only if you want peers to dial your IP.

Essential Node Management

Monitoring Tools

Install these Umbrel apps for better node visibility:

  • ThunderHub — Advanced channel management, fee policy controls, automated rebalancing.
  • Ride The Lightning (RTL) — Channel monitoring, payment history, invoice management.
  • LNbits — Create Lightning wallets and apps on top of your node. Useful for sharing your node’s liquidity with family or running a point-of-sale.

Backup Strategy

Two backups protect the money on a Lightning node: your seed for the on-chain funds, and a fresh channel.backup for the money in channels. A third file, channel.db, is never a backup.

  1. Seed phrase: LND gives you 24 words. Store them on paper or metal, away from the node. They restore your on-chain funds and unlock channel.backup, but on their own they do not bring back the money in your channels. They use LND’s own format (aezeed), so they restore into LND, not into an ordinary wallet: label them as an LND seed.
  2. Static Channel Backup (channel.backup): LND rewrites this file each time a channel opens or closes, so a copy made after your last open or close is complete. It is encrypted with a key from your 24 words. Umbrel’s Lightning Node app also uploads an encrypted copy to Umbrel’s backup server (on by default). Download your own copy to external storage after every channel you open or close.
  3. Never restore an old channel.db: this is LND’s live record of every channel’s latest balance. A copy from last night holds last night’s balances, and putting it back on a node would publish an out-of-date state, which lets your peer take everything in the channel. Restoring a snapshot of the whole machine counts too, if it includes the Lightning data. A copy kept aside is not a backup, though chantools can extract a fresh channel.backup from it.

Our lesson on Lightning backups and watchtowers explains what each file does and what a restore brings back.

If your node dies, three things matter. Your 24-word seed brings back your on-chain bitcoin, but not, on its own, the money in your channels. The channel.backup file, the Static Channel Backup that LND rewrites each time a channel opens or closes and that your seed decrypts, lets a new node ask each peer to close its channel, so the money in your channels comes back on-chain; each peer has to be online to close. An old copy of channel.db holds an out-of-date channel state and must never be restored: your peer could take everything in the channel. Umbrel uploads an encrypted channel.backup for you, on by default; keep your own copy too, downloaded after every channel you open or close.
The seed brings back your on-chain bitcoin; channel.backup brings back the money in your channels. With it, a new node asks each peer to close; as each one comes online and closes, that balance returns on-chain. Never restore an old channel.db.

Keeping Your Node Online

Lightning nodes should run 24/7. Extended downtime risks:

  • Peers may force-close channels after prolonged unresponsiveness.
  • You cannot detect and respond to potential cheating attempts while offline.
  • Routing revenue stops during downtime.

Mitigate these risks with a UPS (Uninterruptible Power Supply) for short outages and a watchtower that monitors your channels when you are offline. Switch the watchtower client on when you open your first channel: a tower only guards the balances revoked while the client runs. Our Lightning watchtower setup guide shows how. On Umbrel, the Lightning Node app’s watchtower client starts switched off: in its advanced settings, turn on Watchtower Client and add a tower. To keep the Bitcoin node underneath healthy, see our full node setup guide.

If a peer publishes an old channel balance, your node must answer before a deadline. With LND's defaults the deadline is 144 blocks, about a day, on channels under about 1.2 million sats, such as a 1,000,000-sat channel; after that a cheat can go unanswered. On the largest channels, about 16.8 million sats or more, it is 2,016 blocks, about two weeks. In between, it grows with the channel's size. A UPS keeps the node running through short power cuts, and a watchtower answers a cheat for you while you are away; on Umbrel, switch on Watchtower Client in the Lightning Node app and add a tower.
On channels the size this guide suggests, your node has about a day to answer a cheat. If you will be offline longer, run a watchtower; a UPS covers short power cuts.

Getting Inbound Liquidity

When you open a channel, all capacity starts on your side (outbound). To receive Lightning payments, you need inbound liquidity — capacity on the other side of your channels.

A 1,000,000-sat channel you open starts with all 1,000,000 sats on your side: you can send, but you can't receive yet. Three ways to make room to receive, each shown as a channel with some or all of its balance on your peer's side. Spend through it: what you pay moves to your peer's side, and you can then receive that much. Loop Out: pay Loop over Lightning and it sends the bitcoin back to you on-chain, minus fees, leaving room on the other side. A channel opened to you: another node funds it, through a LightningNetwork+ swap or bought on Lightning Pool or Magma, so it starts with everything on their side. You can receive only what sits on the other side of your channels.
You can receive only what sits on the other side of your channels. A channel you open starts with everything on your side, so make room by spending, by a Loop Out, or by getting a channel opened to you.

Methods to Acquire Inbound Liquidity

  1. LightningNetwork+ liquidity swaps: Join a swap ring where multiple node operators open balanced channels with each other. You open a channel to one peer, and another peer opens a channel to you.
  2. Lightning Pool / Magma: Marketplace services where you can purchase inbound liquidity from other node operators.
  3. Spend through your channels: Every payment you make shifts capacity from outbound to inbound. Buy gift cards via Bitrefill or pay invoices through your node to naturally build inbound liquidity.
  4. Loop Out: Lightning Labs’ Loop service converts Lightning balance to on-chain bitcoin, creating inbound liquidity. This costs an on-chain transaction fee plus a service fee.
  5. Ask for channels: If you run a service or accept payments, other node operators may open channels to you organically because routing to your node becomes profitable.

For a thorough treatment of liquidity management, see our guide on Lightning channel management best practices.

Security Hardening

Physical Security

  • Place your node in a secure, ventilated location with stable power.
  • Assume that whoever takes the drive can read it. umbrelOS documents no drive encryption, and Start9’s own guide prints the passphrase of StartOS’s encrypted data drive. Keep the node out of sight, and keep your seed on paper, away from it.
  • Ensure your router has a strong admin password and current firmware.

Software Security

  • Keep your node software updated. Check for Umbrel updates monthly.
  • Do not install unnecessary apps — each additional service increases attack surface.
  • If exposing services to the internet beyond Tor, use a reverse proxy with SSL.

Operational Security

  • Never share your node’s seed phrase digitally.
  • Limit the amount of bitcoin in Lightning channels to what you can afford to risk. Most home node operators keep the majority of their stack in cold storage.
  • Enable 2FA on your Umbrel dashboard if accessible remotely.

Costs and Ongoing Maintenance

ItemOne-Time CostMonthly Cost
Hardware (Pi 5 kit)$150 - $250—
Electricity (15W avg)—$1 - $3
Internet (existing connection)—$0
Channel fundingVariable—
On-chain fees (channel opens)About 150 sats per channel at 1 sat/vB; about 3,100 at 20 sat/vB—
Maintenance time—1-2 hours

The total cost of running a Lightning node at home is roughly $150-300 upfront and $1-3/month for electricity. Channel fees are small when the network is quiet: as of November 2026, 1 to 3 sat/vB is usually enough, though in busy periods rates have passed 300 sat/vB, so open and close channels when fees are low. The time investment is the real cost — expect to spend a few hours initially on setup and 1-2 hours per month on maintenance, updates, and channel management.

Part of our free Bitcoin course: This topic is covered in depth in Running a Lightning Node: Earning Sats and Supporting the Network from the Lightning Network & Bitcoin Nodes course.

FAQ

Can I run a Lightning node on a Raspberry Pi 4, or do I need a Pi 5?

A Raspberry Pi 4 with 4GB RAM can run a Lightning node, but for a node that holds channel funds, choose a Pi 5 or a mini PC. The Pi 5 offers faster initial blockchain sync and better performance when running multiple applications simultaneously. Use a quality SSD — this matters as much as the Pi model. If you plan to run umbrelOS, Umbrel recommends the Pi 5: it says USB drives can make a Pi 4 crash and calls the Pi 4 fine for tinkering, and many Pi 4 boards need a bootloader update before umbrelOS 2.0 will start.

How much bitcoin do I need to start running a Lightning node?

You can start with as little as 200,000 sats (0.002 BTC) to open a couple of small channels. For meaningful routing capability, 2,000,000 to 5,000,000 sats across 3-5 channels provides a solid foundation. There is no maximum — large routing nodes may deploy 1 BTC or more across dozens of channels.

Will running a Lightning node slow down my internet connection?

Not noticeably on a normal broadband connection. The first sync downloads the whole chain (about 780 GB of blocks as of October 2026). After that, Bitcoin.org puts downloads at about 20 GB a month, and a node that shares blocks with others can upload 200 GB or more a month. If your plan has a data cap, set Max Upload Target in the Bitcoin Node app’s settings to limit uploads. The Lightning part adds little on top. Any standard broadband connection (10+ Mbps) is sufficient.

What happens if my node goes offline for a few days?

Outages of a few hours are generally safe: your channels remain open, and peers wait before taking action. Longer is a risk, because a peer that publishes an old channel balance has to be answered before a deadline: with LND’s defaults, 144 blocks, about a day, on channels under about 1.2 million sats, rising to 2,016 blocks, about two weeks, on the largest. Extended downtime (weeks) also risks peers force-closing channels. If you may be away longer than a day, run a watchtower client from the day you open your first channel (a tower added just before a trip guards only the balances from then on), and turn on remote access (Umbrel’s Remote Tor access setting, or its Tailscale app) so you can check your node from anywhere.

Can I run Lightning alongside other services on the same hardware?

Yes. Platforms like Umbrel and Start9 support running Bitcoin Core, Lightning, Electrum Server, BTCPay Server, Nostr relay, and more on the same device. On a Raspberry Pi, stick to 3-4 services to avoid memory pressure. On a mini PC with 16GB RAM, you can comfortably run a dozen services simultaneously.

Filed under: Lightning Network & Layer 2
← Back to All Articles