To Node Zeniba: Local force close and claimed both our balances
Posted almost 3 years ago by AM_SB
I used to have two channels with your node "Zeniba", and in the past few days, I found that my node locally force closed the two channels but I actually didn't do it, my best guess is that this usually happens when the other node uses the static channel backup file to request me node to force close a channel
But I have other problem though, When this happened with me I can see I claimed my balance and your node's balance as well and I'm pretty lost in the explorer transactions and don't know what goes where, but I'm pretty sure I claimed both my balance and the your node's balance as well!!
But I have other problem though, When this happened with me I can see I claimed my balance and your node's balance as well and I'm pretty lost in the explorer transactions and don't know what goes where, but I'm pretty sure I claimed both my balance and the your node's balance as well!!
3 Comments
LN+ Admin wrote almost 3 years ago
You very likely didn't claim their balance, it's just their balance has been moved to your side in the past due to forwarding. That's normal and it's how LN works. The channel balances are not static. They move around your channels when you forward funds for other nodes.
AM_SB wrote almost 3 years ago
No, I mean what I said, I know what the settled balance is and I know what the remote balance is, I claimed BOTH and I have no idea why!
SCP-096 wrote almost 3 years ago
This sound scary, so I allowed myself to check your closing txs.. Doesnt look like penalty TX . My understanding would be there was active / stucked htlc, (perhaps 100k sat self payment between both channels?) and one of the peers, probably zeniba could do some major changes, like node upgrade while there were still those two active htlc (that seems to correlate to many of these "spooky" remote force closures.. in a buggy way). In such case, closing tx will have additional output corresponding to this not yet expired htlc..
Something similar happened to me as well and its very annoying. Hopefully bugs will get fix, but for now it may be safer practice for node operators to wait with major node updates etc, until there is no any active htlc.. Unless you are one of the biggest routers around, you should be able to find such moment..
Something similar happened to me as well and its very annoying. Hopefully bugs will get fix, but for now it may be safer practice for node operators to wait with major node updates etc, until there is no any active htlc.. Unless you are one of the biggest routers around, you should be able to find such moment..
Please login to post comments.
Latest news
Shutting down the node
Posted almost 3 years ago