The Lightning Network.
Bitcoin for everyday payments.
Lightning is a second layer built on Bitcoin for instant, nearly free payments. Compare how payment channels work, wallet choices, their limitations, and emerging layer-2 approaches.
Bitcoin's base layer settles approximately 7 transactions per second. That is fine for sovereign-grade settlement and savings. It is not enough for global retail payments. Lightning is a layer built on top of Bitcoin where payments settle instantly and cost a fraction of a cent. Custodial wallets (Strike, Cash App) are easy. Self-custodial wallets (Phoenix, Breez, Zeus) preserve sovereignty.
On this page
Section 1 · The problem Lightning solves
Bitcoin's base blockchainBlockchainA public transaction ledger, grouped into blocks that each link to the one before. Every Bitcoin full node checks each block itself and follows the valid chain with the most accumulated proof of work. Recent blocks can occasionally be replaced (a reorganization); the number of computers does not decide validity.Full definition processes approximately 7 transactions per second verify×DON'T TRUST, VERIFYClaim: Bitcoin's base layer processes approximately 7 transactions per second.Verify at: Bitcoin Wiki: Scalability ↗ Source 1 in the list below7 TPS is the commonly cited theoretical maximum based on average block size, transaction size, and 10-minute block times.. Visa processes approximately 8,000 transactions per second.
For Bitcoin to function as everyday payment money, not just as a savings asset, it needs a way to scale beyond the base layer. The Lightning Network is that scaling solution.
What Lightning is, in one paragraph
Lightning is a second layer built on Bitcoin. Think of Bitcoin's base layer like a settlement system, Fedwire for large dollar amounts, slow and final. Lightning is like cash, Venmo, or a tab at a bar, built on top of that settlement system: instant, cheap, works for small amounts, settles back down to the base layer only when the parties close their tab. Both layers share the same unit of account (satoshis). The difference is where the transactions live.
Section 2 · How payment channels work
Two people who transact often can open a payment channel: a direct line between their wallets with a shared balance.
Step by step
- Alice and Bob open a channel by together putting Bitcoin into a shared multi-signature address on the Bitcoin blockchain. This opening transaction costs a small miner fee.
- Alice can now send Bob satoshis instantly, off-chain. Bob can send back. They exchange cryptographic signatures updating the shared balance. No blockchain transactions. No fees.
- When done, either party can close the channel. The final balance broadcasts to the Bitcoin blockchain as a single transaction. One closing transaction regardless of how many payments happened in between.
Alice and Bob each put 0.01 BTCBitcoin (BTC)The ticker symbol for Bitcoin, used on exchanges and in price quotes.Full definition into a shared 2-of-2 address on-chain. One transaction, one confirmation (though multiple confirmations are typical for safety). Channel is open with a capacity of 0.02 BTC.
Alice pays Bob 0.001 BTC. Their balances update: Alice 0.009, Bob 0.011. This happens off-chain in milliseconds. They can exchange thousands of payments without touching the blockchainBlockchainA public transaction ledger, grouped into blocks that each link to the one before. Every Bitcoin full node checks each block itself and follows the valid chain with the most accumulated proof of work. Recent blocks can occasionally be replaced (a reorganization); the number of computers does not decide validity.Full definition.
When Alice and Bob are done, they broadcast a closing transaction reflecting final balances. One more on-chain transaction. Total on-chain: two transactions. Off-chain payments between them: unlimited.
The magic is the "punishment" mechanism: if one party tries to broadcast an outdated channel state to steal funds, the other party can take the entire channel balance as penalty. Watchtower services monitor for this on behalf of users who aren't always online. See Lightning Practical for the cryptographic details.
The network part
You do not need a direct channel with everyone you want to pay. If Alice has a channel with Bob, and Bob has a channel with Carol, Alice can pay Carol through Bob without a direct channel. This routing creates a network. Alice can pay anyone with a Lightning channel via any number of intermediate hops, in seconds.
Routing fees and safety
Alice can pay Carol through Bob without Bob ever taking custody of the funds. The protocol's HTLC (Hashed Time-Locked Contracts) mechanism makes sure Bob cannot steal the payment in transit.
Each hop takes a tiny routing fee, typically 0.01–0.1% or a fixed satoshi amount, depending on the route. A $10 payment typically costs less than 1 cent in total fees, even through multiple hops. Routing takes milliseconds.
Section 3 · Wallets
Custodial (easier, less sovereign)
- Strike: popular for US users, easy onboarding, links to bank accounts.
- Cash App: accepts Lightning, broad US adoption.
Risk: custodial means a company holds your Bitcoin. If they fail or freeze accounts, you may lose access. Not your keys, not your coins.
Non-custodial (harder, sovereign)
- Phoenix Wallet: the best non-custodial Lightning experience for most users. Self-custodied keys. Automatic channel management. Single fee model verify×DON'T TRUST, VERIFYClaim: Phoenix Wallet provides automatic channel management with a single fee model.Verify at: phoenix.acinq.co ↗ Source 2 in the list belowPhoenix is built by ACINQ, a major Lightning implementer. Verify availability in your region; the wallet is not available everywhere..
- Breez: non-custodial with built-in features for merchants.
- Zeus: advanced self-custodied wallet that connects to your own node.
Node + wallet (most sovereign)
Running your own Lightning node gives you the most control and privacy. Umbrel, Start9, and RaspiBlitz all support Lightning node operation. See Running a Bitcoin Node.
Real-world Lightning use today
Jack Mallers's Strike uses Lightning as rails to move dollars internationally. A U.S. sender deposits USD; the backend converts to Bitcoin, routes over Lightning, and delivers local currency on the receiving end. Near-instant, near-zero fee. Powers remittances from the U.S. to El Salvador and increasingly to other Latin American corridors.
Block (formerly Square) added Lightning send and receive to Cash App in 2022[3]. Tens of millions of U.S. users can now send sats via Lightning with the same UX as Cash App transfers.
Listeners stream satoshis per minute to podcast creators via the "Value for Value" protocol. Micropayments at a scale completely impossible on any traditional payment rail. This is Lightning's native use case.
Posts cost sats to publish. Upvotes pay sats to the poster. A quiet experiment in what online discussion looks like when micropayments are the medium. Proof-of-concept for social media without advertising.
Buy gift cards (Amazon, Uber, airlines, groceries) with Lightning. The practical spending bridge for Bitcoin holders who want to use their stack without selling through an exchange.
Open-source self-hosted payment processor. Merchants can accept Bitcoin and Lightning directly, with no intermediary, no chargeback risk, and no fees to Stripe or Visa. This is the third-party-free model.
Try Lightning right now
- Download Phoenix Wallet. iOS or Android. Self-custodial, Lightning-native, handles channel management automatically.
- Back up the wallet according to its exact implementation. Phoenix documents a 12-word restoration flow, but LND/CLN seed alone does not restore live channels. Read the wallet-specific recovery checklist below before funding.[4][5][6]
- Fund only a small amount you can afford to lose after checking the current wallet fees, liquidity costs and funding route. A tiny deposit may be uneconomic when on-chain fees are high.[6]
- Try it. Go to fountain.fm and stream a podcast while earning (or tipping) sats per minute. Visit stacker.news and zap a post. Buy a Bitrefill gift card with $5 in sats.
Allow time to verify the backup, funding fees, liquidity and receipt. Do not rush a first payment or promise yourself that setup will finish in minutes.[6]
Section 4 · The honest limitations
Liquidity
Payment channels need pre-funded liquidityliquidityHow quickly and easily you can convert an asset to cash without significantly affecting its price.Full definition. To send 100,000 sats you need 100,000 sats in an outgoing channel. To receive, a channel needs incoming capacity on the other side. Liquidity management is the main complexity for non-custodial users.
New Lightning users sometimes discover they can send but not receive until they open a channel or someone opens one to them. Phoenix handles this automatically; self-hosted nodes require attention.
Online requirement
Your node or wallet needs to be online to receive Lightning payments. Hardware wallets (cold storagecold storageStoring Bitcoin on a device that's never connected to the internet, protecting it from online attacks.Full definition) cannot receive Lightning payments while offline.
Channel-closing risk
If a peer publishes revoked channel state, timely monitoring and an appropriate response are necessary. Do not assume every wallet automatically handles every offline or data-loss scenario; inspect the exact implementation’s monitoring and recovery requirements.[4][5]
Not for large amounts
Lightning is designed for frequent, smaller transactions. Large transfers are better done 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. The two layers complement each other.
Channel capacities are typically in the low millions of sats. On-chain is better for moves above a few thousand dollars.
Channel management
Running your own Lightning node means actively managing channels: opening to good routing nodes, rebalancingrebalancingBuying and selling assets to restore your target portfolio split after market movements cause drift.Full definition, monitoring uptime. This is a hobby for some and a chore for others. Custodial Lightning hides this entirely but you give up self-custody of the Lightning balance.
Still maturing
Occasional routing failures, liquidity imbalances, and the occasional channel force-close require patience. UX is improving but not yet invisible.
A typical user-friendly setup today: Phoenix Wallet on mobile for everyday small transactions, handling channel management automatically through ACINQ's infrastructure. Advanced users run their own Lightning node on a Start9, Umbrel, or bare LND/CLN install. The experience is now comparable to Venmo for anyone who understands what's happening underneath. Lightning is now a daily-use payment layer that works.
Not financial advice. Lightning tooling evolves quickly; check the latest wallet docs before moving significant sums.
Section 5 · eCash, Liquid, and Ark (other layer-2 approaches)
eCash (Cashu, Fedimint)
Builds on the eCash concept from David Chaum in the 1980s. Fedimint is a federated mint where a group of trusted custodians hold Bitcoin and issue cryptographically private bearer tokens. Cashu is a simpler eCash implementation. Privacy advantage: eCash tokens are fully private; the mint cannot link tokens to identities. Trade-off: federated trust (you trust the mint operators not to rug you).
Liquid Network
A Bitcoin sidechain operated by a federation of exchanges and businesses. Faster settlement than on-chain Bitcoin. Supports issued assets and stablecoins on Bitcoin. Trade-off: federated, not as trustless as Lightning or the base layer.
Ark
A proposed protocol for off-chain Bitcoin transactions. Aims to solve Lightning's liquidity and receiving problems. As of early 2026 in active development, not widely deployed. Worth tracking but not yet a production option.
Lightning is Bitcoin's payment layer. It does not replace the base layer; it complements it. If you hold Bitcoin but have never sent a Lightning payment, you are missing half of what Bitcoin can do. The setup above is the shortest path from reading about Lightning to using it.
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.[4][7]
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.[5]
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.[6]
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.[5][7]
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.[4][5][7]
Where to go from here
Sources
Bracketed numbers and verify badges in the text link to these sources. Figures, rates and rules change: check each source’s date before acting on it.
- Bitcoin Wiki, Bitcoin Wiki: Scalability ↩
- Phoenix Wallet (ACINQ) · phoenix.acinq.co. ↩
- Block (Cash App) Lightning launch announcement, 2022 · block.xyz. ↩
- Recovery: Planning for Failure | Builder's Guide, retrieved 2026-09-17. ↩
- Backup your wallet, retrieved 2026-09-17. ↩
- Phoenix Wallet | FAQ, retrieved 2026-09-17. ↩
- Disaster recovery | Builder's Guide, retrieved 2026-09-17. ↩
- Bitcoin Developer Guide: Block Chain, retrieved 2026-09-17.
- Lightning Network whitepaper. Poon and Dryja, 2016 · lightning.network/lightning-network-paper.pdf.
- Breez · breez.technology.
- Zeus · zeusln.app.
- Fedimint · fedimint.org.
- Lightning Network specifications (BOLTs) · github.com/lightning/bolts. Canonical technical spec for Lightning clients.
- Fountain.fm (podcast micropayments via Lightning) · fountain.fm.
- Stacker News · stacker.news.
- Bitrefill · bitrefill.com. Gift cards and services purchasable with Bitcoin and Lightning.
- BTCPay Server (open-source self-hosted payment processor) · btcpayserver.org.
Last updated . Educational content, not financial advice. Disclosures · How pages are reviewed