Lightning is not a separate coin. It is a second layer on top of Bitcoin where payments settle almost instantly, for fractions of a cent. You open a channel with an on-chain transaction, then send unlimited payments off-chain until you close it. For daily spending, tips, and streaming sats, Lightning is where Bitcoin actually works as money.
READING TIME: 7 MIN
Not financial advice. Lightning is still evolving. Software changes rapidly. Figures marked [VERIFY] should be confirmed against current documentation before you act.
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.
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 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 mempool. 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.
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 storage top-ups and large one-time transfers.
This is the hardest concept for new Lightning users, so slow down for it.
If your channel has a total capacity of 1 million sats and all of it is on your side, you can send 1 million sats but you cannot receive anything. If all of it is on the counterparty's side, you can receive but not send.
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.
Phoenix is the easiest Lightning wallet. Non-custodial, which means your keys stay on your phone. Behind the scenes, Phoenix auto-manages channel liquidity, handles opening and closing transactions for you, and even receives payments when you are offline (using trampoline routing and async receive). Recommended for anyone who wants Lightning without the complexity.
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.
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 is a third-party service that monitors your channels for cheating attempts while you are offline. For Phoenix users, watchtower functionality is built in. For self-managed LND, you add one explicitly, either running your own or paying a service.
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.
Last updated 2026-04-14. Not financial or legal advice.