From 0c27311f4734bf9611daf7a62e3c603c63ee36c2 Mon Sep 17 00:00:00 2001 From: Jeffrey Czyz Date: Mon, 10 Mar 2025 11:09:39 -0500 Subject: [PATCH] Allow either node to send tx_init_rbf in v2 establishment Splicing allows either node to send `tx_init_rbf` as they may want to take the opportunity to contribute or withdraw additional funds to / from the channel. Allow the same for v2 channel establishment for consistency. --- 02-peer-protocol.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/02-peer-protocol.md b/02-peer-protocol.md index 2057728..20940ca 100644 --- a/02-peer-protocol.md +++ b/02-peer-protocol.md @@ -1407,7 +1407,7 @@ a transaction paying more fees to make the channel confirm faster. #### Requirements The sender of `tx_init_rbf`: - - MUST be the *initiator* + - MAY be the either the *initiator* or the *accepter* - MUST NOT have sent or received a `channel_ready` message. The recipient: @@ -1430,6 +1430,10 @@ a large feerate change, instead sets their `sats` to zero, and decline to participate further in the channel funding: by not contributing, they may obtain incoming liquidity at no cost. +We allow both nodes to initiate RBF, because any one of them may want to take +this opportunity to contribute additional funds to the channel without +waiting for the initial funding transaction to confirm. + ## Channel Quiescence Various fundamental changes, in particular protocol upgrades, are