LND Pending Channels -- Why Channels Get Stuck and How to Fix Them

Pending channels in LND sit in a limbo state between being opened and becoming active. This guide covers why channels get stuck and how to resolve them.

Types of Pending Channels

- Pending Open: funding transaction broadcast but not yet confirmed

- Pending Force Close: force close broadcast, waiting for CSV timelock

- Waiting Close: cooperative close broadcast, waiting for confirmation

Check Pending Channels

lncli pendingchannels

Pending Open — Channel Stuck

If the funding transaction is stuck (low fee), you may need to CPFP or RBF.

# Check funding tx in mempool
lncli pendingchannels | grep funding_txid

# Then check on mempool.space
# If stuck, use CPFP from your on-chain wallet

Pending Force Close — Waiting for Timelock

Force closed channels have a CSV (CheckSequenceVerify) delay, typically 144 blocks (~1 day). This is normal — wait it out.

# Check blocks until maturity
lncli pendingchannels | grep blocks_til_maturity

Recover Pending Force Close Funds

# After timelock expires, funds return automatically
# If not, try:
lncli wallet bump-closing-tx --txid <pending_txid>

Abandoned Channels

# If peer is gone and channel never confirmed:
lncli abandonchannel --funding_txid <txid> --output_index <index>

Warning: Only use abandonchannel if the funding transaction was never confirmed on-chain. Using it on confirmed channels will cause fund loss.

Common Issues

- Channel stuck for days: check if funding tx confirmed on-chain

- Force close taking too long: CSV timelock is working as designed

- Peer offline: channel will force close automatically after timeout