NewsCryptoForced Bitcoin Lightning Exits Are Cheap but Can Lock Funds for Days, Study Finds

Forced Bitcoin Lightning Exits Are Cheap but Can Lock Funds for Days, Study Finds

Author: CryptoNewsNet·

Key Takeaways

  • •New research by Saurabh Kumar of Bitcoin Data Labs, released as a November 12 preprint, reviewed 973,581 Lightning channel closures spanning January 2018 to October 31, 2026, of which 523,815 were forced exits.
  • •Median fees for 2026 forced closures reached 925 satoshis per channel across both participants, roughly 4.7 times the 197-satoshi median recorded for cooperative closes.
  • •Parties who unilaterally shut channels in the 2026 sample faced a median 2.5-day wait before their own balances became eligible to be swept, versus a 1.7-day median across the entire study window.
  • •The waiting period stems from the BOLT 3 specification's to_self_delay output, which gives the channel peer time to penalize a broadcaster that publishes a revoked channel state.
  • •A break-even analysis showed the cost of waiting on locked balances would equal force-close fees at a 1.2% annual return in 2026, down from 16.7% over the full period, indicating the wait can outweigh fees in low-fee environments.
Forced Bitcoin Lightning Exits Are Cheap but Can Lock Funds for Days, Study Finds

Forced exits from Bitcoin's Lightning Network can carry surprisingly low fees while leaving users unable to reach their funds for days, according to new research on channel closures.

Channel exits come in two forms on Lightning: a cooperative close that both channel partners sign, and a forced close, in which one party settles alone by publishing its most recent commitment transaction.

In a 2026 sample of public channels, forced closures cost a median of 925 satoshis (Bitcoin's smallest unit) per channel across both parties, while the party that initiated the closure waited a median of 2.5 days before it could reclaim its own balance, according to a November 12 preprint by Saurabh Kumar of Bitcoin Data Labs.

Kumar examined 973,581 channel closes from January 2018 through October 31, 2026, of which 523,815 were force closes. The detailed 2026 cost cohort covers 14,435 public force closes through October 4, leaving four weeks to follow their outputs.

For comparison, the paper reports a 2026 cooperative-close median of 197 satoshis, putting the ratio between force-close and cooperative-close medians at 4.7 to one. The force-close total includes the commitment transaction, required balance sweeps, pending-payment resolution, observed same-block owner fee bumps and later owner anchor cleanup, with batched spending fees divided among inputs.

Why the balance stays locked

A unilateral close uses a previously signed commitment transaction to settle a channel on Bitcoin. Under Lightning's BOLT 3 specification, the output returning the broadcaster's own balance carries a delay known as to_self_delay, giving the peer time to penalize a broadcaster that submits a revoked channel state.

The 2.5-day figure measures the wait before that balance becomes eligible to be swept. It does not promise wallet receipt at that moment, and it does not describe the speed of ordinary Lightning payments. Across the whole study period, the reported median wait was 1.7 days.

The distinction matters for operators that need accessible funds while a channel is settling. A cheap exit can still leave capital unavailable for days, and its fee alone does not reveal how much immediately usable liquidity remains.

Kumar compares those costs using a break-even annual return: the rate at which the broadcaster's locked-balance waiting cost would equal force-close fees. That rate was 1.2% in 2026, versus 16.7% over the full period. The calculation compares per-channel fees across both parties with the broadcaster's locked balance, excluding pending-payment amounts. It illustrates how the wait can outweigh fees in a low-fee environment; it does not assume that operators earned that return.

How fees are paid under BOLT 3

The same distinction between fees and accessible funds applies to BOLT 3's zero-fee commitment design, which changes how miners are paid. A child transaction supplies the commitment's mining fee through child-pays-for-parent — a technique in which a higher-fee descendant transaction makes the parent worthwhile for miners to confirm — while transactions resolving conditional pending payments, known as HTLCs, obtain fees through added inputs. The broadcaster's delayed balance remains part of that design. Removing a fee from the pre-signed transaction therefore leaves both a paid settlement path and a waiting period to account for.

Measurement boundaries

The findings have limits. Private cooperative closes are absent from the data, splices are excluded from the close counts, and simple-taproot delays, HTLC resolutions and fee bumps are unclassified in the cost analysis. Confirmed-chain records cannot show failed or replaced fee bumps.

The released repository contains code and aggregate outputs, while the underlying scan tables, channel lists and gossip snapshots are available from the author on request.

For operators, the findings make access to funds part of the exit bill, alongside the transactions needed to recover them.