[DRAFT] Multi-cell-hop onion with TLV (and example for multi-part-payment)



Summary:

The conversation starts with a description of a proposed `application_data` type 6, which would work for spontaneous payments to identify the sender. The writer is of the opinion that the invoice should not specify it as it will create confusion and could lead to people doing dumb things. The writer suggests using it for games of chance where the user can put in a random number. The intent is to combine multi-use offers with spontaneous payments. It was mentioned that spontaneous payment would be useful when interacting with trust-demanding third parties, like Bitcoin banks, that hold Bitcoin on behalf of their customers. It was suggested that the bank would provide a multi-use offer containing the application data, which the customer would use by providing a spontaneous payment below.The conversation then switches to describe a proposed spontaneous payment type 8, which would sacrifice proof-of-payment, and the reader would claim the HTLC using the given preimage. The writer agrees that readers should reject spontaneous payments and wonders if it should be advertised on global features.


Updated on: 2023-06-02T15:08:11.201059+00:00