pull down to refresh
162 sats \ 15 replies \ @Undisciplined OP 23 Oct \ parent \ on: Route Not Found lightning
It's only my inbound liquidity on the channel with SN that runs out. There's plenty on the private channels, which I had set up previously and which used to receive payments from SN.
Oh, mhh. Is it possible that you withdrew as much as the channel is big, so all liquidity is on your side now in that public channel?
reply
Not according to the information Alby provides. The receiving capacity on those channels is sufficiently large for anything I've been doing.
Edit: Yes, that's exactly the situation wrt the public channel. I'm wondering why payments aren't going to the channels with receiving capacity.
reply
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.
reply
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
reply
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.
reply
If you cannot include route hints on those private channels you cannot receive into them.
Plain and simple.
see here #737329
reply
This would have to be something that changed then, because I had been receiving through those channels previously.
reply
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.
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.
reply
reply
Assuming SN is using the same node as it used to.
reply
reply
That's certainly something I was wondering. SimpleStacker mentioned needing to raise his max fee to 100 for some transactions to go through.
reply