Overview
Opening a channel is the first step to transacting on the Lightning Network. It involves creating and broadcasting an on-chain funding transaction that locks bitcoin into a 2-of-2 multisig address controlled jointly by both channel parties. Once this transaction is confirmed on the blockchain, the Lightning channel is active and both parties can begin making off-chain payments.
Channel Opening Process
Step 1: Negotiate channel parameters
Alice ←──────────────→ Bob
(open_channel / accept_channel)
Step 2: Create funding transaction
Alice creates tx:
Input: Alice's UTXO(s)
Output: 2-of-2 multisig (Alice + Bob)
Amount: Channel capacity
Step 3: Exchange initial commitment transactions
Alice ←──────────────→ Bob
(funding_signed)
Step 4: Broadcast funding tx to Bitcoin network
Alice → Bitcoin mempool → Confirmed in block
Step 5: Channel is active (after N confirmations)
Alice ←═══════════════→ Bob
(channel_ready)
Capacity and Initial Balance
The total channel capacity is set at the time of opening and cannot be changed without closing and reopening the channel. Initially, all the capacity sits on the funder's side as outbound liquidity. Dual-funded channels (where both parties contribute funds) distribute the initial balance between both sides.
Costs and Considerations
Opening a channel requires an on-chain transaction, which means paying a mining fee and waiting for confirmations. Users should consider channel size carefully — a channel that is too small may not be able to route meaningful payments, while opening many small channels can be expensive in aggregate. Most Lightning implementations require a minimum of 3-6 confirmations before considering the channel active.
Common Misconceptions
Opening a channel does not mean the funds are "locked away" or inaccessible. The bitcoin in the channel can still be used for Lightning payments instantly. If needed, the channel can be cooperatively closed at any time, returning the funds on-chain. The bitcoin never leaves the user's control — it simply moves from an on-chain UTXO to a channel state.