routing+rpc: enable senders to set a custom first-hop TLV blob for update_add_htlc
#8618
Closed
3 tasks
Labels
Protocol improvement proposals such as the endorsement bit require the ability for an implementation to set a new TLV value (so far none are used) within the
update_add_htlc
message. We should add such an ability to facilitate such improvement proposals.Today the
LightningPayment
struct houses all payment details requested by the sender, we can set a custom TLV blob for the last hop, but not yet the first hop:lnd/routing/router.go
Lines 2228 to 2329 in b117551
We should add another custom blob here, then ensure that we include it once we go to make the
UpdateAddHTLC
message to send to the first hop:lnd/routing/payment_lifecycle.go
Lines 667 to 696 in b117551
Steps To Completion
Add new field to
LightningPayment
Thread through context to the
paymentLifecycle
struct.Add a slim RPC cut out so we can write an itest in addition to unit tests. The itest can set a custom value for the first hop, then use the
HTLCInterceptor
to ensure that the value was properly set.The text was updated successfully, but these errors were encountered: