Author: Rusty Russell 2018-10-24 06:36:52
Published on: 2018-10-24T06:36:52+00:00
The Lightning developers have been discussing the addition of a splice feature to the protocol, which would allow nodes to add or remove liquidity from channels without closing them. The developers have now proposed a design for the splice feature which includes a distinct message that references an active channel ID and a splice channel ID for the pending splice. The proposal also suggests adding a splice-reject message/error code to signal when a local tolerance for the number of pending splices has been reached. The developers have also discussed the need for both parties to send channel updates with the option_channel_moving bit set and continue to keep the channel in their routing table. Additionally, the developers have suggested allowing both sides to modify parameters such as CSV param, reserve, max accepted HTLCs, max HTLC size, etc., as the size of the channel is either expanding or contracting. The developers have also discussed the benefits and drawbacks of resetting the revocation sequence post-splice, but ultimately decided against it due to the current atomicity perspective. Finally, the developers have considered the potential scalability issues with increasing the maximum values of these parameters.
Updated on: 2023-05-25T14:10:38.202226+00:00