reply on: Route Not Found \ stacker news ~lightning

37 sats \ 6 replies \ @DarthCoin 17h \ parent \ on: Route Not Found lightning

You analyzed the problem a little yourself and noticed that you run out of inbound liquidity on that public channel fast:

There we go...

It's roughly the difference between your current and desired balance.

users must also keep in mind a 1% of the channel at least to leave it for reserves, on both sides not just on your side.

For example:

you have a channel of 1M with only 10k sats inbound space available, you cannot receive more than 9k sats.

But... if you send 9k sats and after that another 100 sats, you can receive, until it fills out that channel.

This is happening due to channel buffer fee https://github.com/lightningnetwork/lnd/blob/6dea86428d031171af30119e3f6599820dc5454a/lnwallet/channel.go#L3803-L3815

0 sats \ 5 replies \ @Undisciplined OP 17h

I know there isn't enough receiving capacity on the public channel with SN, but the private channels have orders of magnitude more receiving capacity than I'm trying to process.

28 sats \ 4 replies \ @DarthCoin 17h

If you cannot include route hints on those private channels you cannot receive into them. Plain and simple. see here #737329

0 sats \ 3 replies \ @Undisciplined OP 17h

This would have to be something that changed then, because I had been receiving through those channels previously.

39 sats \ 2 replies \ @DarthCoin 17h

Is the liquidity and route hints. Do you run the latest version of Alby Hub? Now having a LDK backend, not sure how Alby is updating it too. LDK recently released a new version.

21 sats \ 1 reply \ @Undisciplined OP 17h

I updated a few days ago, because I was having a different issue.

38 sats \ 0 replies \ @DarthCoin 17h

hmmm maybe is time to invite here @alby and @MoritzK to give more clues about how an Alby Hub self hosted with default LDK and private channels is using route hints to build a LN invoice.