Simplified protocol for multiple in-flight updates.



Summary:

In a discussion regarding the simplicity of a protocol, Rusty Russell suggests that eliminating all acknowledgements would make it much simpler. However, when adding HTLCs, this may have some tradeoffs. The downside of doing this is that there is uncertainty about whether the other party has received the message. This means that once packets are sent over the wire, it should be assumed the other party can broadcast. To remove an HTLC securely, it requires removing the HTLC, committing, and then the other party revokes the prior commitment. If the ratio of success/failure is high enough, eliminating acknowledgements may be worth it. However, intermittently connected nodes may face some disadvantages as requiring confirmation has a significantly smaller time window for non-responsive payments. Joseph Poon notes that he is optimizing against payment failure on the ADD side, as failure may require a re-route in the opposite direction to do a full cancel with a non-responsive node in multi-hop payments. He agrees that if both nodes are well connected, then eliminating acknowledgements is more optimal if latency is the primary concern.


Updated on: 2023-05-23T22:34:08.175897+00:00