pull down to refresh
0 sats \ 1 reply \ @antic OP 15 Dec 2023 \ parent \ on: PSA to Node Operators: Check coop-close-target-confs lightning
Ah, I see what happened now. So it looks like someone sent an HTLC through that timed out while one of you was offline. This is IHMO one of the most horrible node operator situations.
If one of the nodes is offline when a pending HTLC expires, instead of being canceled by both nodes cooperatively, it triggers a force close of the channel to resolve the HTLC on chain. If you were the recipient of the incoming transaction, theoretically you would have that HTLC balance as input from the source (prior to expire)—so what got taken from you on chain should be in your LN balance (just as a balance shift incoming from another channel). This is my understanding of it anyway. This hasn’t happened to me yet…
I’ve also heard of people saying that htlcs can just get stuck when nodes are both online and trigger this. Maybe if you are both tor only and your ping time is really long and tor just shat the bed…
Thank you for taking a look!
I think this would account for the HTLC expire tx, in that the sats are going to be in another channel.
I am at a loss on why it spent the whole onchain wallet on such high fees?
I think the bulk of the sats were spent from just broadcasting the claim tx's.
It blew away several small UTXOs, overspending to consolidate them.
Seems wise to have a minimal amount and few UTXO so high fees don't eat up large claims.
reply