Churn (Lightning)

Channel churn is the rate at which Lightning channels are opened and closed on-chain. Some churn is unavoidable - users add/remove liquidity, channels go inactive, services rebalance. High churn is a problem because every channel open and close is an on-chain Bitcoin transaction with real fee cost.

What contributes to churn:

• Users opening channels they don't end up using much. Inactive channels eventually get closed to recover the locked capital.
• Liquidity rebalancing. Without splicing, the only way to change a channel's capacity is to close it and reopen. Frequent rebalancing = high churn.
• Custodial wallet operators who open and close channels in response to user activity.
• LSP onboarding flows that may rotate channels as user balances grow.
• Routing nodes managing liquidity across many counterparties.

Why churn matters:

• On-chain costs aggregate. A single channel costs ~$0.50-$5 to open and close at typical fees. A million-channel ecosystem with monthly churn is millions in Bitcoin transaction costs per year.
• Channel-history loss. When a channel closes, its accumulated routing reputation and gossip presence disappear. Reopening doesn't restore that history.
• Mempool pressure. Lots of channel closes during a single fee window push fees up for everyone.

How modern Lightning reduces churn:

• Channel splicing lets capacity be adjusted without closing. Major win, deployed 2024+.
• Better LSP designs open right-sized channels initially.
• Channel reuse for repeat customers via inbound liquidity services.
• Better wallet UX that doesn't push users to close channels unnecessarily.

Churn isn't the enemy; it's a normal feature of an evolving network. The goal is reducing unnecessary churn, which is most of it.