Base AMP



Summary:

The email thread between Johan and ZmnSCPxj discusses the concept of merge nodes, which wait for the entire payment to be available and committed to as HTLCs before making claims. They assume that proof-of-payment is valuable and if the ultimate payee has not received all payments, it would be irrational to claim a partial payment since it would release the proof-of-payment for a value less than the value implied by the invoice. Similarly, intermediate nodes should forward a value only if it's greater than the current total value merging into it and it has assurances it can claim all values in a commitment transaction. This atomicity is economically rational and not information theoretically atomicity. Johan suggests renaming non-atomic payments and ZmnSCPxj proposes a `multipath_merge_per_hop` type to support Base AMP, allowing arbitrary merges of paths but not arbitrary splits, which may not be safe. The proposal defines the contents of the hop and specifies that the receiver must impose a reasonable timeout for waiting to receive all component paths and fail all incoming HTLC offers for the payment hash if they have not totaled equal to intended_total_payment. The sender must use the same payment_hash for all paths of a single multipath payment.


Updated on: 2023-05-25T16:30:54.125163+00:00