📅 Original date posted:2020-10-14
📝 Original message:
Bastien TEINTURIER <bastien at acinq.fr> writes:
> It's a bit tricky to get it right at first, but once you get it right you
> don't need to touch that
> code again and everything runs smoothly. We're pretty close to that state,
> so why would we want to
> start from scratch? Or am I missing something?
Well, if you've implemented a state-based approach then this is simply a
subset of that so it's simple to implement (I believe, I haven't done it
yet!).
But with a synchronous approach like this, we can do dynamic protocol
updates at any time without having a special "stop and drain" step.
For example, you can decrease the amount of HTLCs you accept, without
worrying about the case where there HTLCs being added right now. This
solves a similar outstanding problem with update_fee.
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 13:01:20
in reply to nevent1q…qqxd
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 13:01:20Event JSON
{
"id": "3cea7b6f081618b72a2b7d154491b4edefe246a8445ecb26393fe566e7d7a368",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686315680,
"kind": 1,
"tags": [
[
"e",
"979ba1732a5bff6ecbedadd53fb6514308c996861998729f33c9b71e23f85e90",
"",
"root"
],
[
"e",
"e16572129a4dff688fdf5e67740a470757d1d672744b3b1af6ff60f8e8d3375d",
"",
"reply"
],
[
"p",
"f26569a10f83f6935797b8b53a87974fdcc1de6abd31e3b1a3a19bdaed8031cb"
]
],
"content": "📅 Original date posted:2020-10-14\n📝 Original message:\nBastien TEINTURIER \u003cbastien at acinq.fr\u003e writes:\n\u003e It's a bit tricky to get it right at first, but once you get it right you\n\u003e don't need to touch that\n\u003e code again and everything runs smoothly. We're pretty close to that state,\n\u003e so why would we want to\n\u003e start from scratch? Or am I missing something?\n\nWell, if you've implemented a state-based approach then this is simply a\nsubset of that so it's simple to implement (I believe, I haven't done it\nyet!).\n\nBut with a synchronous approach like this, we can do dynamic protocol\nupdates at any time without having a special \"stop and drain\" step.\n\nFor example, you can decrease the amount of HTLCs you accept, without\nworrying about the case where there HTLCs being added right now. This\nsolves a similar outstanding problem with update_fee.\n\nCheers,\nRusty.",
"sig": "549245521ed29a1eb048120263a466fc1f0dcc4bb1baea1fd29f8a5aa7ddd26601b698ffb79a567c5b89cc69986f39839e1a312906eddcd15fe6d14e000106c9"
}