Opening a channel locks on-chain funds into a collaborative contract so you can send many off-chain payments later.
Complete Step 1 // Required reading in the study plan above, then continue here. This opens Channels & HTLCs.
Step 2 — Core idea: fund, confirm, activate
Channel opens lock capital on-chain. Whether you can send or receive depends on how balance is split — covered next in Channel Liquidity.
Analogy: Stocking a cash drawer between two cashiers. Total cash is fixed until you restock (splice/dual-fund) or close.
Loading diagram…
# Illustrative LND-style flow
lncli connect <pubkey>@host:port
lncli openchannel <pubkey> <local_amt>Single-funded opens usually leave the funder outbound-heavy. Do not route large value before your configured confirmation depth.
Done when: You can narrate open → funding tx → confirmations → channel_ready.
Step 3 — Try it: open on Polar (lab)
Connect two lab nodes and open a channel. Record local vs remote balance right after open.
Common mistakes
- Opening to random public nodes without operational needs
- Ignoring on-chain fees and reserve requirements
- Forgetting backups after open
Done when: Lab evidence (open proof + balance split + source link) is complete.
Next lesson
Channel Liquidity — why balance direction matters before you route a single payment.