-
Notifications
You must be signed in to change notification settings - Fork 922
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
Peculiarities w/re paying down zeroconf channels w/ pay
and getroute
+sendpay
#5803
Comments
pay
down zeroconf channel when there's existing channelpay
and getroute
+sendpay
See #5846 for a resolution to the |
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Feb 2, 2023
Modifications from issue ElementsProject#5803 to work here: 1. import json 2. Add xfail 3. Increase channel sizes by 10x so we can open them 4. Fix plugin path Signed-off-by: Rusty Russell <[email protected]>
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Feb 2, 2023
If we only specify the node_id, we get the "first" channel. Closes: ElementsProject#5803 Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: Plugins: `pay` uses the correct local channel for payments when there are multiple available (not just always the first!)
rustyrussell
pushed a commit
to rustyrussell/lightning
that referenced
this issue
Feb 2, 2023
Modifications from issue ElementsProject#5803 to work here: 1. import json 2. Add xfail 3. Increase channel sizes by 10x so we can open them 4. Fix plugin path Signed-off-by: Rusty Russell <[email protected]>
rustyrussell
added a commit
to rustyrussell/lightning
that referenced
this issue
Feb 2, 2023
If we only specify the node_id, we get the "first" channel. Closes: ElementsProject#5803 Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: Plugins: `pay` uses the correct local channel for payments when there are multiple available (not just always the first!)
rustyrussell
pushed a commit
that referenced
this issue
Feb 2, 2023
Modifications from issue #5803 to work here: 1. import json 2. Add xfail 3. Increase channel sizes by 10x so we can open them 4. Fix plugin path Signed-off-by: Rusty Russell <[email protected]>
ddustin
pushed a commit
to ddustin/lightning
that referenced
this issue
Apr 11, 2023
Modifications from issue ElementsProject#5803 to work here: 1. import json 2. Add xfail 3. Increase channel sizes by 10x so we can open them 4. Fix plugin path Signed-off-by: Rusty Russell <[email protected]>
ddustin
pushed a commit
to ddustin/lightning
that referenced
this issue
Apr 11, 2023
If we only specify the node_id, we get the "first" channel. Closes: ElementsProject#5803 Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: Plugins: `pay` uses the correct local channel for payments when there are multiple available (not just always the first!)
gkrizek
pushed a commit
to voltagecloud/lightning
that referenced
this issue
Apr 26, 2023
Modifications from issue ElementsProject#5803 to work here: 1. import json 2. Add xfail 3. Increase channel sizes by 10x so we can open them 4. Fix plugin path Signed-off-by: Rusty Russell <[email protected]>
gkrizek
pushed a commit
to voltagecloud/lightning
that referenced
this issue
Apr 26, 2023
If we only specify the node_id, we get the "first" channel. Closes: ElementsProject#5803 Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: Plugins: `pay` uses the correct local channel for payments when there are multiple available (not just always the first!)
ddustin
pushed a commit
to ddustin/lightning
that referenced
this issue
May 12, 2023
Modifications from issue ElementsProject#5803 to work here: 1. import json 2. Add xfail 3. Increase channel sizes by 10x so we can open them 4. Fix plugin path Signed-off-by: Rusty Russell <[email protected]>
ddustin
pushed a commit
to ddustin/lightning
that referenced
this issue
May 12, 2023
If we only specify the node_id, we get the "first" channel. Closes: ElementsProject#5803 Signed-off-by: Rusty Russell <[email protected]> Changelog-Fixed: Plugins: `pay` uses the correct local channel for payments when there are multiple available (not just always the first!)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(This is for
v22.11.1
) Payments via zeroconf channels are broken in quite a peculiar way, in order to track down the issue I've made a parameterizedpytest
reproducer that is parameterized by:open_existing_normal_channel
(zeroconf_only
oradd_existing_normal
): Whether or not we open a normal (non-zeroconf and confirmed) channel between the payer and the receiver before trying to open zeroconf channels.confirm_zeroconf_channel
(no_confirm_zeroconf
oryes_confirm_zeroconf
): Whether or not to confirm the zeroconf channel by generating a block (this is obviously not useful for zeroconf payments in general, but its failure indicates something odd aboutpay
)payment_method
(pay
orgetroute_sendpay
): Whether to usepay
to make the zeroconf payment orgetroute
+sendpay
Here are the test results from my machine:
These results would seem to indicate that:
pay
is unable to make any payments down a zeroconf channel if there exists an existing normal channel, even if we mine a block to confirm the zeroconf channel and give it a real (non-aliased) SCID.getroute
+sendpay
Is only able to make a payment down a zeroconf channel if there's a confirmation for the zeroconf channel. I speculate that this is becausesendpay
does NOT know how to handle SCID aliases but DOES know how to handle real (non-aliased) SCID (getroute
rightly returns a SCID alias if the zeroconf channel has never been confirmed).The text was updated successfully, but these errors were encountered: