LND Force Close Channel — When and How to Do It Safely

Force-closing a channel is a last resort. Here is when it's appropriate and how to do it without losing funds.

When to force-close

- Peer has been offline for >2 weeks
- HTLC stuck for >48 hours and peer unresponsive
- Channel in BREACH_CLOSE state
- Cooperative close fails repeatedly

How to force-close

# Get channel point
lncli listchannels | python3 -c "
import json,sys
for c in json.load(sys.stdin)['channels']:
    print(c['channel_point'], c['remote_pubkey'][:20])
"

# Force close
lncli closechannel --force FUNDING_TXID:OUTPUT_INDEX

What happens after force-close

1. Transaction broadcast to mempool
2. CSV lockup period begins (usually 144 blocks = ~24h)
3. Funds return to on-chain wallet after lockup
4. Channel removed from listchannels

Monitor the force-close

lncli pendingchannels
# Watch 'waiting_close_channels' and 'force_closing_channels'
# 'blocks_til_maturity' counts down to fund recovery

Common mistake: force-close with active HTLCs

If you force-close while HTLCs are in-flight, they resolve via timeout/preimage on-chain. This can take up to 144 blocks per HTLC hop. Wait for HTLCs to clear if possible.

Need help with a stuck channel? $9

I'll diagnose your specific situation and recommend the safest path. USDT TRC-20.

→ Service page