-
Notifications
You must be signed in to change notification settings - Fork 2.2k
lncli: No routehints argument defined for sendpayment & queryroutes #6601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Route hints aren't available via the |
Oh okay, will adding the argument to cmd_payments fix it? If it's the case I can open a PR for that. I'm surprised keysend can't work at all with private channels because of this. AMP won't help my case. |
…tningnetwork#6601) Adds an integration test to verify SendPayment successfully uses invoice route hints for payments involving private channels.
…tningnetwork#6601) Adds an integration test to verify SendPayment successfully uses invoice route hints for payments involving private channels.
…tningnetwork#6601) Adds an integration test to verify SendPayment successfully uses invoice route hints for payments involving private channels.
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend and --amp payments. CLI will error if neither is specified or if --pay_req is specified since bolt 11 already handles route hinting. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend/amp over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend and --amp payments. CLI will error if neither is specified or if --pay_req is specified, however it appears --pay_req codepath is unreachable, left for robustness. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend/amp over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend and --amp payments. CLI will error if neither is specified or if --pay_req is specified, however it appears --pay_req codepath is unreachable, left for robustness. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend/amp over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend and --amp payments. CLI will error if neither is specified or if --pay_req is specified, however it appears --pay_req codepath is unreachable, left for robustness. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend/amp over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend and --amp payments. CLI will error if neither is specified. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend/amp over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend and --amp payments. CLI will error if neither is specified. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend/amp over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
…tningnetwork#6601) Adds --route_hints flag to sendpayment for --keysend payments. Hints should be JSON encoded (see usage for example). Adds --route_hints flag to queryroutes (no restrictions). Adds integration tests for query routes over RPC, and manual keysend over RPC to emulate the new feature. Testing revealed route hinting did not work for standard payment (w/ or w/o --pay_addr).
Background
The issue has arisen when trying to do a keysend payment from an LND node to @hsjoberg 's @BlixtWallet also running LND node. Keysend works when sending payments from Blixt LND to a Desktop LND but not the other way around.
It turns out it was because of the private nature of Blixt channels, sending from Blixt Wallet to Another Blixt Wallet is possible because the QR code contains route hints in a form of JSON that are passed to lnd within Blixt Wallet using
routerrpc.SendPaymentRequest
spec.For some reason I can't get the
--route_hints
argument to work inlncli
so I can do a keysend payment to Blixt from a desktop node, actually, the only place that argument is mentioned to exist within lndcli is the API docI've done some digging in commits history and
--route_hints
should be available both inlncli sendpayment
andlncli queryroutes
but All I get isTried other combinations like
--routehints
but same resultYour environment
lnd 0.14.3-beta
Ubuntu / Win10 pre-built binaries
btcd
,bitcoind
, or other backendneutrino
Steps to reproduce
run
lncli sendpayment --keysend
orlncli queryroutes
with--route_hints
argument.Expected behavior
Actual behaviour
related #3971
The text was updated successfully, but these errors were encountered: