Gossip never seems to get a full take from Eclair/CLN

[TheBlueMatt]

We've seen a handful of reports that seem to indicate we don't succeed fetching gossip from CLN/Eclair. If I had to guess its because they don't sort the gossip into channel_announcements first, then channel_updates, then node_announcements, as required by the spec.

[rustyrussell]

We definitely do order it correctly. We do ratelimit to 1Mbyte/sec these days though?

[vincenzopalazzo]

We do ratelimit to 1Mbyte/sec these days though?

Probably someone is impacted, but not everyone. LDK is syncing correctly. Probably the problem that we are discussing here is a problem that people do not see channel_announcements that is a similar problem that I nodded between cln nodes

Working on producing a gossip observer tool in the next coming days (more weeks)

[TheBlueMatt]

Yea, I think its quite likely just that the peer in question doesn't have the whole gossip map. I guessed it was ordering because we get a lot of errors that look like ordering errors - is it possible that CLN (or others?) relay live channel_update gossip for SCID X when it is still doing a historical sync and hasn't yet reached X, thus making the channel_update an out-of-order error?

[vincenzopalazzo]

Sorry if took me so long to get back to this issue, but I think I finally had some real symptoms to report.

Probably not related to ldk but this is another symptom of this issue ElementsProject/lightning#7995

Gossip is not propagating through different implementations (not tested with ldk yet but I will) like LND, CLN and Aclair