You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We introduce a `CommitSigBatch` class to group `commit_sig` messages
when splice transactions are pending. We use this class to ensure that
all the `commit_sig` messages in the batch are sent together to our
peer, without any other messages in-between.
When we receive `commit_sig` messages that contain the `batch` TLV, we
group them directly in the `PeerConnection` before relaying them as a
batch to the channel.
// We haven't received our peer's tx_signatures for the latest funding transaction and asked them to resend it on reconnection.
198
198
// They also resend their corresponding commit_sig, but we have already received it so we should ignore it.
199
199
// Note that the funding transaction may have confirmed while we were offline.
@@ -202,34 +202,29 @@ data class Normal(
202
202
}
203
203
// NB: in all other cases we process the commit_sig normally. We could do a full pattern matching on all splice statuses, but it would force us to handle
204
204
// corner cases like race condition between splice_init and a non-splice commit_sig
205
-
else-> {
206
-
when (val sigs = aggregateSigs(cmd.message)) {
207
-
isList<CommitSig> ->when (val result = commitments.receiveCommit(sigs, channelKeys(), logger)) {
0 commit comments