Short answer: Lightning is a network of two-party payment channels built on top of Bitcoin. Opening a channel is an on-chain transaction; after that, unlimited payments inside it settle instantly for a fraction of a cent, and only the final balance is written back to the blockchain.
The problem it solves
Bitcoin produces a block roughly every ten minutes and every transaction competes for space in it. That is excellent for final settlement of meaningful sums and unworkable for buying coffee. Lightning moves everyday payments off-chain while keeping Bitcoin as the court of final appeal.
How a payment channel works
- Two parties lock bitcoin into a shared on-chain address. That is the channel, and it costs one normal Bitcoin transaction.
- They then exchange signed balance updates privately — "now it's 0.004 to you, 0.006 to me". Each update invalidates the previous one, and no block is involved.
- Either side can close the channel at any time by broadcasting the latest balance to the blockchain.
The security model is that either party can always take their rightful balance on-chain, and an attempt to publish an outdated state can be punished by the counterparty taking the whole channel.
Routing: why you don't need a channel with everyone
You do not open a channel with each person you pay. Payments hop across existing channels, the way traffic crosses the internet. If you have a channel with a node that has a channel with the merchant, the payment routes through, secured by cryptographic conditions that make every hop atomic: either the entire path settles or nothing does. Nobody in the middle can take the money.
Lightning vs on-chain Bitcoin
| Lightning | On-chain | |
|---|---|---|
| Speed | Under a second | 10–60 minutes for confirmations |
| Fee | Fractions of a cent | Cents to many dollars |
| Amount range | Small to moderate | Any |
| Privacy | Better — payments are not broadcast | Public ledger |
| Setup | Channel liquidity required | None |
| Best for | Payments, tips, streaming money | Settlement, savings, large transfers |
The honest limitations
- Liquidity is directional. You can only receive as much as the far side of your channels can send. New wallets often need inbound liquidity before they can accept payments.
- Capital is locked. Bitcoin committed to a channel is not available elsewhere until the channel closes.
- Large payments route poorly. Above a certain size the path may not exist and the payment fails, though multi-path payments have improved this considerably.
- Node uptime matters if you run your own; most users sensibly delegate this to a wallet.
Choosing a wallet
Custodial Lightning wallets are trivially easy — the provider handles channels, and you are trusting them with the balance. Self-custodial wallets keep your keys and manage liquidity for you at the cost of occasional on-chain fees. A reasonable pattern is a self-custodial wallet with a modest spending balance and savings held on-chain in cold storage, as described in our wallet security guide.
Key takeaways
- Lightning is Bitcoin's payment layer, not a separate coin.
- Channels make payments instant and effectively free once opened.
- Routing removes the need for direct channels with every counterparty.
- Liquidity, not cryptography, is the practical constraint.
If you need to move between on-chain BTC and other assets, you can do it in one step on the Cryptozilla exchange.
Frequently asked questions
Is Lightning bitcoin the same as on-chain bitcoin?
Yes — the same coins, held in a channel rather than a simple address. Closing the channel returns the balance to a normal on-chain address.
What happens if the other party disappears?
You can close the channel unilaterally and claim your balance on-chain after a timelock. This is the core safety property of the design.
Are Lightning payments private?
More private than on-chain, since individual payments are not published to a global ledger. Routing nodes still see traffic passing through them, and a custodial provider sees everything you do.
