Author: Rusty Russell 2019-11-08 02:55:17
Published on: 2019-11-08T02:55:17+00:00
The context discusses the message flow for a donation offer on a website. The process involves sending an invoice request via non-Lightning communication channels like https and receiving payment through the Lightning network. The use of `lno` and `lni` as HRPs is deemed incorrect, and alternatives are suggested. The discussion also covers the format and encoding of the data fields in the payment message, including the specification of currency codes and the use of UTF-8. The default offer of a node is described as an implicit offer that never expires and can be used by any node at any time to construct an invoice request. The concept of `refund_proof` is explained, which refers to a previous invoice paid by the sender. The article also highlights the need for paths in human-readable alternate encoding. Furthermore, the article explains the new `directed` message as the mechanism for sending invoice requests and receiving invoice request responses. Finally, the incentive for forwarding nodes to forward a `directed` message is discussed.
Updated on: 2023-06-02T21:38:50.847642+00:00