reply on: Route Not Found \ stacker news ~lightning

pull down to refresh

132 sats \ 10 replies \ @ek 23 Oct \ parent \ on: Route Not Found lightning

Ok, let me summarize your current setup and problem:

You have 3 channels. Two are private and to LSPs recommended by Alby Hub. One is public to SN.

Your problem is that you can't receive payments from SN.

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

I opened a public channel to Stacker News, which has been receiving sats. The problem is that I run out of inbound liquidity on that channel pretty fast.

but this sounds contradictory to this statement:

The receiving capacity on those channels is sufficiently large for anything I've been doing.

So I am confused. Am I right to assume that you attached your Alby Hub node via NWC to SN and see a lot of ERROR autowithdrawal failed: no route found in your logs which is the problem you're trying to solve?

Increasing the max fee might help. Is it at 1%? And how much is it trying to withdraw? It's roughly the difference between your current and desired balance.

37 sats \ 6 replies \ @DarthCoin 23 Oct

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 23 Oct

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 23 Oct

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 23 Oct

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

39 sats \ 2 replies \ @DarthCoin 23 Oct

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 23 Oct

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

38 sats \ 0 replies \ @DarthCoin 23 Oct

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.

0 sats \ 2 replies \ @Undisciplined OP 23 Oct

The channels with lots of receiving capacity are the other two private channels.

On the public channel, I generally haven't had enough receiving capacity for the daily rewards. Then I get the error "no route found". I had tried increasing the default fee (perhaps not enough though). I'd rather just withdraw to another wallet than pay a hundred sat fee.

What's confusing to me is that the two private channels had been receiving transactions and now they aren't.

40 sats \ 1 reply \ @ek 23 Oct

What's confusing to me is that the two private channels had been receiving transactions and now they aren't.

They aren't receiving payments from the same nodes as before?

0 sats \ 0 replies \ @Undisciplined OP 23 Oct

Assuming SN is using the same node as it used to.