💡 The Plain-English Definition
A payment channel is a direct two-party agreement that allows unlimited Bitcoin payments to occur off-chain, with only the opening and closing transactions ever touching the Bitcoin blockchain. It’s the foundational unit of the Lightning Network.
🤔 But Why Though?
Every on-chain Bitcoin transaction costs a fee and takes time to confirm. For small or frequent payments — buying coffee, streaming micropayments, tipping content creators — these costs and delays make on-chain Bitcoin impractical. Payment channels solve this by pre-committing funds on-chain once, then allowing the two parties to transact freely off-chain, updating their balances instantly and for free (or near-free), before eventually settling the final state on-chain.
Opening a channel requires one on-chain transaction: one party (or both, in a dual-funded channel) deposits Bitcoin into a special 2-of-2 multisig output (a Bitcoin address requiring signatures from both parties to spend). This locking of funds is the channel’s capacity — the total maximum that can flow through it. Once open, the parties can transfer value back and forth as many times as they like by creating commitment transactions — updated records of who owns what — that are signed by both parties but never broadcast. Each update supersedes the last. The current balance state is always available to either party, but they only broadcast it when closing the channel.
Closing is either cooperative (both parties agree, sign a closing transaction dividing the funds, broadcast once) or a force close (one party broadcasts their most recent commitment transaction unilaterally if the other party is unresponsive — with a mandatory waiting period before funds are accessible, allowing the other party to dispute if the wrong state was broadcast). The Lightning Network (the broader payment network) is built by connecting millions of these channels — payments route through chains of channels between users who aren’t directly connected, using HTLCs (Hash Time-Locked Contracts — conditional payment structures that ensure atomicity: payments either complete fully or refund) to ensure no funds are lost at intermediate hops.
🌍 The Real-World Analogy
Think of a payment channel like running a tab at a pub. Instead of paying for each drink individually (separate on-chain transactions), you open a tab at the start of the evening (the channel open). Throughout the night you and your friend order drinks, with the bartender keeping a running tally of who owes what (commitment transactions). At the end of the evening you settle the final bill (the channel close) — one transaction, regardless of how many drinks changed hands. The Lightning Network is a city full of these pubs, connected such that you can pay anywhere in the city as long as there’s a connected route of tabs between you and your destination.
⚡ So What?
Payment channels are why Lightning payments are instant and cheap — the on-chain cost is amortised across as many transactions as the parties make. One channel can process thousands of payments for a single opening and closing fee. Understanding channels explains why Lightning requires initial capital commitment (the channel funding), why channels have capacity limits, and why the Lightning Network’s architecture is a network of bilateral agreements rather than a single payment system.