📅 Original date posted:2019-01-02
📝 Original message:
Hello All, and Happy New Year!
To understand why there is a steady stream of channel updates, even
when fee parameters don't seem to actually change, I made hourly
backups of the routing table of one of our nodes, and compared these
routing tables to see what exactly was being modified.
It turns out that:
- there are a lot of disable/enable/disable etc…. updates which are
just sent when a channel is disabled then enabled again (when nodes go
offline for example ?). This can happen
there are also a lot of updates that don’t change anything (just a new
timestamp and signatures but otherwise same info), up to several times
a day for the same channel id
In both cases we end up syncing info that we already have.
I don’t know yet how best to use this when syncing routing tables, but
I thought it was worth sharing anyway. A basic checksum that does not
cover all fields, but only fees and HTLC min/max values could probably
be used to improve routing table sync ?
Cheers,
Fabrice
Fabrice Drouin [ARCHIVE] /
npub1s8…5yaw4
2023-06-09 14:53:50
in reply to nevent1q…y3d2
Author Public Key
npub1s8zghfrvyydu3ld5jrgue7crvzw8agyslpv8mh9pexgxwmcfelfsk5yaw4Published at
2023-06-09 14:53:50Event JSON
{
"id": "d71a59e03a5845f89072fab5c5f819aa40cd8eb25952ebc95887e6d83477a361",
"pubkey": "81c48ba46c211bc8fdb490d1ccfb03609c7ea090f8587ddca1c990676f09cfd3",
"created_at": 1686315230,
"kind": 1,
"tags": [
[
"e",
"fd0da5dbd5383b525edc98216d5094b180c1b831bf7af1f8df8ca35294a8c8fd",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2019-01-02\n📝 Original message:\nHello All, and Happy New Year!\n\nTo understand why there is a steady stream of channel updates, even\nwhen fee parameters don't seem to actually change, I made hourly\nbackups of the routing table of one of our nodes, and compared these\nrouting tables to see what exactly was being modified.\n\nIt turns out that:\n- there are a lot of disable/enable/disable etc…. updates which are\njust sent when a channel is disabled then enabled again (when nodes go\noffline for example ?). This can happen\nthere are also a lot of updates that don’t change anything (just a new\ntimestamp and signatures but otherwise same info), up to several times\na day for the same channel id\n\nIn both cases we end up syncing info that we already have.\nI don’t know yet how best to use this when syncing routing tables, but\nI thought it was worth sharing anyway. A basic checksum that does not\ncover all fields, but only fees and HTLC min/max values could probably\nbe used to improve routing table sync ?\n\nCheers,\n\nFabrice",
"sig": "2f3d707950486424234b8a80d37cf946e2ef203b4e6ae6794b43cf72a3548745a50fddf55b199e3b198c7b0bcad85feb6cf6299f46f38169f1716e096725a5cb"
}