Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Pay invoice via a specific route if chan_id is specified #197

Open
peartobear opened this issue Apr 8, 2020 · 2 comments
Open

Pay invoice via a specific route if chan_id is specified #197

peartobear opened this issue Apr 8, 2020 · 2 comments
Assignees
@michael1011
Labels
enhancement New feature or request P2

Comments

@peartobear
Copy link
Contributor

peartobear commented Apr 8, 2020 •
edited
Loading

Letting Boltz construct a route via a specified channel when the channel id is specified would allow for creation of more custom channel opening and normal submarine swaps.
@michael1011 michael1011 self-assigned this Apr 8, 2020
@michael1011 michael1011 added the enhancement New feature or request label Apr 8, 2020
@armurbalda armurbalda reopened this Apr 28, 2023
@armurbalda armurbalda changed the title Boltz Backend should pay invoice via a specific route if chan_id is specified Pay invoice via a specific route if chan_id is specified Apr 28, 2023
@armurbalda armurbalda added the P2 label May 26, 2023
@kilrau
Copy link
Member

kilrau commented Sep 21, 2023

To be clear: this is needed for swap INs to come in/rebalance a specific channel

@kilrau
Copy link
Member

kilrau commented Dec 21, 2023

Idea just came up to also let users specify the "to be rebalenced" channel via routing hints in the invoice (even if the channels in the hints are public). With these hints it should be much easier and faster for us to construct the route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michael1011 michael1011

Labels
enhancement New feature or request P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@michael1011 @armurbalda @kilrau @peartobear