Nodes, Lightning and mining · Step-by-step guide

Lightning, practical.
A payment layer for everyday spending.

READ7 min·UPDATED·APPLIES TOAny country·LEVELIntermediate
For bitcoiners ready to use Lightning for daily payments. Sources are listed at the bottom of the page; check their dates before acting.

Lightning is a second layer on top of Bitcoin where payments settle almost instantly, for fractions of a cent, not a separate coin. You open a channel with an on-chainon-chainA Bitcoin payment recorded directly and permanently on Bitcoin's main public ledger, settled by the network itself rather than through a faster off-network lane.Full definition transaction, then send unlimited payments off-chain until you close it. You can use Lightning for daily spending, tips, and streaming sats.

Not financial advice. Lightning is still evolving. Software changes rapidly. Figures cited here change over time; confirm against current documentation before you act.

Short answer

Lightning is a second layer on top of Bitcoin. Two parties lock funds into a "channel" with an on-chain transaction. After that, they can transact between each other unlimited times, instantly, at near-zero fee. When they close the channel, the final balance settles on-chain. For small repeated payments, Lightning is dramatically cheaper than base-layer Bitcoin. For one-time large payments, on-chain is still the right answer. Phoenix Wallet is the easiest entry point for beginners.

On this page
  1. What Lightning is (in one paragraph)
  2. Opening and closing channels
  3. Inbound vs outbound liquidity
  4. Practical use cases
  5. Wallets
  6. When Lightning makes sense vs on-chain
  7. Watchtowers
  8. Known tradeoffs
  9. Backups depend on the wallet, not just Bitcoin
Lightning channel topology: Alice ↔ LSP ↔ Bob LAYER 2 · LIGHTNING (INSTANT, OFF-CHAIN) Alice 0.05 BTC CHANNEL #1 0.05 BTC capacity LSP HUB Liquidity routes HTLCs CHANNEL #2 0.10 BTC capacity Bob 0.03 BTC 10,000 sats from Alice → Bob routed through LSP via HTLC; instant settlement LAYER 1 · BITCOIN (10-MIN BLOCKS, ON-CHAIN) FUNDING TX (CHANNEL #1) one-time, when channel opens FUNDING TX (CHANNEL #2) one-time, when channel opens Payments along the route consume zero on-chain block space. The base layer is touched only at open / close / dispute.
Lightning payments route off-chain through pre-funded channels. The base layer is touched only at open and close.

What Lightning is (in one paragraph)

Lightning is a layer on top of Bitcoin. Two parties open a "channel" by locking funds in a shared on-chain transaction. They can then send unlimited payments between each other off-chain, near-instantly, with sub-cent fees. Each payment is a signed update to the shared balance. When they close the channel, the final balances settle back on-chain as a normal Bitcoin transaction.

Because nodes route payments through many connected channels, you do not need a direct channel with every person you want to pay. You just need a path through the network.

Opening and closing channels

Opening a channel is an on-chain Bitcoin transaction. That means it pays a regular Bitcoin fee, which can be cents or dollars depending on the mempoolmempoolThe waiting area for Bitcoin transactions that have been broadcast to the network but not yet confirmed in a block.Full definition. Once the channel is open, you can send thousands of Lightning payments through it at near-zero cost.

Closing the channel is another on-chain transaction. You pay another regular fee to reclaim the funds.

ECONOMIC LOGIC

Lightning makes sense for repeated small payments, where the on-chain channel costs amortize across many transactions. It makes less sense for one-time large payments, where the opening and closing fees dominate and the channel itself adds no advantage. Use Lightning for streaming sats, tips, and daily spending. Use on-chain for cold storagecold storageStoring Bitcoin on a device that's never connected to the internet, protecting it from online attacks.Full definition top-ups and large one-time transfers.

Inbound vs outbound liquidity

This is the hardest concept for new Lightning users, so slow down for it.

One abacus-style rod between two posts, beads gathered at each end and a single bead sliding across the middle.
A Lightning channel locks funds between two parties. Funds on your side are what you can send, funds on the peer's side are what you can receive, and each payment is an update that shifts the shared balance.
  • Outbound liquidityliquidityHow quickly and easily you can convert an asset to cash without significantly affecting its price.Full definition is BTCBitcoin (BTC)The ticker symbol for Bitcoin, used on exchanges and in price quotes.Full definition on your side of the channel. This is what you can send.
  • Inbound liquidity is BTC on the counterparty's side. This is what you can receive.

In a simplified channel, funds on your side provide outbound liquidity and funds on the peer’s side provide inbound liquidity. The spendable or receivable amount is below gross capacity because reserves, fees and in-flight payments can lock funds. Check your wallet’s available liquidity, not just total capacity.[1]

Freelancers, podcasters, and merchants all need inbound liquidity to receive payments. A wallet like Phoenix handles this behind the scenes by buying inbound capacity automatically. Self-managed nodes handle it manually.

Practical use cases

USE CASE 1
Receiving payments
Freelance invoices, podcast tips, value-for-value streaming (Podcasting 2.0). Settle in seconds, no chargebacks, global. Sats earned this way are ordinary income at receipt; see earning Bitcoin and taxes.
USE CASE 2
Buying things
Bitrefill for gift cards (Amazon, grocery, utilities), Strike for merchant checkout, growing list of Lightning-accepting online shops.
USE CASE 3
Tipping online
Nostr zaps, podcast value splits, Twitter (now X) tips. The first place Lightning became mainstream for a niche audience.
USE CASE 4
Remittance
Sending money across borders instantly for fractions of a cent. Services like Strike connect local fiat on both ends with Lightning in the middle.

Wallets

Phoenix is one option for small spending balances, not a universal best wallet. ACINQ manages channel operations, but fees and availability matter. Keep the app connected when expecting payments; operating-system background restrictions and offline periods can cause failures or force-closes.[1]

Self-managed LND or CLN

For the node-runner tier. You run your own Lightning node inside a Start9 or Umbrel install. You manage channels, inbound liquidity, and routing manually. More sovereignty, much higher complexity, a real time commitment. Only go this route if Lightning operation is something you actively want to do.

When Lightning makes sense vs on-chain

Lightning is right for:

  • Small daily payments
  • Streaming sats (podcasts, content)
  • Gift cards and merchant checkout
  • Tipping and zaps
  • Remittance with fiat on-ramps on both ends

On-chain is right for:

  • Large one-time payments
  • Cold storage top-ups
  • Inheritance and estate transfers
  • Anything that needs long-term settled finality
  • Any single transaction big enough that Lightning channel limits get in the way

Watchtowers

Lightning has one subtle trust assumption. If you go offline while your channel is open, a malicious counterparty could try to close the channel claiming an older balance state where they had more funds (cheating). Normally, an online node detects this and publishes the penalty transaction that takes their entire balance.

A watchtower monitors for revoked channel states when configured and supported. Do not assume a wallet includes one or that it removes offline risk. Follow your implementer’s monitoring and recovery instructions.[2][3]

Known tradeoffs

HONEST ABOUT LIMITS

Lightning is not fully private - your node's public ID is visible, and some routing info leaks. Channel management can fail during on-chain fee spikes. You have historically needed to be online to receive, though async receive is closing that gap. Liquidity management adds a mental overhead base-layer Bitcoin does not have. It is good, not perfect. A work in progress.

Backups depend on the wallet, not just Bitcoin

Lightning channels hold changing off-chain state. A seed-only on-chain recovery drill is not a universal Lightning recovery procedure. A custodial wallet instead relies on the provider’s account recovery and continued ability to return funds; you cannot reconstruct its balance from your own seed.

LND

Self-managed LND: the aezeed seed alone does not restore live channels. Keep the seed (and any cipher-seed passphrase) securely backed up, plus a separate current static channel backup, channel.backup, refreshed whenever channels open. SCB recovery contacts peers and asks them to force-close; it recovers funds on-chain rather than resuming the old channels. Peer availability, confirmations and sweep fees affect recovery. A stale channel.db is not a safe restore snapshot: broadcasting revoked state can trigger a penalty and lose channel funds. Use the implementer’s disaster-recovery procedure, not an ordinary laptop-backup restore.[2][4]

Core Lightning (CLN)

Self-managed Core Lightning (CLN): preserve hsm_secret or the supported mnemonic for your version, any required passphrase, and emergency.recover updated when a new channel opens. The root secret is necessary but insufficient for in-channel funds. CLN discourages snapshot database backups because stale state can cause permanent loss; use its documented real-time database backup/replication strategy. Static recovery is a last resort requiring peer cooperation, not a guarantee of continuing channels.[3]

Phoenix

Phoenix: follow ACINQ’s instructions for the current wallet version. Its documented wallet restore uses the 12-word recovery phrase in the authentic Phoenix app; payment-history backup is a separate matter. Do not run two Phoenix apps with the same seed. For force-closed channels, do not erase app data or uninstall before funds are recovered. Recovery may wait 720 blocks (roughly five days, sometimes longer) and incur on-chain fees; the FAQ’s Final wallet procedure explains the next steps. Do not force-close merely to test a backup or fix a routine issue.[1]

Safe preparation and recovery

Before funding: write down your wallet, version, backup types, storage locations and recovery-document URL offline; never put the actual secrets on this site. Practice on testnet or with a separate low-value setup following that implementation’s instructions. After failure: preserve available data, stop the old node, choose the documented recovery path and keep the old instance offline. Do not run two active copies of a self-managed node. Check each channel’s closing status and recovered on-chain funds before treating recovery as complete. If state freshness is uncertain, stop and seek official guidance without sharing keys.[3][4]

A watchtower is not a backup. Monitoring helps react to a counterparty’s revoked-state close within the dispute window; it does not recreate lost keys or your current channel database. Keep on-chain fee capacity and allow for force-close delays; offline use is not a free long-term storage mode.[2][3][4]

Where to go from here

Do next

Why Run a Node

Set up a personal node, the prerequisite for running your own Lightning channels.

Read next

Advanced Privacy

Continue into privacy hygiene, since Lightning leaks a node ID.

Explore further

Sources

Bracketed numbers in the text link to these sources. Figures, rates and rules change: check each source’s date before acting on it.

  1. Phoenix Wallet | FAQ, retrieved 2026-09-17. ↩
  2. Recovery: Planning for Failure | Builder's Guide, retrieved 2026-09-17. ↩
  3. Backup your wallet, retrieved 2026-09-17. ↩
  4. Disaster recovery | Builder's Guide, retrieved 2026-09-17. ↩
  5. Lightning Network specification (BOLTs) - github.com/lightning/bolts
  6. Phoenix Wallet documentation - phoenix.acinq.co
  7. LND documentation - docs.lightning.engineering
  8. Core Lightning (CLN) documentation - docs.corelightning.org
  9. Bitcoin Optech: Lightning topics - bitcoinops.org

Last updated . Not financial or legal advice. Disclosures · How pages are reviewed

Subscribe via RSS for new articles.