Receiving Lightning Payments

Receiving a Lightning payment is slightly different from receiving on-chain Bitcoin — and worth understanding before you set it up.

On-chain Bitcoin: you generate an address, share it, and funds arrive whenever the sender decides to send. You don’t need to be online. The coins sit at the address until you spend them.

Lightning: you either generate an invoice for a specific amount and expiry time, or use a Lightning address that others can send to. Your wallet needs inbound liquidity — space on the receiving side of a channel — for the payment to arrive.

For most users with custodial or semi-custodial Lightning wallets, this is handled automatically. You share your Lightning address, someone sends to it, the money arrives. Simple.

For self-custodial Lightning, the inbound liquidity question matters more. A brand new channel has no inbound capacity — you’ve funded it from your side, so all the liquidity starts on your side. You can send but not receive until you’ve spent some first, or until someone opens a channel to you.

This is one of Lightning’s practical friction points. Most good wallets have solved it with automatic channel management or by maintaining a small custodial balance for receiving. But it’s worth knowing the mechanism.

The Lightning address format — username@domain.com — was one of the most user-experience-improving developments in Lightning’s history. Instead of generating a new invoice for every payment, you have a permanent, shareable address. Put it in your email signature. Put it on your website. Anyone with a Lightning wallet can send you sats instantly.

For anyone in your life ready to explore Bitcoin from scratch — this is the book written for exactly that starting point:

Bitcoin, Explained Without the Brain Melt — amzn.to/4dvqcyQ

Tomorrow: Bitcoin remittances — sending money home without losing 10% to fees.

— The Daily Bit