Replying to Avatar LNBϟG

I have a feeling that the node "c=" is experiencing some issues. The thing is, I've noticed that its capacity has decreased over the past few days. You can verify this yourself using the viewer at amboss.space. Another indirect sign of problems is that when I tried to cooperatively close channels with it a few minutes ago—channels that haven't been used for payments in 14 days—several channels were unable to be closed cooperatively, even though the node is online. This usually happens when a node has lost data about the channels. The node itself is online, but when a remote peer connects to it and requests, for example, to cooperatively close a channel that was with it, the node doesn't respond because it no longer has data about the channel. With this node, I have the feeling that this exact problem is occurring. It would be interesting to know from the owners of this node whether they are indeed experiencing any problems currently, whether they've had a failure or not. I think they have. #LightningNetwork
Avatar
Matt Corallo 9mo ago 💬 1

I don’t believe it is having any such issues. It absolutely would not “not respond” due to having lost data, it wouldn’t be online at all if it had (because if it’s architecture). I’m not sure about anything else but I’m unaware of any issues.

Reply to this note

Please Login to reply.

Discussion

Avatar
Matt Corallo 9mo ago

Checked looks like the node is working just fine. Can you share more about why your channel “wasn’t able to be closed cooperatively”? Usually that’s because of a feerate disagreement that causes a force-close (new protocol changes to address this coming to a node near you soon!), not (to my knowledge, from any implementation) “lost data”.