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
Unexpected behavior: json_sendpay() can pick the wrong channel despite you specifying a particular local channel for firsthop. You expect json_sendpay() to be the low-level function that does exactly what you ask of it.
Currently send_payment_core() is used by both json_sendpay() RPC and also onion forwards where it uses the function find_channel_for_htlc_add() for non-strict forwarding as required by BOLT 4.
Christian Decker approved a plan where we pass a new boolean flag named strict_first to differentiate firsthop from onion forwarding.
Version: pre-0.12 da0b651
Unexpected behavior: json_sendpay() can pick the wrong channel despite you specifying a particular local channel for firsthop. You expect json_sendpay() to be the low-level function that does exactly what you ask of it.
Currently send_payment_core() is used by both json_sendpay() RPC and also onion forwards where it uses the function find_channel_for_htlc_add() for non-strict forwarding as required by BOLT 4.
Christian Decker approved a plan where we pass a new boolean flag named strict_first to differentiate firsthop from onion forwarding.
nepet@e49f647
Draft patch v0 Feedback welcome!
Please confirm this logic:
The text was updated successfully, but these errors were encountered: