We had some cases where channels were staying stuck in the CLOSING state without going to the CLOSED state in previous versions of eclair where we published different versions of our 3rd-stage transactions after a restart and a feerate increase.
This happened in two cases:
when we published a different version of our claim-main, since we only store the latest (it's an Option, not a Seq) and put a watch on this specific txid instead of watching the corresponding output
when we re-published 3rd-stage txs after receiving CMD_FULFILL_HTLC because we replaced the previous claim-htlc-delayed transactions
This was on my backlog for a while, and I wanted to take another look at it after the splicing implementation. Fortunately, this was fixed as part of the splicing changes, but it's worth having a test to ensure that there's no regression from future changes.
We had some cases where channels were staying stuck in the CLOSING state without going to the CLOSED state in previous versions of eclair where we published different versions of our 3rd-stage transactions after a restart and a feerate increase.
This happened in two cases:
Option, not aSeq) and put a watch on this specifictxidinstead of watching the corresponding outputCMD_FULFILL_HTLCbecause we replaced the previousclaim-htlc-delayedtransactionsThis was on my backlog for a while, and I wanted to take another look at it after the splicing implementation. Fortunately, this was fixed as part of the splicing changes, but it's worth having a test to ensure that there's no regression from future changes.