Lightning Limitations

Part 8 has covered what Lightning does well. It’s worth ending with an honest account of where the gaps remain.

Large payments. Lightning works best for small to medium amounts — a few hundred dollars and below routes reliably. Larger amounts struggle because few individual channels hold sufficient liquidity and routing a large payment across multiple hops requires each hop to have adequate capacity. On-chain remains better for significant transfers.

Receiving without being online. If your phone is off and someone sends to your Lightning address, the payment may fail or queue depending on your wallet setup. On-chain Bitcoin has no such requirement — coins arrive at your address whether you’re online or not.

Cold storage incompatibility. Bitcoin held for long-term savings belongs in cold storage, not Lightning channels. Lightning is for actively circulating funds. The security model is different. Most serious holders keep their savings on-chain and use a separate, smaller Lightning balance for spending.

Channel management complexity. For self-custodial users managing their own channels, rebalancing inbound and outbound liquidity is a real operational task. Good wallets abstract most of this — but it’s still more complex than on-chain Bitcoin.

Still maturing. Payment failures still occur — perhaps 1-5% of payments in challenging routing situations. The network has improved dramatically but it’s not yet as reliable as Visa for all payment types in all corridors.

Watchtowers. If you go offline for an extended period, a malicious channel partner could attempt to close the channel with an outdated state. Watchtower services monitor for this on your behalf — but it’s an added dependency that on-chain Bitcoin doesn’t require.

Lightning is a powerful tool with real limitations. Understanding both is how you use it well.

Tomorrow: a story — the freelancer who switched to Lightning payments entirely.

— The Daily Bit