Balanced Channel (Lightning)

A balanced channel is a Lightning channel where local and remote balance are roughly equal: both sides have meaningful capacity to send to the other. This is what routing nodes want for most channels, because a balanced channel can forward payments in either direction.

Why balance matters:

• For routing nodes. A 10M-sat channel split 5M / 5M can forward up to 5M in either direction. The same 10M channel skewed 9M / 1M can only forward 1M one way and 9M the other; the long-tail capacity is unusable until balance shifts back.
• For users. Skew has a direction. A new channel funded entirely by you (10M / 0M) lets you send but not receive. A channel funded entirely by your peer (0M / 10M) lets you receive but not send.

How balance gets out of whack:

• Asymmetric payment flow. Users send more than they receive (or vice versa); balance drifts to one side.
• Routing imbalance. Forwarded payments through a routing node shift balance toward the receiving side.
• One-sided channel funding. New channels usually start fully on one side.

How operators restore balance:

• Circular rebalancing. Pay yourself in a loop through other nodes, paying small routing fees to shift balance between your own channels.
• Submarine swaps (Loop, PeerSwap). Trade Lightning balance for on-chain balance and vice versa, effectively moving capacity in or out of channels without closing them.
• Splicing. Use Lightning channel splicing to add or remove on-chain funds from an existing channel.
• Liquidity ads / channel purchase. Open a fresh channel with the balance shape you need.

For end-user wallets, balance management is mostly automatic or invisible. For routing nodes, it's a daily operational task and the most important determinant of channel revenue: an out-of-balance channel earns no fees on the dry side until balance is restored.