Problem with update_channel gossip propagation across LND nodes (wrongly marked as zombie channels?). about lnd HOT 9 CLOSED

For the part relating to channels being marked as zombies when they have recent channel_updates, I think that will be addressed in the next release when #8030 is included.

As for the weird update horizon.... that seems like a different issue 🤔

from lnd.

@urza - as mentioned before, this should be addressed by #8030 which will be in the next release. So I dont think there is any work that needs to be done... hence the P3 status

from lnd.

In fact, I think we could even close this issue.

from lnd.

I connected to a friend with LND node (we don't have channel) and he has this in his terminal:

GossipSyncer - applying new update horizon: start=2106-02-07 07:23:15, end=2242-03-16 13:56:30

We have no idea what it means, but it doesn't look healthy :)

from lnd.

The two dates, when interpreted as seconds since 1970, correspond to 8589934590 and 4294967295 (ignoring the time zone?). The first number is double the second number. Furthermore, 4294967295 is 2^32 - 1. To me, this looks like some kind of default is used for both values.

from lnd.

ah also - if the LND node is printing this after receiving the GossipTimestampRange message from you (CLN) node, then it looks like it is CLN sending these dates

from lnd.

@saubyk I believe this deserves higher priority then P3. Because LND has such a high share of the whole lightning network, this issue causes that almost all nodes have very distorted view of the network graph.

This can be seen in public network explorers like amboss, 1ML and ligthtning lab's terminal. They have very wrong information about nodes. In last week I talked to many node operators trying to figure out my gossip issues, and almost nobody has correct information on these explorers about their node.

I now believe it is becuase LND doesn't propagate channel_update gossip messages when it should. And because it has such a high share of the network it is serious issue for the whole network.

from lnd.

@urza - as mentioned before, this should be addressed by #8030 which will be in the next release. So I dont think there is any work that needs to be done... hence the P3 status

Ok, I was more reacting to the "nice to have" description in P3 label.

from lnd.

Closing based on @ellemouton 's comment above. Feel free to reopen if the issue is not addressed after 0.18. Thanks

from lnd.