pull down to refresh

LNBIG discovered that "c=" node is experiencing some issues
759 sats \ 3 comments \ @DarthCoin 9 Mar lightning
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.
nostr source - nevent1qvzqqqqqqypzpx3eh7phep5dv8kcenn2f3aqawt0teduczp266ha64ykeds55glmqqsxvfj39lnwvdgadgqa74fnne70tnu4a8kd0eema6yrdm8fp4x9rscsqp9vh
write
preview
related posts
21 sats \ 1 reply \ @siggy47 9 Mar
I have been following the situation on nostr. The general consensus now is that the node is okay.
reply
136 sats \ 0 replies \ @DarthCoin OP 9 Mar
I know. I didn't post this note as a PSA, but more like an advice for node runners. Is not enough just to have a 24/7 online node because you see it so, but also to be reliable. Many people think that if you open 10-20 channels with well known nodes it means you are also a good node. That is totally false presumption.
There are many factors that can make a LN node unreliable:
  • Tor only connection
  • bad maintenance
  • data loss because of faulty hardware / not proper hardware. For a serious LN public node is always recommended to have ECC memory that can avoid a lot of data loss, especially for so much I/O is doing a LN node.
  • faulty software, not updating / syncing well, bad time response
And some other factors. So, node runners out there, be aware how you maintain your LN node.
reply
0 sats \ 0 replies \ @anon 9 Mar
If this is true it would be helpful if people connected to c= force-closed their channels to help c= get their money back. Also, if you are connected to c=, the data loss risks your funds too, as if you now screw up there is no way to get the money back; usually if you lose data you can get your counterparty to force-close for you to get your money back.
reply