📅 Original date posted:2022-04-21 📝 Original message: On 4/21/22 1:31 PM, Alex ...

Matt Corallo [ARCHIVE] /

npub1e46…xmcu

2023-06-09 13:05:52

in reply to nevent1q…xnwg

📅 Original date posted:2022-04-21
📝 Original message:
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

Author Public Key

npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu

Seen on

wss://relay.noswhere.com wss://relay.nostr.band

Show more details

Published at

2023-06-09 13:05:52

Kind type

1 Short Text Note

Event JSON

{ "id": "84817a79819d3e1343830dbdc839418ede04a0996b6cdf5d003291afb6a78d4b", "pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba", "created_at": 1686315952, "kind": 1, "tags": [ [ "e", "90c8a22893d09190339208f6b0eb636d6de40a2b6c7cff5708a261796a93b71e", "", "root" ], [ "e", "0eba9308d3d005f6badf9826653ef64f4e1f546b9272e3a2549a62cf2bc2faf9", "", "reply" ], [ "p", "52b603cc7527b671d1636a488828123ae7e57dadefec3b4182df7f134485426e" ] ], "content": "📅 Original date posted:2022-04-21\n📝 Original message:\nOn 4/21/22 1:31 PM, Alex Myers wrote:\n\u003e Hello Bastien,\n\u003e \n\u003e Thank you for your feedback. I hope you don't mind I let it percolate for a while.\n\u003e \n\u003e Eclair doesn't do any rate-limiting. We wanted to \"feel the pain\" before adding\n\u003e anything, and to be honest we haven't really felt it yet.\n\u003e \n\u003e I understand the “feel the pain first” approach, but attempting set reconciliation has forced me to \n\u003e confront the issue a bit early.\n\u003e \n\u003e My thoughts on sync were that set-reconciliation would only be used once a node had fully synced \n\u003e gossip through traditional means (initial_routing_sync / gossip_queries.) There should be many \n\u003e levers to pull in order to help maintain sync after this. I'm going to have to experiment with them \n\u003e a bit before I can claim they are sufficient, but I'm optimistic.\n\nPlease, no. initial_routing_sync was removed from most implementations (it sucks) and gossip queries \nis broken in at least five ways. May we can recover it by adding yet more extensions but if we're \ngonna add a minisketch-based sync anyway, please lets also use it for initial sync after restart \n(unless you have no channels at all, in which case lets maybe revive initial_routing_sync...)\n\nMatt", "sig": "e9612a78d43ba6cdcf3215bf36dd2e50586d030af4cbaf2a96555f569bd08896ccc06dedc5360dfef8b25dcb008894f27e1d8db4e17bde82b6234d9282f67691" }