Opening a channel locks on-chain funds into a collaborative contract so you can send many off-chain payments later.
Why this matters
Without outbound capacity you cannot send. Without inbound capacity you cannot receive. Channel opens are the capital planning step of Lightning ops.
Analogy
Opening a channel is stocking a cash drawer between two cashiers. The total cash is fixed until you restock (splice/dual-fund) or close.
Open flow
Loading diagram…
# Illustrative LND-style flow
lncli connect <pubkey>@host:port
lncli openchannel <pubkey> <local_amt>Inbound vs outbound
- Outbound: your side’s spendable balance for sending
- Inbound: counterparty balance that lets you receive
New single-funded channels often start with outbound only, receiving may require liquidity strategies.
Common mistakes
- Opening to random public nodes without operational needs
- Ignoring on-chain fees and reserve requirements
- Forgetting backups after open
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
Study commitment transactions, the signed states that make channels safe.