Lightning Preview

Hook

On-chain Bitcoin settles in blocks—usually minutes, sometimes longer when the waiting room is busy. Everyday small payments often want something closer to a tap. Lightning is Bitcoin’s answer for that speed: still bitcoin, moved a different way.

One idea

Lightning is a second layer on Bitcoin: you open a payment channel, move value back and forth off the main chain for a while, and settle to the base ledger when you close. Fast and usually cheap for small sends—not a replacement for learning on-chain first.

Plain walkthrough

Why a preview, not a course. This chapter is a map, not a how-to. You already practiced an on-chain send (Chapter 9): destination, fee, broadcast, confirmation. Lightning builds on that intuition. If send/receive still feels fuzzy, refresh Chapter 9 before chasing Lightning wallets or invoices.

What a channel is (picture it). Imagine two people keep a private tab of who owes whom, then write the final score on the public ledger when they stop. A Lightning channel is similar: both sides lock some bitcoin into a special on-chain setup, then update balances between themselves with signed messages. Those updates are not every small payment waiting for a new block. When the channel closes, the agreed balances land on-chain.

Still Bitcoin. Lightning does not invent a second coin. The units are bitcoin (often shown in sats). Security ultimately rests on the base chain’s rules and your ability to enforce a correct close if something goes wrong. Think different delivery, same asset—not “crypto apps” bolted on for their own sake.

What feels different in practice.

1. Speed — Payments inside healthy channels can feel near-instant compared with waiting for a confirmation.
2. Fees — Often much smaller for tiny amounts than a full on-chain transaction when block space is contested (Chapter 12). Exact costs depend on path and liquidity; this is mechanism, not a promise.
3. Invoices and liquidity — Receivers often show a Lightning invoice (a timed payment request). Channels need liquidity in the right direction; sometimes a route fails until capacity moves. That is normal network plumbing, not “Bitcoin broken.”
4. Custody still matters — Hot Lightning wallets hold keys for channel funds. Seed hygiene and scam habits (Chapters 7, 17, 18) still apply. A Lightning balance is not “safe because it’s fast.”

What we are not covering here. Channel factories, watchtowers, routing algorithms, force-closes, or which app to install. Those belong in Advanced / Under the Hood after you are comfortable with on-chain send, fees, and custody tradeoffs. If a guide skips “what happens if the other side disappears” or never mentions the base chain, treat it as incomplete.

When on-chain still wins. Larger amounts, long-term cold storage, learning the ledger, or anytime you want settlement that does not depend on channel partners being online. Lightning is a tool for frequent, smaller payments—not a reason to unlearn blocks and confirmations.

Watch-outs

• Skipping on-chain intuition — Without Chapter 9’s rhythm, Lightning looks like magic cards. Learn the base send first.
• “Lightning = free forever” — Fees can be tiny; they are not guaranteed zero, and on-chain open/close still costs block space.
• Confusing IOUs with channels — Custodial “Lightning balances” on an exchange are still company IOUs (Chapter 17). Mechanism of channels ≠ who holds your keys.
• Fake support / seed asks — Same scams, new costume. Nobody needs your seed to “open a channel for you.”
• This site is not a Lightning course — One-page preview only. Deep setup belongs later, on purpose.

You now can…

• Explain Lightning as Bitcoin via payment channels, not a separate money.
• Say why it can feel fast and cheap for small payments while still settling to the base chain when channels close.
• Know this is a preview: on-chain send first; full Lightning skills later under Advanced.