routing: require tlv capability for custom record payments
Previously if a payment was sent with custom records attached, path finding wouldn't perform a check whether the final node was capable of receiving custom records in a tlv payload.
This commit is contained in:
parent
c37289cd94
commit
75aa4e7061
@ -97,6 +97,7 @@ func (p *paymentSession) RequestRoute(payment *LightningPayment,
|
|||||||
OutgoingChannelID: payment.OutgoingChannelID,
|
OutgoingChannelID: payment.OutgoingChannelID,
|
||||||
LastHop: payment.LastHop,
|
LastHop: payment.LastHop,
|
||||||
CltvLimit: cltvLimit,
|
CltvLimit: cltvLimit,
|
||||||
|
DestCustomRecords: payment.DestCustomRecords,
|
||||||
}
|
}
|
||||||
|
|
||||||
// We'll also obtain a set of bandwidthHints from the lower layer for
|
// We'll also obtain a set of bandwidthHints from the lower layer for
|
||||||
|
Loading…
Reference in New Issue
Block a user