File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -3103,9 +3103,9 @@ fn test_blocked_chan_preimage_release() {
3103
3103
}
3104
3104
3105
3105
fn do_test_inverted_mon_completion_order ( with_latest_manager : bool , complete_bc_commitment_dance : bool ) {
3106
- // When we forward a payment and receive an `update_fulfill_htlc` message from the downstream
3107
- // channel, we immediately claim the HTLC on the upstream channel, before even doing a
3108
- // `commitment_signed` dance on the downstream channel. This implies that our
3106
+ // When we forward a payment and receive `update_fulfill_htlc`+`commitment_signed` messages
3107
+ // from the downstream channel, we immediately claim the HTLC on the upstream channel, before
3108
+ // even doing a `commitment_signed` dance on the downstream channel. This implies that our
3109
3109
// `ChannelMonitorUpdate`s are generated in the right order - first we ensure we'll get our
3110
3110
// money, then we write the update that resolves the downstream node claiming their money. This
3111
3111
// is safe as long as `ChannelMonitorUpdate`s complete in the order in which they are
You can’t perform that action at this time.
0 commit comments