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
Currently our RPC methods for asset channel invoices/payments require the user to narrow down the tap-channel peer candidates to a single one, as we need a target to initiate the RFQ negotiation with.
This may be confusing for users as they may not be sure which peer should be chosen for a payment.
Solution
We could convert this into a feature by taking advantage of the competition amongst our asset peers in order to find the best quote, and prioritize a payment attempt using that one.
The text was updated successfully, but these errors were encountered:
Can we add multiple quotes to increase payment reliability but still set a priority for the route with the best rate? Do hop hints have a priority that the client is encouraged to honor?
Can we add multiple quotes to increase payment reliability but still set a priority for the route with the best rate
Currently we can't, but we eventually want to. This is what the issue outlines
Do hop hints have a priority that the client is encouraged to honor?
Right now it's just 1 hop hint, which is the tap channel over which the receiver wants to receive (which is currently bound to 1 peer and 1 type of asset).
Description
Currently our RPC methods for asset channel invoices/payments require the user to narrow down the tap-channel peer candidates to a single one, as we need a target to initiate the RFQ negotiation with.
This may be confusing for users as they may not be sure which peer should be chosen for a payment.
Solution
We could convert this into a feature by taking advantage of the competition amongst our asset peers in order to find the best quote, and prioritize a payment attempt using that one.
The text was updated successfully, but these errors were encountered: