On 4/21/22 1:31 PM, Alex Myers wrote:
Hello Bastien,
Thank you for your feedback. I hope you don't mind I let it percolate for a
while.
Eclair doesn't do any rate-limiting. We wanted to "feel the pain" before
adding
anything, and to be honest we haven't really felt it yet.
I understand the “feel the pain first” approach, but attempting set reconciliation has forced me to
confront the issue a bit early.
My thoughts on sync were that set-reconciliation would only be used once a node had fully synced
gossip through traditional means (initial_routing_sync / gossip_queries.) There should be many
levers to pull in order to help maintain sync after this. I'm going to have to experiment with them
a bit before I can claim they are sufficient, but I'm optimistic.
Please, no. initial_routing_sync was removed from most implementations (it sucks) and gossip queries
is broken in at least five ways. May we can recover it by adding yet more extensions but if we're
gonna add a minisketch-based sync anyway, please lets also use it for initial sync after restart
(unless you have no channels at all, in which case lets maybe revive initial_routing_sync...)
Matt
_______________________________________________
Lightning-dev mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
