Core Lightning stuck channel / force-close TX rejected with missing-inputs

[angelohori]

Title: Core Lightning stuck channel / force-close TX rejected with missing-inputs

Umbrel Core Lightning v25.09.3 with Bitcoin Knots.

Problem channel:

peer_id:
03da872791c43022c0bad6dc46b0e5f2fa7b92f635aeacf1aab55285cf41343e3f

channel_id:
b22d58d0e22b17b274e03a8f061e3516f699c9fdabeb0e7e6d17976ff07514e5

funding_txid:
e51475f06f97176d7e0eebabfdc999f616351e068f3ae074b2172be2d0582db2

funding_outnum:
0

Current CLN state:
AWAITING_UNILATERAL

State change:

Forcibly closed by close command timeout
Force-close TXID:
a60d81dcc52307133fad88fc1c0841a4ad3a22fe07e699693754e7c5c3af2f2d

Bitcoin Knots testmempoolaccept result:
allowed: false
reject-reason: missing-inputs

CLN listtransactions shows the force-close TX with blockheight: 0.

Bitcoin Knots does not see the funding output as unspent.

Question: What is the safe recovery path for this channel state? Should this be handled with CLN rescan/recovery tooling, and what exact commands are safe to run?

[daywalker90]

I can't find the funding txid on my node. Is it possible this channel never actually opened?

[cdecker]

Sounds like it, yes, the funding TX never made it into the blockchain, and the closing TX is just a courtesy for the peer, essentially returning the funds to the funder should the funding TX ever accidentally be broadcast.

@angelohori do you happen to have a copy of the funding TX, or its inputs so we can check whether it was double-spent or not?

[angelohori]

Sounds like it, yes, the funding TX never made it into the blockchain, and the closing TX is just a courtesy for the peer, essentially returning the funds to the funder should the funding TX ever accidentally be broadcast.

@angelohori do you happen to have a copy of the funding TX, or its inputs so we can check whether it was double-spent or not?

i try to answer to your eMail you send to me but your mail address is full