The Lightning Network scales Bitcoin payments by moving most transfers off-chain into bilateral payment channels. Users update balances locally and only settle on-chain when opening or closing channels.
Why this matters
On-chain block space is scarce. Instant coffee payments should not compete with large settlements for the same limited capacity. Lightning is how builders offer snappy UX without abandoning Bitcoin settlement.
Analogy
A channel is a bar tab between two friends. You keep a running tally (signed IOUs). When you are done hanging out, you settle the final balance once at the bank (on-chain). Routing is asking mutual friends to help settle tabs across a network of tabs.
Core concepts
Payment channels
Two parties lock bitcoin in a 2-of-2 multisig-style funding output. They exchange signed commitment transactions off-chain to update balances without publishing every change.
HTLCs
Hash Time Locked Contracts make multi-hop payments atomic: either the whole route completes, or it fails safely as timelocks unwind.
Invoices
BOLT11 invoices encode payment requests (amount, expiry, routing hints). Wallets decode before paying.
Loading diagram…
Before you build
Complete the Bitcoin roadmap first. Lightning assumes UTXOs, fees, scripts/timelocks, and regtest comfort.
Worked mental model
Re-read the diagrams in this lesson once out loud in plain language. If you cannot explain the flow to a friend without jargon, pause and revisit Mastering Bitcoin / Mastering Lightning chapters linked in Resources. Chapter references are intentional, not decorative.
Hands-on habit
Every protocol idea should be paired with one local experiment:
- Reproduce the happy path on regtest (or Polar for Lightning)
- Break it on purpose (wrong fee, expired invoice, offline peer)
- Write down what error you saw and which layer produced it (wallet, node, mempool, peer)
That habit turns reading into builder instinct.
Glossary check
Pick three terms from this lesson and define them in one sentence each without opening notes. Weak definitions mean the lesson is not finished yet.
Resource order
Use Resources in order: narrative book chapter first, then BIP/BOLT for precision, then implementation docs for commands. Jumping straight to RPC flags without the mental model creates brittle knowledge.
Next steps
Learn the BOLT specification landscape: how implementations stay interoperable.