What Lightning is
Bitcoin's base layer settles a few transactions per second with ten-minute blocks. Lightning is a second layer built on top: two parties lock Bitcoin in a shared on-chain transaction (a channel), then update the balance between them off-chain as often as they like, instantly and for almost nothing. Only opening and closing a channel touch the blockchain. Payments to people you do not have a channel with are routed through a path of channels, each hop forwarding the payment for a tiny fee, secured by hash time-locked contracts so that either the whole path succeeds or nobody loses funds.
The result is Bitcoin payments that settle in under a second for fractions of a cent — the property the base chain cannot offer.
The state of adoption
| Measure | Where it stands |
|---|---|
| Public channel capacity | On the order of 5,000 BTC, with a large and growing private (unannounced) share not counted |
| Exchange integration | Coinbase, Kraken, Binance, Bitfinex, OKX and others support Lightning deposits and withdrawals |
| Payment apps | Cash App and Strike route Lightning natively; many wallets (Phoenix, Breez, Wallet of Satoshi, Zeus, Muun) abstract channel management away |
| Merchant acceptance | Common in Bitcoin-focused communities and online services; not mainstream retail |
| Micropayment use | Nostr "zaps", pay-per-article and pay-per-API-call (L402 / machine-to-machine payments), streaming sats per minute for podcasts and video |
Two things changed the trajectory since 2023: wallets that manage channels automatically (so users never see the plumbing) and exchange support, which made Lightning the cheap way to move Bitcoin on and off major venues.
Micropayments that stuck
The use cases that survived are the ones where a sub-cent, instant, borderless payment has no alternative:
- Content tipping and zaps — small, frequent, cross-border payments to creators without a platform in the middle.
- Pay-per-use APIs and AI agents — a machine paying a few sats per request, with no account or card; the L402 protocol standardises the HTTP flow.
- Streaming payments — paying by the minute or by the megabyte.
- Remittance rails between apps — Strike-style transfers that use Lightning in the middle and local currency at the ends.
What has not happened: Lightning replacing card networks for everyday retail. It is a payment rail for Bitcoin, growing where Bitcoin is used.
Privacy: better in some ways, worse in others
- Better: individual Lightning payments are not recorded on a public ledger. An observer of the blockchain sees channel opens and closes, not what happened inside.
- Worse: routing nodes see part of each payment's path; the recipient's node identity is often public; channel opens and closes are on-chain transactions from your addresses, with all the usual chain-analysis exposure. Custodial Lightning wallets see everything.
- Net: Lightning is more private than on-chain Bitcoin for the payment, and not a substitute for a privacy coin for the holding. The privacy best practices rank the options.
Lightning and account-free swaps: the one thing to know
An instant swap gives you an on-chain Bitcoin deposit address. A Lightning invoice cannot pay it, and a Lightning wallet cannot send to it; they are different layers. Sending "to" a Bitcoin address from a Lightning-only wallet either fails or, in wallets that offer it, triggers an internal Lightning-to-on-chain conversion (a "swap out") with its own fee and delay.
If your Bitcoin is on Lightning and you want to swap it — to Monero, to a stablecoin, to ETH:
- Move it on-chain first. Use your wallet's "send to on-chain address" function (Phoenix, Breez and others offer this; it costs a fee and takes an on-chain confirmation), or withdraw from an exchange to an on-chain address, or close a channel.
- Then open the pair page — BTC → XMR, BTC → USDT (TRC-20), BTC → ETH — and send from the on-chain balance to the deposit address with a fee that confirms in one or two blocks.
In the other direction, a swap pays out on-chain Bitcoin — USDT (TRC-20) → BTC delivers to an on-chain address. To get it onto Lightning, receive it in a wallet that can open a channel or do a "swap in", or deposit to an exchange that supports Lightning withdrawals. Do not paste a Lightning invoice as a swap's receiving address; it will be rejected as an invalid Bitcoin address.
Frequently asked questions
Is Lightning safe for large amounts? Channels are secured by the Bitcoin chain, but node uptime and channel management matter; most users keep spending amounts on Lightning and savings on-chain.
Do I need to run a node? No. Modern wallets handle channels for you, custodially or non-custodially. Running your own node gives more control and privacy.
Why can't a swap accept Lightning? A swap needs a deposit it can verify on the chain it settles on; Lightning payments are off-chain between channel parties. Some services offer Lightning-specific swaps as a separate product; SyntheticSwap's Bitcoin pairs are on-chain.
What does a Lightning payment cost? Typically a few sats in routing fees — fractions of a cent. Channel opens and closes cost normal on-chain fees.
Is Lightning the same as Bitcoin? It is Bitcoin, moved through a different mechanism. One BTC on Lightning is backed one-for-one by BTC locked in a channel.
BTC → USDT (TRC-20)
USDT (TRC-20) → BTC