Author: Christian Decker 2017-12-28 11:31:55
Published on: 2017-12-28T11:31:55+00:00
The article discusses the issues with splitting single payments into multiple invoices. It is stated that this approach has bad semantic properties and makes the payment no longer atomic, which can lead to problems if channel capacity is exhausted partway through a transaction. The article goes on to explain that multipath payments are a simple solution to this problem, as long as both the sender and recipient know how to handle them. It is technically possible to do this without using multiple invoices, but it increases complexity for the recipient. The article also states that the current protocol limits are like training wheels, but they may not always be necessary in the future. It is possible to change these limits on a per-channel level, and an upgrade can be performed using feature bits without the need to fork lightning. The article concludes by saying that larger channels can be used in the multi-hop layer, and that these changes will make lightning more useful for intended applications.
Updated on: 2023-05-24T17:14:08.837436+00:00