Gossip Propagation, Anti-spam, and Set Reconciliation



Summary:

In an email conversation between Rusty Russell and Matt Corallo, they discussed the issue of nodes hitting the spam limit due to rate-limiting. Rusty proposed setting a widely-agreed limit between once per block and every 1000 blocks to avoid aggressive spamming from nodes. However, Matt argued that the sync system should not rely on this number too much. Inconsistent rate-limit policies cause issues during sync and changing the limit would be difficult. They also talked about gossip2 enabling taproot and using blockheight as timestamps, which could support one operation and a direct query op. Additionally, they mentioned how LND nodes had some channels left disabled due to rejecting more than one update per day, and this problem will occur if anyone does ratelimiting unless everyone does. Finally, Matt suggested using an "update-based-sketch" gossip sync approach to reduce the damage caused by inconsistent policies.


Updated on: 2023-06-03T08:30:08.448203+00:00