Small payments not going through on mainnet #2718
Comments
|
It seems that indeed most candidates were excluded due to not meeting the I see two course of actions here:
On LDK Node I so far also had put off overriding the default value as the interface doesn't really lend itself nicely to be overridden (e.g., the To me, a combination of 1) and 2) would make the most sense. |
|
We're going to go ahead and remove the fee here: MutinyWallet/mutiny-node#834 I don't know why it's happening all of a sudden and why no payment attempt is even tried. I had this issue on one existing wallet, then created a new one and it didn't have the issue. Then the next day the new wallet was running into it and we're getting user reports that no payments are going out. I'm seeing this up to 10k sats which I believe is ridiculous and I'm kind of surprised it's hitting fee limits. Perhaps there's a bug with the implementation of max fees. |
|
Removing the fee limits did not work. I still cannot send payments under 20k sats. Here is a series of payments I attempt from 21 sats to 50k sats. |
|
Sorry for the delay, the issue you're hitting is this: So LDK wasn't able to use either of its two outbound channels and promptly couldn't find a route. That htlc minimum is the |
Yes, very likely the general issue is not the maximum fee limit, but the This is likely due to the recent fee spike rendering your small payments dust. There is sadly not much to do about that, besides adjusting the dust exposure limit, as Matt just mentioned. |
|
We set out dust exposure limit to |
|
If I change it to Looks like it is being cast as a |
FWIW, I just replicated this behavior in LDK Node tests. |
|
made #2722 which should fix those potential overflows / undefined behavior |
|
Thanks for the help here. By implementing a large value here we've been able to send smaller amounts again. Feel free to close this unless you want to use it as a tracker for #2722 |
Last time this happened it was due to high mempool congestion, is that's what is going on here again? Hard to tell by the logs. Tested with a 100 sat payment in these logs. I immediately testing 50k sats after and it went through no problem.
I pulled out the last line that prints out the channel info in a human readable format. Perhaps something is going on here?
The text was updated successfully, but these errors were encountered: