Run Your Own Lightning Node on Umbrel (LND or Core Lightning)

Q: What's the difference between LND and Core Lightning on Umbrel?

LND (Lightning Node Daemon by Lightning Labs) is the default Umbrel Lightning app and has the largest ecosystem of companion tools. Core Lightning (by Blockstream) is a leaner, spec-focused implementation that some advanced users prefer. For most people starting out, LND is the easier choice because more guides, wallets, and LSPs support it.

Q: What happens to my funds if my node goes offline?

Your on-chain bitcoin is safe — it's recoverable with your seed phrase. Bitcoin inside open channels is also yours, but channels will be force-closed by your peers if you're offline for too long (typically 2 weeks). Your counterparty can theoretically broadcast an old channel state while you're offline if they're malicious, which is why running reliably is important. The SCB file gets you back your funds after a force-close, not an instant recovery.

Q: Does the Static Channel Backup (SCB) save everything?

No — and this is important. The SCB lets you trigger a cooperative close of all your channels after a catastrophic failure. It does not restore your channel state or any in-flight payments. After recovery, your funds will be returned on-chain minus the closing fees and any routing fees owed. You don't lose your bitcoin, but you lose your channel graph and will need to reopen channels.

Q: How much bitcoin do I need to get started?

You can open a channel with as little as 20,000 sats, but the on-chain fees to open and close a channel make small amounts uneconomical — especially when fees are elevated. A realistic starting point is 500,000–2,000,000 sats per channel. Have at least two channels for redundancy.

Q: Can I receive payments immediately after opening a channel?

No — when you open a channel, all the capacity is on your side (outbound). You can send immediately, but to receive you need inbound liquidity. The easiest ways to get inbound liquidity are: buy a channel from an LSP like Voltage or Bitrefill's node, or use a service like Bitrefill's Thor to receive your first payment via a paid inbound channel.

Q: What Aussie nodes are good to connect to first?

Look for nodes with Australian IPs via amboss.space or mempool.space/lightning. Wallet of Satoshi runs well-connected nodes that are friendly for new channel opens. Bitrefill's node is useful if you shop there. For serious routing, Voltage offers managed LSP services with good global peering. There's no single 'right' answer — start with 1–2 channels to established, high-uptime nodes.

Running your own Lightning node is the full self-custody stack for Bitcoin. You hold your keys, you route your own payments, and you can connect any Lightning wallet to it — no third party involved. It’s also genuinely useful: payments settle in seconds, fees are fractions of a cent, and you can accept Lightning payments for goods or services without a custodial middleman.

The honest version of that pitch: Lightning is still rough around the edges. Channel management takes attention. The UX of pairing mobile wallets is improving but not seamless. And if your node dies without a proper backup, recovering your channel funds is stressful (though possible). This guide walks you through doing it right — with backups, with real channel strategy, and with realistic expectations.

Before starting, your Umbrel must be running and Bitcoin Core must be fully synced. If you haven’t done that yet, start with the Running a Bitcoin Node on Umbrel guide.

What you’ll need

An Umbrel node with Bitcoin Core fully synced (hardware options at Shop Bitcoin Australia)
Sparrow Wallet on your desktop — for sending bitcoin from your hardware wallet to your Lightning node’s on-chain address
Zeus or Blixt installed on your phone — for using Lightning on the go
At least 500,000–2,000,000 sats to fund your first channel (plus some extra for on-chain fees)

Warning: Everything in this guide involves real bitcoin. Test with small amounts first. Lightning is not a savings layer — it’s a payment layer. Keep the bulk of your stack in cold storage.

Step 1 — Choose your Lightning implementation: LND or Core Lightning

Umbrel ships two Lightning Network implementations in its App Store. You only need one.

LND (Lightning Node Daemon) — listed as “Lightning Node” in the Umbrel App Store (currently v0.20.0-beta, built on LND v0.20.1-beta). This is Umbrel’s default and what the majority of guides, mobile wallets, and LSPs support. If you’re just starting out, install this one.

Core Lightning — listed as “Core Lightning” in the App Store (currently v25.09.3-hotfix.1, developed by Blockstream). It’s leaner and more specification-compliant. Better for advanced users who want to run plugins or who specifically want CLN’s architecture. Fewer companion tools support it compared to LND.

This guide focuses on LND but notes CLN differences where relevant.

Open your Umbrel dashboard → App Store → search “Lightning Node” → Install. The app is around 400 MB and will download in a few minutes depending on your connection.

Step 2 — Let LND initialise and save your wallet seed

Once installed, open the Lightning Node app. On first launch, LND will generate a new wallet and show you a 24-word seed phrase.

Warning: Write this seed down on paper — or stamp it into metal — and store it offline. This seed controls your on-chain Lightning wallet. If your node is destroyed and you haven’t backed this up, those funds are unrecoverable. Do not screenshot it. Do not store it in a password manager unless you understand the risks.

Confirm the seed, set a wallet password, and LND will start syncing to the chain. This can take a few minutes — it’s reading from your local Bitcoin Core node, so it’s fast.

Step 3 — Back up your Static Channel Backup (SCB) immediately

Before you put a single sat into LND, set up your channel backup routine.

The Static Channel Backup (SCB) is a file (channel.backup) that LND maintains automatically. If your node dies, this file lets you trigger force-closes on all your channels and recover the on-chain funds. Without it, you’re relying on memory or your peers’ goodwill.

Where to find it on Umbrel:

Umbrel automatically backs up your SCB to your Umbrel account cloud (if you’re logged in). You can also access it manually:

umbrel.local → Lightning Node → ⋮ menu → Backup

Download the channel.backup file and store it somewhere separate from your node — a USB drive, a cloud folder, or email it to yourself. Update it every time you open or close a channel.

Tip: Umbrel also supports automated SCB uploads to your connected cloud account. Enable this in the app settings. It’s not a substitute for understanding what the SCB does — see the FAQ below — but it’s better than nothing.

What the SCB does and does not do:

✅ Lets you recover funds from all channels via cooperative/force-close after a node failure
✅ Works even if your channel peer has moved on
❌ Does not restore your channel state or in-flight HTLCs
❌ Does not make recovery instant — force-closes take on-chain confirmations (up to 2 weeks for the CLTV delay to expire)

Step 4 — Fund your Lightning on-chain wallet

LND has its own on-chain Bitcoin wallet. You send bitcoin to it, then use those funds to open channels.

In the Lightning Node app, click Receive → choose On-chain → copy the address. It will be a native SegWit (bc1q...) or Taproot (bc1p...) address.

From Sparrow Wallet (recommended):

If your stack is in a hardware wallet connected to Sparrow:

Open Sparrow → your wallet → Send
Paste the Lightning node address into the Pay To field
Set an amount — enough for 1–2 channel opens plus a buffer for on-chain fees. A practical starting amount is 0.01–0.05 BTC
Choose a fee rate appropriate for how urgent this is (check mempool.space for current fee levels)
Sign on your hardware device → Broadcast

Wait for 1–3 confirmations before proceeding to open channels.

Tip: Your LND on-chain wallet is a hot wallet by design — it needs to sign channel-open transactions automatically. Keep only what you intend to put into channels. Your cold storage stays cold.

Step 5 — Find your first peer: Aussie nodes and well-connected hubs

Before opening a channel, you need a peer’s node pubkey and address. A pubkey looks like:

03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f

Good first peers to consider:

Wallet of Satoshi — a well-connected, high-uptime node popular in the Australian Lightning community. Find their node URI on amboss.space — search “Wallet of Satoshi”.

Bitrefill — useful if you buy gift cards or top-ups. Their node is highly connected globally. Search “Bitrefill” on amboss.space.

Voltage LSP — voltage.cloud offers managed Lightning nodes and LSP services. If you want professional-grade inbound liquidity, they’re worth a look.

Finding Aussie nodes: Go to amboss.space or mempool.space/lightning, filter by country/region, and look for nodes with high uptime (99%+), recent activity, and reasonable fee policies. A node that’s been online for 6+ months with hundreds of active channels is a safe first peer.

Step 6 — Open your first channel

In the Lightning Node app → Channels → Open Channel.

Enter the peer’s pubkey (you can usually paste the full pubkey@ip:port URI), set the channel capacity, and confirm.

Channel sizing guidance:

Too small (< 100,000 sats): closing fees eat a large percentage; not worth it
Practical minimum: ~500,000 sats
A good first channel: 1,000,000–5,000,000 sats

The channel-open transaction needs 1–3 on-chain confirmations before it becomes active. At current fee levels (check mempool.space), expect to pay 300–2,000 sats in mining fees to open a channel.

Warning: Channel opening and closing fees are on-chain transactions. If the mempool is congested, these can be expensive. Don’t open or close channels frivolously — think of each channel as a long-term relationship with a peer.

Once confirmed, your channel appears as Active. All capacity starts on your side (outbound). You can now send payments.

Step 7 — Understand inbound vs outbound liquidity

This is the part of Lightning that trips up almost everyone the first time.

Outbound liquidity = bitcoin on your side of a channel = what you can send.

Inbound liquidity = bitcoin on your peer’s side = what you can receive.

When you open a channel with 1,000,000 sats, you start with 1,000,000 sats of outbound and 0 sats of inbound. You can send payments immediately, but you cannot receive until some of that liquidity shifts to the other side (via payments you make) or until you acquire inbound through other means.

Ways to get inbound liquidity:

Spend sats through your channel — every payment you make shifts capacity to the other side
Request an inbound channel from a peer — some nodes will open a channel back to you (especially if you’ve opened to them)
Use an LSP — Voltage, Bitrefill’s Thor service, or similar Liquidity Service Providers will open a paid inbound channel to you
Loop Out — LND’s Loop service (Lightning Labs) lets you swap on-chain sats for inbound liquidity via a submarine swap

For receiving payments from customers or friends, you’ll need to sort inbound liquidity first. Budget for it.

Step 8 — Send and receive your first payments

Sending:

In the Lightning Node app → Send → paste a Lightning invoice (a string starting with lnbc...). Confirm the amount and fee, then send. Payments settle in 1–5 seconds.

Receiving:

In the Lightning Node app → Receive → Lightning → create an invoice. Set an amount (or leave it as a generic “any amount” invoice for donations). Share the QR code or the invoice string.

The recipient scans or pastes it, and the payment arrives in seconds.

Tip: Lightning invoices expire — usually after 24 hours. Don’t share a static invoice and expect it to work days later. For a reusable payment link, look into LNURL or Lightning Address (e.g. [email protected]) as a layer on top.

Step 9 — Pair your mobile wallet: Zeus or Blixt

Your node is running at home. Your phone is not. These apps let you control your node remotely.

Zeus (remote control of your home node)

Zeus connects to your existing LND node over the network. It’s a remote control, not a separate wallet — your channels and funds stay on your node.

On your phone, download Zeus from the App Store / Play Store
On Umbrel: Lightning Node → Connect Wallet → Zeus → a QR code appears
Open Zeus → Connect a node → scan the QR code
Zeus connects via LNDConnect/REST — it works over Tor (which Umbrel enables by default) so it works globally, not just on your home Wi-Fi

You can now send and receive Lightning payments from your phone, with your own node.

Warning: Zeus over Tor can be slow to connect (10–30 seconds). This is normal. If it times out, retry — it’s a Tor circuit issue, not a node problem.

Blixt (embedded LND, different approach)

Blixt Wallet runs a full LND instance on your phone. It’s a separate node, not a remote control. Use Blixt if you want a self-custodial Lightning wallet that doesn’t depend on your home node being online. The trade-off: your phone needs to be online to receive payments, and your phone battery matters.

For most people who already have an Umbrel node, Zeus is the better choice because you’re leveraging the infrastructure you’ve already built.

Step 10 — Core Lightning: the alternative path

If you installed Core Lightning instead of LND, the flow is similar but the tools differ:

Umbrel app: “Core Lightning” (v25.09.3-hotfix.1)
Mobile wallet: Zeus supports CLN via the CLN REST plugin; Ride the Lightning is a solid web UI companion (also available in Umbrel App Store as “Ride the Lightning”)
Backups: CLN uses hsm_secret + a peer-backup scheme rather than SCB — back up hsm_secret (a binary file in the CLN data directory) offline
Liquidity: Same concepts apply — outbound vs inbound, same LSP options

Core Lightning is a fine choice but has a steeper learning curve and fewer companion apps. Switch to it once you’re comfortable with Lightning concepts.

Step 11 — Verification: confirm your node is healthy

Check the following after your first channel is active:

Channel status: Open the Channels tab — your channel should show as Active with a green indicator
Synced to chain: LND status bar should show the current block height matching mempool.space
SCB backup: Re-download your channel.backup file now that you have a real channel in it
Send a test payment: Use testnet.satoshis.me — on mainnet, send a small payment to a Lightning-enabled service like Bitrefill or Stacker News to confirm routing works

Troubleshooting

“Insufficient balance” when trying to send Your outbound liquidity is exhausted or the route can’t find enough capacity. Check your channel balances — if everything is on the remote side, you need to rebalance or open a new outbound channel.

Payment fails with “no route found” Your node may not have enough connected channels to find a path. Open 1–2 more channels to well-connected hubs (Wallet of Satoshi, ACINQ/Phoenix nodes, Bitrefill). A single channel gives you limited routing options.

Zeus says “Node unreachable” over Tor Tor circuits can be flaky. Close Zeus, wait 30 seconds, reopen. If persistent, check that your Umbrel node is online and that Tor is running (visible in the Umbrel system status panel).

Channel stuck in “Pending” for hours The channel-open transaction is waiting for confirmation. Check mempool.space with the txid shown in the Channels view. If fees were set too low, it may be stuck in the mempool. RBF (Replace-By-Fee) is not directly supported in LND’s UI — you may need to wait for mempool congestion to clear.

“SCB restore” — what to do if your node dies Re-install Umbrel, re-install Lightning Node, restore your 24-word seed, then import your latest channel.backup file via the restore interface. LND will broadcast force-close transactions to all peers. Wait for the CLTV timelock to expire (up to 2 weeks), then your funds return on-chain.

What’s next

Setting Up an Umbrel — if you haven’t set up your node yet, start here
Running a Bitcoin Node on Umbrel — make sure Bitcoin Core is fully synced before running Lightning
Bitcoin node hardware at Shop Bitcoin Australia — purpose-built hardware for running a reliable always-on node
Explore BTCPay Server (available in Umbrel App Store) if you want to accept Lightning payments for a business — it integrates directly with your LND node

Frequently Asked Questions

What's the difference between LND and Core Lightning on Umbrel?

LND (Lightning Node Daemon by Lightning Labs) is the default Umbrel Lightning app and has the largest ecosystem of companion tools. Core Lightning (by Blockstream) is a leaner, spec-focused implementation that some advanced users prefer. For most people starting out, LND is the easier choice because more guides, wallets, and LSPs support it.

What happens to my funds if my node goes offline?

Your on-chain bitcoin is safe — it's recoverable with your seed phrase. Bitcoin inside open channels is also yours, but channels will be force-closed by your peers if you're offline for too long (typically 2 weeks). Your counterparty can theoretically broadcast an old channel state while you're offline if they're malicious, which is why running reliably is important. The SCB file gets you back your funds after a force-close, not an instant recovery.

Does the Static Channel Backup (SCB) save everything?

No — and this is important. The SCB lets you trigger a cooperative close of all your channels after a catastrophic failure. It does not restore your channel state or any in-flight payments. After recovery, your funds will be returned on-chain minus the closing fees and any routing fees owed. You don't lose your bitcoin, but you lose your channel graph and will need to reopen channels.

How much bitcoin do I need to get started?

You can open a channel with as little as 20,000 sats, but the on-chain fees to open and close a channel make small amounts uneconomical — especially when fees are elevated. A realistic starting point is 500,000–2,000,000 sats per channel. Have at least two channels for redundancy.

Can I receive payments immediately after opening a channel?

No — when you open a channel, all the capacity is on your side (outbound). You can send immediately, but to receive you need inbound liquidity. The easiest ways to get inbound liquidity are: buy a channel from an LSP like Voltage or Bitrefill's node, or use a service like Bitrefill's Thor to receive your first payment via a paid inbound channel.

What Aussie nodes are good to connect to first?

Look for nodes with Australian IPs via amboss.space or mempool.space/lightning. Wallet of Satoshi runs well-connected nodes that are friendly for new channel opens. Bitrefill's node is useful if you shop there. For serious routing, Voltage offers managed LSP services with good global peering. There's no single 'right' answer — start with 1–2 channels to established, high-uptime nodes.