Quick analysis of channel_update data



Summary:

Fabrice Drouin has shared detailed information on the data he collected, which includes 17,000 channel IDs and 130,000 different channel updates. On average, each channel has been updated eight times. However, only 18,000 pairs of channel updates carry actual fee and/or HTLC value change, meaning that 85% of the time, information was queried that had previously been received. This can happen in two legitimate cases: when a node is updated too fast or during the weekly refresh of channel_update. To handle this, Fabrice suggests discarding the newer duplicate unless it is more than one week old. Additionally, to avoid requesting duplicates again in future advanced reconstruction schemes, they could remember the latest timestamp of the duplicate. Fabrice also proposes adding a basic checksum that covers fees and HTLC min/max value to channel range queries as this would be a significant improvement. Such a checksum could also be used in inventory-based gossip messages and set reconciliation schemes. However, Rusty questions whether all these measures are necessary.


Updated on: 2023-06-02T16:49:36.307667+00:00