Open whitslack opened 6 months ago
Now I have no way of pruning the unconfirmable transaction from my wallet.
Its existence was interfering with my using fundchannel minconf=0
, so I had to get rid of it. I manually deleted it from the outputs
table in the database, and it promptly stopped appearing in the output of listfunds
, so I hope that was a safe thing to do. :crossed_fingers:
Issue and Steps to Reproduce
Two same-valued outputs in the CLN wallet: one confirmed, one unconfirmed:
Decoding the unconfirmed transaction:
Decoding the confirmed transaction:
Points of note:
My best guess as to how this happened is that a mutual close was successfully negotiated, but then the peer broadcast their own unilateral close anyway, and the unilateral close is the one that got mined into a block. My node did not drop the mutual close transaction from its wallet when the peer's unilateral close confirmed.
Now I have no way of pruning the unconfirmable transaction from my wallet.
getinfo
outputI am running CLN v24.02.2.