Bastien Teinturier 13d4c9f06c Add support for RBF-ing splice transactions (#2925) ... If the latest splice transaction doesn't confirm, we allow exchanging `tx_init_rbf` and `tx_ack_rbf` to create another splice transaction to replace it. We use the same funding contribution as the previous splice. When 0-conf isn't used, we reject `splice_init` while the previous splice transaction hasn't confirmed. Our peer should either use RBF instead of creating a new splice, or they should wait for our node to receive the block that confirmed the previous transaction. This protects against chains of unconfirmed transactions. When using 0-conf, we reject `tx_init_rbf` and allow creating chains of unconfirmed splice transactions: using RBF with 0-conf can lead to one side stealing funds, which is why we prevent it. If our peer was buying liquidity but tries to cancel the purchase with an RBF attempt, we reject it: this prevents edge cases where the seller may end up adding liquidity to the channel without being paid in return.		2024-10-18 04:44:10 +02:00
..
main	Add support for RBF-ing splice transactions (#2925)	2024-10-18 04:44:10 +02:00
test	Implement on-the-fly funding based on splicing and liquidity ads (#2861)	2024-09-25 13:01:17 +02:00