@@ -483,11 +483,13 @@ func testCustomChannels(ctx context.Context, net *NetworkHarness,
483483 // Test case 2: Pay a normal sats invoice from Dave by
484484 // Charlie using an asset,
485485 // making it a direct channel invoice payment with no RFQ SCID present in
486- // the invoice (but an RFQ is used when trying to send the payment). In this
487- // case, Charlie gets to choose if he wants to pay Dave using assets or
488- // sats. In contrast, test case 3.5 we have the opposite scenario where
486+ // the invoice. This case should fail because Charlie can't choose
487+ // to send something that dave is not expecting. More details about this
488+ // scenario are discussed in
489+ // https://github.com/lightninglabs/taproot-assets/issues/1421#issuecomment-2707614141
490+ // In contrast, in test case 3.5 we have the opposite scenario where
489491 // an asset invoice is used and Charlie must pay with assets and not have
490- // a choice (and that case is supposed to fail because Charlie tries to
492+ // a choice (and that case is also supposed to fail because Charlie tries to
491493 // pay with sats instead).
492494 //
493495 // Charlie --[assets]--> Dave
@@ -538,6 +540,8 @@ func testCustomChannels(ctx context.Context, net *NetworkHarness,
538540 // taproot asset from Charlie, that must be honored because Charlie did
539541 // an RFQ with Dave when that invoice was created agreeing that when it
540542 // was paid that Dave would receive taproot asset instead of sats.
543+ // More information about this scenario is discussed in
544+ // https://github.com/lightninglabs/taproot-assets/issues/1430
541545 //
542546 // Charlie --[assets]--> Dave
543547 //
0 commit comments