Bitcoin in Practice

Using Lightning

Lightning works beautifully, but it behaves differently from on-chain bitcoin, and a few realities catch newcomers out. Here’s what actually using it looks like — the wallet choice, how you get paid, and the one genuinely new concept to understand.

The big choice: custodial vs self-custodial

  • Custodial wallets — the provider runs the channels for you (this platform’s own balance works this way). Dead simple, instant to start, nothing to manage — but it’s back to “not your keys”: you’re trusting the provider with your spending money. Perfect for small amounts and for onboarding someone in minutes.
  • Self-custodial wallets — apps like Phoenix, Breez or Zeus run channels from your own phone, so you hold the keys. Modern ones automate most of the fiddly parts. The trade-off is the familiar one: full sovereignty for a little more responsibility.

The sane rule of thumb: keep only pocket-money on Lightning, custodial or not, and keep real savings in on-chain cold storage.

How you get paid: invoices and Lightning addresses

  • A Lightning invoice — a one-time request for a specific amount, shown as a long string or QR code, that expires after a while. Ideal for a checkout: scan, pay, done.
  • A Lightning address — looks just like an email (you@wallet.com) and is reusable forever: anyone can send you any amount, any time, with nothing to generate first. It’s how tips, donations and payouts work — this platform sends winning-bidder payments and referral rewards straight to your Lightning address.

Liquidity — the one new idea

A channel holds a fixed amount, split between what you can send and what you can receive. Fund a brand-new channel yourself and the whole balance sits on your side — so you can spend, but you have no room to receive until some balance moves the other way. That’s why a newcomer sometimes sees “you can’t receive yet.” Spending shifts your balance toward the receive side, and receiving shifts it back. Increasingly, wallets and Lightning service providers arrange this inbound room for you automatically, but it helps to know why it exists: unlike an on-chain address, a Lightning wallet needs capacity in both directions.

Being online, and watchtowers

A channel is kept honest by the threat that either party can publish the latest agreed balance. So a self-custodial node ideally stays online — or delegates to a “watchtower” — so that a cheating counterparty can’t broadcast an old, more favourable balance and get away with it. In practice today’s wallets handle this quietly, but it’s the deeper reason Lightning suits everyday spending rather than money you intend to lock away untouched for years.

What it’s actually for

Micropayments and “streaming” sats (paying by the second, or per article), instant low-cost remittances across borders, machine-to-machine and AI-agent payments, and ordinary day-to-day purchases. The mental model is simple: savings live on-chain in cold storage; spending money lives on Lightning. Two layers, two jobs.

Lightning for spending, cold storage for saving. Treat a Lightning wallet like the cash in your pocket — convenient, and only ever carrying what you’d be relaxed about losing. Your long-term stack belongs in on-chain self-custody.

And if you’d like to run this layer yourself — route others’ payments, earn a little in fees, and depend on no one — you can stand up your own Lightning node. Core Lightning, next.

Key takeaways

  • The main choice is custodial (provider runs your channels — simple, but ‘not your keys’; good for small spending money) vs self-custodial (you hold the keys, e.g. Phoenix/Breez/Zeus). You receive with either a one-time invoice or a reusable Lightning address (email-like, LUD-16) used for tips and payouts.
  • Liquidity is the one new idea: a channel splits into send and receive capacity, so a freshly-funded channel can spend but not yet receive until balance moves. Rule of thumb: Lightning for spending, on-chain cold storage for saving.

Check yourself

Why might a brand-new self-custodial Lightning wallet be unable to receive at first?

What is a Lightning address (like you@wallet.com)?

Spotted an error or have feedback on this lesson? Suggest a correction ↗

Comments

Powered by Nostr — reply from any Nostr client, and zap the lesson over Lightning.