Closing Transaction Cut-through as a Generalization of Splice-in/Splice-out [combined summary]



Individual post summaries: Click here to read the original discussion on the lightning-dev mailing list

Published on: 2018-04-13T13:10:56+00:00


Summary:

ZmnSCPxj and Christian discuss the connection between channel factories and propose alternative methods for channel reseating. ZmnSCPxj suggests that if there is a way to invalidate a prior funding transaction without needing a cut-through, the connection between channel factories is unnecessary. ZmnSCPxj proposes introducing a `reseatchannel` command at the c-lightning RPC level, which would transfer the remaining funds of a channel from one peer to a new channel with another peer. This can be achieved using current operations before the deployment of Burchert-Decker-Wattenhofer channel factories.The proposal also introduces the idea of implementing a more general "cut-through" for a channel close transaction. Instead of splice-in/splice-out, both parties would provide signed normal transactions that spend the outputs and create a new close transaction that cuts through the original close transaction and additional normal transactions. Incomplete and unsigned stubs could also be provided, which would be applied to the closing transaction. Inputs in the stubs would be added to the closing transaction as inputs, while outputs would be added to the closing transaction, drawing from the balance of the party adding the new output. This allows for multiple splice-in/-out operations in a single reseat operation.The proposed cut-through generalization is useful for "reseating" a channel from one peer to another. For example, if a node notices that a channel with one peer has a high probability of failing to forward payments, it could decide to close that channel and open a channel with another peer. This reseat operation could be done off-chain if the reseat-form peer, reseat-to peer, and the node belong to the same channel factory.It is noted that the connection to channel factories is not essential if there is an invalidation scheme that allows for the invalidation of a prior funding transaction. To simplify the process, the proposal suggests using tx formatted messages to transport the intent, reconnecting to the idea of cut-through and combining multiple transactions into one. Although this may complicate state tracking, it is believed that transactions will eventually assume multiple roles.In summary, the proposal suggests an alternative to splice-in/splice-out by implementing a "cut-through" for channel close transactions. This allows for the closing of a channel and opening of another in a single on-chain transaction using the closing transaction cut-through. The proposed reseat operation is useful for reseating a channel from one peer to another, and can be done off-chain if the peers and node belong to the same channel factory.


Updated on: 2023-07-31T19:59:03.911572+00:00