đź“… Original date posted:2019-01-03
đź“ť Original message:
Follow-up: here's more detailed info on the data I collected and
potential savings we could achieve:
I made hourly routing table backups for 12 days, and collected routing
information for 17 000 channel ids.
There are 130 000 different channel updates :on average each channel
has been updated 8 times. Here, “different” means that at least the
timestamp has changed, and a node would have queried this channel
update during its syncing process.
But only 18 000 pairs of channel updates carry actual fee and/or HTLC
value change. 85% of the time, we just queried information that we
already had!
Adding a basic checksum (4 bytes for example) that covers fees and
HTLC min/max value to our channel range queries would be a significant
improvement and I will add this the open BOLT 1.1 proposal to extend
queries with timestamps.
I also think that such a checksum could also be used
- in “inventory” based gossip messages
- in set reconciliation schemes: we could reconcile [channel id |
timestamp | checksum] first
Cheers,
Fabrice
Fabrice Drouin [ARCHIVE] /
npub1s8…5yaw4
2023-06-09 12:53:50
in reply to nevent1q…z7tv
Author Public Key
npub1s8zghfrvyydu3ld5jrgue7crvzw8agyslpv8mh9pexgxwmcfelfsk5yaw4Published at
2023-06-09 12:53:50Event JSON
{
"id": "2093eeb48076e13c53d4d88f19640ac4e4ad31865a01dc46a78cf5cca7f4772e",
"pubkey": "81c48ba46c211bc8fdb490d1ccfb03609c7ea090f8587ddca1c990676f09cfd3",
"created_at": 1686315230,
"kind": 1,
"tags": [
[
"e",
"fd0da5dbd5383b525edc98216d5094b180c1b831bf7af1f8df8ca35294a8c8fd",
"",
"root"
],
[
"e",
"19cedde4ce27ce2c9638cc4926e56023d61d0d6d6940c696ae28e304c76f3be7",
"",
"reply"
],
[
"p",
"81c48ba46c211bc8fdb490d1ccfb03609c7ea090f8587ddca1c990676f09cfd3"
]
],
"content": "📅 Original date posted:2019-01-03\n📝 Original message:\nFollow-up: here's more detailed info on the data I collected and\npotential savings we could achieve:\n\nI made hourly routing table backups for 12 days, and collected routing\ninformation for 17 000 channel ids.\n\nThere are 130 000 different channel updates :on average each channel\nhas been updated 8 times. Here, “different” means that at least the\ntimestamp has changed, and a node would have queried this channel\nupdate during its syncing process.\n\nBut only 18 000 pairs of channel updates carry actual fee and/or HTLC\nvalue change. 85% of the time, we just queried information that we\nalready had!\n\nAdding a basic checksum (4 bytes for example) that covers fees and\nHTLC min/max value to our channel range queries would be a significant\nimprovement and I will add this the open BOLT 1.1 proposal to extend\nqueries with timestamps.\n\nI also think that such a checksum could also be used\n- in “inventory” based gossip messages\n- in set reconciliation schemes: we could reconcile [channel id |\ntimestamp | checksum] first\n\nCheers,\n\nFabrice",
"sig": "7d91f11b0f3cd7101bdba4c13b1527156367fc83cf83f3027da5c191a2eb143836294ae899fbba7c618990d2be3063e837f9d8f7591f1b24efbfd6a3cf1e7f21"
}