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
Discussion
Maybe nostr:nprofile1qqsrscyl3wmn5fq22463zftu3yt3yzskqetanj656jvnzhqllz4c7rqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdsq3qamnwvaz7tmwdaehgu3wwa5kuega6s5qw knows who to contact
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.
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”.
i work on the c= node. according to our logs those channels failed to close cooperatively because your node and ours couldn't agree on a closing feerate. in that case a force close follows.
unfortunately this happens sometimes with lightning, but our node is operating fine with no issues. thanks for bringing to our attention!
I recently closed a channel, no issues there. Based on my rating history (some metric generated by lnd-manageJ), the node simply did not perform well. The rating was OK/good until around January 22nd and dropped a lot afterwards. Note that the rating takes previous performance into account, so the actual change may have happened way before then.
Is your rating based on routing volume and channel utilization or on some other type of reliability metric? If the latter please let me know!
My c= channel is routing fine, I do notice however that the node is often very slow to respond. I keep latency metrics and the 30d average is over 7000ms.
I just reviewed the logs from March 9th, the day I was closing channels.
All the problematic channels were on my node edge-1, and almost all of them are now closed, but one channel still remains open (c11795b2b5e4ab295a4055ce387345341547d3880208cf6499a9352672f86e90:0).
I started examining the logs at that time and encountered the following error (lnd): "unable to gracefully close channel while peer is offline (try force closing it instead): channel link not found"
I believe it was some sort of desynchronization during peer-to-peer communication.