The Tradeoffs

Lightning is genuinely impressive. It’s also worth being honest about what it trades away for its advantages.

Online requirement. To receive Lightning payments, your wallet or node needs to be online. Unlike on-chain Bitcoin — where coins sit in a wallet address that anyone can send to at any time, regardless of whether you’re online — Lightning channels require both parties to be reachable for a payment to complete. Mobile wallets solve this with custodial or semi-custodial approaches, but pure self-custodial Lightning requires more management.

Channel liquidity. Payments can only flow where there’s sufficient liquidity in the channel network. Large payments — anything over a few thousand dollars — can struggle to route reliably because few single channels hold that much capacity. On-chain is still better for large, infrequent transfers.

Not suited to cold storage. Bitcoin held in deep cold storage for long-term savings shouldn’t be in Lightning channels. Lightning is for spending and receiving regularly. Cold storage is for holding securely. They serve different purposes.

Backup complexity. If a Lightning channel is force-closed by the other party while you’re offline, you need recent channel backups to recover your funds. Most good wallets handle this automatically — but it’s a layer of complexity that on-chain Bitcoin doesn’t have.

Still maturing. Lightning is roughly seven years old. The user experience has improved dramatically but it’s not yet as seamless as a credit card tap. Edge cases exist. Payments occasionally fail. The technology is real and working — but it’s not finished.

None of these are reasons not to use Lightning. They’re reasons to understand it clearly before you do.

Tomorrow: a story — the Lightning torch, revisited.

— The Daily Bit