ZmnSCPxj [ARCHIVE] on Nostr: š
Original date posted:2018-01-15 š Original message: Good morning Matt, > I ...
š
Original date posted:2018-01-15
š Original message:
Good morning Matt,
> I can't imagine the constants add up that fast... Allow 25 channels per peer and limit your peers reasonably and the cost should be low enough. Really not sure why something like a 25 channel limit should limit any usage or reasonably burden a node, what am I missing?
You impose this 25 channels per peer. I start opening a channel to you. Because I did not check mempool or because my fee-estimation algo is bad, I pay too low a fee. I become impatient and bump it up, which you perceive as another open (so it is now 2/25 channels). Unfortunately I only bumped my fee by a tiny amount, because reasons. I bump the fees upwards for example five more times, each of which you perceive as another channel open, so from your side it looks like I am consuming 7/25 channels. Finally the funding transaction confirms, but the 6 previous transactions are perceived by you as unconfirmed channel opens, so you will still keep the 6 channels accounted in your 25-channel-limit.
Suppose in a few days (i.e. much less than a week) I decide to have three more channels to you. If I go through all that (starting with low fee, bumping up fee, etc) then I may very well run out of the available 25 channels to you, even though I only really have 1 channel already opened and am trying to make an additional 3 channels only.
Granted this is somewhat contrived, but it shows what I wish to avoid with `funding_cancelled`.
Regards,
ZmnSCPxj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180114/f05d4b7e/attachment.html>
Published at
2023-06-09 12:48:27Event JSON
{
"id": "6d3255b726969e8e0306e65df3b03c8229c89e0a5af807565dcc7cb24ef101b8",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686314907,
"kind": 1,
"tags": [
[
"e",
"2a4926c7999f60c613526723369cef244df2cc105602a16cdb8a4a5833ba7a81",
"",
"root"
],
[
"e",
"f07322f1a670b8f2f888abb3ea32e16bebb1e69189483b96497665335c88629c",
"",
"reply"
],
[
"p",
"cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba"
]
],
"content": "š
Original date posted:2018-01-15\nš Original message:\nGood morning Matt,\n\n\u003e I can't imagine the constants add up that fast... Allow 25 channels per peer and limit your peers reasonably and the cost should be low enough. Really not sure why something like a 25 channel limit should limit any usage or reasonably burden a node, what am I missing?\n\nYou impose this 25 channels per peer. I start opening a channel to you. Because I did not check mempool or because my fee-estimation algo is bad, I pay too low a fee. I become impatient and bump it up, which you perceive as another open (so it is now 2/25 channels). Unfortunately I only bumped my fee by a tiny amount, because reasons. I bump the fees upwards for example five more times, each of which you perceive as another channel open, so from your side it looks like I am consuming 7/25 channels. Finally the funding transaction confirms, but the 6 previous transactions are perceived by you as unconfirmed channel opens, so you will still keep the 6 channels accounted in your 25-channel-limit.\n\nSuppose in a few days (i.e. much less than a week) I decide to have three more channels to you. If I go through all that (starting with low fee, bumping up fee, etc) then I may very well run out of the available 25 channels to you, even though I only really have 1 channel already opened and am trying to make an additional 3 channels only.\n\nGranted this is somewhat contrived, but it shows what I wish to avoid with `funding_cancelled`.\n\nRegards,\nZmnSCPxj\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180114/f05d4b7e/attachment.html\u003e",
"sig": "909836825ffeafef05a74fba76d78245bcd88dfe685fbe1df63aff750dd4b2858e9cc1bd4790b3333bb9b603139f466c64c7cef82915024ef12964493f34a595"
}