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.

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

[Feature request] Include route hints for private channels #977

Open
Darth-Coin opened this issue Jan 11, 2025 · 2 comments
Open

[Feature request] Include route hints for private channels #977

Darth-Coin opened this issue Jan 11, 2025 · 2 comments

Comments

@Darth-Coin
Copy link

I would like to propose an important feature for that use private channels.
For which situation?

  • when the Alby Hub user is having multiple private channels
  • when user want to receive a payment to a specific private channel, so will need to add routing hints to his LN invoice, selecting one of his LSP channels.
  • this option to be available for all LN implementations used as funding source for an Alby Hub
@rolznz
Copy link
Contributor

rolznz commented Jan 13, 2025

@Darth-Coin we already include route hints, just choosing which channel to use is not supported.

As long as you do not have any public channels, route hints will be used (for both LDK and LND).

The algorithm at least for LDK is quite complicated in which route hints it will provide.

For choosing specifically which route hints to provide, is it because you would like to do rebalancing?

@Darth-Coin
Copy link
Author

Automated route hints I know there are in place. I wasn't talking about that.
It is about the case when I want a specific payment to get through a specific channel.
Use case:

  • I have 3 private channels: 1 with 90% liquidity, 1 with 50%, 1 with 10%
  • I want to receive the payment only in the one with only 10%, no matter what fees or routes will take.
  • sometimes the payments are taking the fastest and cheapest route, but I want to receive in a specific channel even that on the other channels can fit the payment too.

In this way I can refill emptied channels before are getting stuck and have to close them. yes this shit can happen and I don't know why. If you go lower than 1% in a channel sometimes it stuck. I think is linked to commit fees + reserves + channel buffer and the channel simply became disabled, unusable.
To avoid this is better to keep them filled. So I can even make a circular rebalancing from those with more liquidity to the ones with less, moving the sats to a temporary wallet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants