Stuck "ChanStatusRestored" Channels — Funds Unspent On-Chain After Force Close

[Ellienat]

Summary

7 channels remain stuck in ChanStatusRestored on an Umbrel node hardware (Raspberry Pi 5, 2TB SSD).

• Channels 1–3: never fully opened, no on-chain funds, unsure why listed
• Channels 4–7: have confirmed on-chain funds
• Channel Allow for error-free build via go github.com/lightningnetwork/lnd/... #4: contacted remote node whom ran listpeerchannels and can confirm does not see this channel
• Attempted lncli closechannel --force fails with "cannot close with state ChanStatusRestored"
• 17 other channels from the same SCB restored correctly, funds returned to on-chain wallet

Environment: Umbrel Docker, LND v0.19.3-beta, Bitcoin Core v29.1, fully synced.

Background

Originally ran an Umbrel node on a Raspberry Pi 4 (1TB SSD). Pruned the blockchain on this node, but afterwards realized that a pruned node would not operate with Lightning channels correctly. Then attempted to resolve by removing the pruned state, which left the node completely unresponsive. Still have old hardware and SSD.

In attempt to recover my open channels, I ran a fresh Umbrel install, fully sync'd blockchain on a Raspberry Pi 5 (2TB SSD), new hardware. After the node fully sync, Umbrel prompted to recover from a backup file and start force closure of channnels (SCB), which was done. At the time, using the SCB forced-close did not realise this might not have been a poor decision as Umbrel recovery process appeared to be recommending this approach.

From this recovery, 17 other channels restored successfully with funds returned to the on-chain wallet. However, 7 channels remained stuck in ChanStatusRestored state now since Feb '25.

After investigating further attempted past suggestions without any luck.

The first 3x channels below I dont' think we ever opened properly but not sure why they are still listed as pending. Last 4x channels below have unspent funds.

I am able to contact remote peer from channel #4 although they can't see this as an open channel on their node.

I have installed chantools and attempted to triggerforceclose although appears to have not successfully run from the logs, but I haven't attempted this again in case its the wrong approach.

Expected Outcome

Pending channel to be closed and sats returned to onchain wallet.

Attached Log File with focus on SCB and errors

---

Pending Channels Output

 {
    "total_limbo_balance": "0",
    "pending_open_channels": [],
    "pending_closing_channels": [],
    "pending_force_closing_channels": [],
    "waiting_close_channels": [
        {
            "channel": {
                "remote_node_pub": "02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b",
                "channel_point": "1335e6432ac04ab08910aec478d4dc57a312bdb4dea5bb05926a5202118ee129:1",
                "capacity": "8000000",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 1 — never fully opened, no on-chain funds
        },
        {
            "channel": {
                "remote_node_pub": "02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b",
                "channel_point": "4105a41eded009e9613679e3f20cda9341b5165b3e2e9487179f3d00467b7533:0",
                "capacity": "15000000",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 2 — never fully opened, no on-chain funds
        },
        {
            "channel": {
                "remote_node_pub": "02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b",
                "channel_point": "f19365701f16995c70341a99cfc778f482f4581e801a69ebf33b0ae2144917ca:1",
                "capacity": "15000000",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 3 — never fully opened, no on-chain funds
        },
        {
            "channel": {
                "remote_node_pub": "02fe6a27ddcb2dd9fa8479fe1d52549b5932079a493b51f1409fa2c5878f1bc07c",
                "channel_point": "da72f710178fefb50ad13f44dbcf50aa00c04209484da62de2195fa26481b1b5:1",
                "capacity": "15000000",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 4 — has on-chain funds, remote node does not list this channel
        },
        {
            "channel": {
                "remote_node_pub": "039cd42c10b569257512d397ae5c7c3989f8559b286d656b61e0898c4673457842",
                "channel_point": "f06b449877da6843846bf18008aeff2cf7e1b97003a11a40962b236da4d21d92:0",
                "capacity": "6704988",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 5 — has on-chain funds
        },
        {
            "channel": {
                "remote_node_pub": "03a5b35380cb1d4d9ee90775a178b1a78afa61d03da0da15641cd4ca8e176bf3c9",
                "channel_point": "d158296b6bf032521c20e1b0b3355d55c830f30632f046d108dec878cda24a68:1",
                "capacity": "100000",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 6 — has on-chain funds
        },
        {
            "channel": {
                "remote_node_pub": "03c227a9003c1b2d176f5afad901066075e72343a24a1df9c3e7d74c7deaf76d4b",
                "channel_point": "4d8f37601d96dd803416a2612506073a77b19638bfbe107b6e78c4b322907f86:0",
                "capacity": "1000000",
                "local_balance": "0",
                "remote_balance": "0",
                "chan_status_flags": "ChanStatusRestored"
            }
            // Channel 7 — has on-chain funds
        }
    ]
}


[lnd_scb_scrubbed.log](https://github.com/user-attachments/files/22742276/lnd_scb_scrubbed.log)

[ziggie1984]

Regarding Channel 4,

can you peer do lncli listchannels --inactive_only and also
lncli pendingchannels and look for this channel there.

is this peer an LND node ?

For the other channels which were not force-closed, can you verify that the peers are online meaning they can essentially force-close the channel from their side?

[Ellienat]

Re Channel #4, I'll email node operator again now and ask them to report outputs/findings to your request above and post it here. On 1ML the owner info states: c-lightning,
linux; not sure if that confirms LND node.

Regarding rest of the channels, I've email all of these remote nodes a few times via lightninngnetwork.plus where I opened the liquidity swaps with no responses and on 1ML shows the nodes haven't been seen for awhile 'over 1 year' for most of them. I can't confirm but I suspect most are offline.

However channel 4 is definitely online but still hasn't closed.

I know channel #4 ran this request and got this output, nil:

listpeerchannels 02480372e95bc572b196c8a37d66098cf49b55dd841eaad5135ecf1255283ff0c4
{ "channels": []
}

[ziggie1984]

you can try this as well for channel 4: https://github.com/lightninglabs/chantools/blob/master/doc/chantools_triggerforceclose.md

[Ellienat]

Thanks @ziggie1984, I've tried using chantools triggerforceclose previously but was unable to trigger force close – getting a channel status manager error.

Here is the details.

Command used for channel 4:

export CHAN_ENABLE_TIMEOUT=10
export CHAN_STATUS_SAMPLE_INTERVAL=5
export CHAN_DISABLE_TIMEOUT=30

$HOME/go/bin/chantools triggerforceclose \
  --peer 02fe6a27ddcb2dd9fa8479fe1d52549b5932079a493b51f1409fa2c5878f1bc07c@65.108.134.61:9735 \
  --channel_point da72f710178fefb50ad13f44dbcf50aa00c04209484da62de2195fa26481b1b5:1

Error msgs received:

error connecting to peer: unable to create channel status manager: chan-enable-timeout + chan-status-sample-interval must <= chan-disable-timeout and all three chan configs must be positive integers

error requesting force close: error connecting to peer: error connecting to peer: unable to create channel status manager: chan-enable-timeout + chan-status-sample-interval must <= chan-disable-timeout and all three chan configs must be positive integers

Environment:

• chantools v0.14.1
• Peer reachable on clearnet (65.108.134.61:9735)

Notes:

• Tried both exporting the variables and setting them inline
• Values are positive integers and satisfy CHAN_ENABLE_TIMEOUT + CHAN_STATUS_SAMPLE_INTERVAL <= CHAN_DISABLE_TIMEOUT
• Error occurs immediately despite peer being reachable
• Tried using both Tor and Clearnet

Unsure why chantools refuses these settings even though they appear valid?

[ziggie1984]

seems like an error in the code, going to provide a fix

[ziggie1984]

provided a fix see here: lightninglabs/chantools#206

[Ellienat]

Thanks @ziggie1984 for finding a bug fix to code with @guggero

Unfortunately after successfully running triggerforceclose with most channels (with exception of a few of Tor that could not connect too), I am still unable to resolve the stuck channels.

What other options should I explore?

Other measures I have tried it recovering an old channel.backup and running the SCB again.

I've been able to recover files off my old node SSD such as channel.db, wallet.db, channel.backup and .macaroon files.

I don't have alot of experience though in try to recover channels with these files.

[guggero]

@Ellienat I added an additional fix in lightninglabs/chantools#207, can you try again with git pull && git checkout c94224d8 && make install?

[Ellienat]

@guggero with a new make install that had this fix in it confirmed, I ran this ( i assumed you meant me to run 'tiggerforceclose' again):

pubkey="02fe6a27ddcb2dd9fa8479fe1d52549b5932079a493b51f1409fa2c5878f1bc07c"
txid="da72f710178fefb50ad13f44dbcf50aa00c04209484da62de2195fa26481b1b5"
index="1"
peer="n56b3i5awpqmc4sdrh62pk4vztkjbkyy277pzj6i6rp6y5l2sellaoad.onion:9735"

echo "Triggering force close for $txid:$index with peer $pubkey at $peer"
chantools triggerforceclose \
  --peer $pubkey@$peer \
  --channel_point $txid:$index \
  --torproxy 127.0.0.1:9050

and got this output after numerous tries:

no spends found after 60 seconds, aborting re-try loop umbrel@umbrel:~/chantools-dev$

appears connection is being established successfully, log shows repeated force close attempts but after each attempt no spend found, idk

[guggero]

Okay, then there's nothing more chantools can do. Either the peer's CLN version is misbehaving or they themselves don't have the data for the channel anymore. So you can attempt to contact them (looks like they might be active on lightningnetwork.plus where you can send them a message).

[guggero]

Ah, make sure to try the triggerforceclose command a few times, it seems to be timing-sensitive, especially for CLN peers.

[Ellienat]

@guggero I let it run for quite some time now on and off last few days without any success unfortunately.

Then moved on to trying scbforceclose without success

2025-10-13 00:20:22.174 [INF] CHAN: No spends found yet, waiting 5 seconds... 2025-10-13 00:20:27.366 [INF] CHAN: No spends found yet, waiting 5 seconds... 2025-10-13 00:20:32.526 [INF] CHAN: No spends found yet, waiting 5 seconds... 2025-10-13 00:20:37.690 [INF] CHAN: No spends found yet, waiting 5 seconds... 2025-10-13 00:20:42.849 [INF] CHAN: No spends found yet, waiting 5 seconds...

[ziggie1984]

If contacting the other noderunners does not work out and they remain silent, you still have another chance to recover your funds look also at:

https://github.com/lightninglabs/chantools/blob/master/doc/chantools_scbforceclose.md

In the SCB file we safe the latest commitment transaction for every channel, however given that your node crashed (afaict) there might be the risk that this is an outdated state of the channel and you might get punished by your peers if thats the case and you might lose all your money on this channel.

Be aware of the risk !!!

[ziggie1984]

that's expected, you need actual channels, all those channels in your SCB are just shells for the restore process. The force-close transaction would be in there if there were actual channels. You probably never run with LND 19 when you node was still working ?

[Ellienat]

Probably not, my node was last properly working around Oct 2024, before pruning it, then unpruned it Nov2024 when it died. Then started up new node in Feb2025 and ran first SCB instance with umbrel in Feb2025 with new node restored from seed

[Ellienat]

@ziggie1984 I have old channel backups and channel db files prior to node crashing.

do I have any other options to resolve given amount of btc stuck?

[ziggie1984]

you could use the old channel.db and extract a commitment transaction, however there is a risk of it being out of date, and if your peer is online or uses a watchtower you will be punished.

[ziggie1984]

maybe wait until people show up, and if nobody comes abound in a couple of months take the risk ?