WhayPAY asked about 2 years ago

Channel auto Force Closed with partner & Fund Returns

So I got a question for the LN+ community. For some reason my node forced closed with the partner on here and were both confused on why. And second on how the funds were paid out, If the operator just lost half of their funds.

This was a triangle swap for 3m. With a automatic force close on one of the 3.
LNDg Info:
Rag3_Against_Fiat  | 3,000,000  | 3db9cfdc9f844e401814757b79ba2fbd821b5df4868af35bf67c7d4a616f9cd8  | (Settled Balance) 1,286,257  | (Locked Balance) 1,395,619  | (Close Height) 758,543  | (Close Type) Local Force  | (Opener) Remote  | (Closer) Local

4 Comments

LN+

LN+ Admin wrote about 2 years ago

The funds moved to one of their other channels when they routed earlier. That's how lightning nodes work. Nobody lost money.

Force close can happen because a channel appears closed and a payment is stuck.


EnduraUmb-I wrote about 1 year ago

Is there any chance using different configuration parameters to reduce likelihood of forced close? 
I see this as main contributor of fees (channel forced close and reopening fees). 

In some cases nodes were instable, in others no obvious reason was found. If there is no reason visible like channel partner offline for a longer period I am still looking for sources to find more details on root causes to eliminate them. Any descriptions know where to find hints for root cause analysis?


LN+

LN+ Admin wrote about 1 year ago

I'm not sure what to recommend right now, but will look and post if I find it.


EnduraUmb-I wrote about 1 year ago

thank you - asking mainly because  for me it sometimes looks like random (which it is hopefully not). At least it is not happening only to nodes known from logs as frequently being offline. In several cases both side were online for a while but still a forced close happened.
In most cases TOR nodes are affected, but this might be pure statistics issues on my side as I am not connected to many Clearnet nodes to do a proper comparison.

Please login to post comments.