-
Notifications
You must be signed in to change notification settings - Fork 377
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
Unable to send_probe
to eclair due to lack of payment secret
#2525
Comments
Hmm, yea, interesting. The error clearly indicates that we got to the recipient, which means for probing purposes we should treat it as a success, but for payment purposes this error implies we should never try to route through this node again so we should blame the inbound channel (which is what we do). The simple fix is, indeed, just add a random payment secret to get them to respond with unknown_payment again, though we could also move to a different I'm also curious why the node isn't accepting this as a keysend - does eclair not support receiving keysends/spontaneous payments? |
I think they do, this was opened last week: ACINQ/eclair#2724 |
CC @t-bast any chance you can help illuminate here - tony is getting the above error (PERM|invalid_onion_payload) when trying to probe to an eclair node, but it should presumably be treating it as a keysend and simply failing with unknown_payment. |
Hey! Sure, that one is simple enough. By default, But in your case, the |
Oh duh lol, y'all identify keysend by the preimage, not the lack of payment secret. Okay, makes sense, we should probably just fill in a random payment secret. Thanks. |
Because of this issue, eclair requires payment secret when sending probes: ACINQ/eclair#1810 (comment)
Right now I'm getting:
And I think it's because when sending probes, it uses
sponaneous_empty
which does not send payment secret.rust-lightning/lightning/src/ln/outbound_payment.rs
Lines 984 to 993 in 3dffe54
rust-lightning/lightning/src/ln/outbound_payment.rs
Lines 461 to 463 in 3dffe54
Would always sending payment secret be the right approach? Don't all nodes support it at this point? Or would allowing
send_probe
to pass throughRecipientOnionFields
be a work around and I can hardcode their node pubkey for it.The text was updated successfully, but these errors were encountered: