lightning community – Automated power closure and on chain settlement of expired HTLC

0
60


After roughly a month of largely easy operation a lightning node (LND 0.16.2-beta) mechanically initiated a power closure of a channel. Two days later an expired HTLC was settled on-chain. In each cases, excessive charges (~2-3 occasions the going fee) had been mechanically paid from the on-chain pockets of the node. Every thing occurred with none person intervention in any way. Listed below are the 2 transactions:

https://mempool.house/tx/71c18287c075bf3eb9a5083b98701faa87071266e5f0fe33577885fbb1180901
https://mempool.house/tx/2730193b26c2c2be70d20bb1e3f0e0d4eefed5283086320ae2f361af0f58aadf

The 2 transactions appear to be associated within the sense that the expired HTLC was attributable to the power closure.

So, I am looking for out what triggered the power closure. So far as I do know the lightning community protocol is designed to have the dangerous actors bear the price of their conduct and make everybody else complete, so I think that the node was misbehaving one way or the other?

  • Might or not it’s a connection subject (the node is barely reachable through TOR)?
  • How can the excessive charges for power closure/expired HTLC be averted sooner or later, is that this configurable anyplace?

In the event you want extra data (logs, and so forth.), I would be glad to ask the operator to supply them.

LEAVE A REPLY

Please enter your comment!
Please enter your name here