LND: Payment failures when amount is over dust limit sats, on testnet #9235
Replies: 2 comments 9 replies
-
Sorry, to be clear, at the bottom of the previous message are the full LND logs for both SENDER and RECEIVER |
Beta Was this translation helpful? Give feedback.
9 replies
-
Note, I tried this also with Bolt 11 invoices, and got the same result. So it's not just a Keysend problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a strange scenario, between two testnet nodes. My best guess is that it might be due to the current insanely high fees on Testnet (right now about 4200 sats/vbyte), but I'm really not sure.
Both nodes are running:
lncli version 0.18.3-beta commit=lightning-terminal-v0.13.4-alpha
I recently restarted both bitcoind (running testnet3), and also both instances of LND.
I have a channel between the two nodes.
Let's call the two nodes SENDER and RECEIVER.
Here is what the channel looks like on the SENDER node:
We can see that almost all the balance is on the SENDER side.
Now, let's do a keysend from SENDER to RECEIVER.
A 1 sat keysend works well...
... and a 100 sat keysend also works well...
Also a 200 sat payment works well....
Also a 250 sat payment works well...
... in fact, all payments work well, up until EXACTLY
354 sats
... which is the dust limit!When I send 354 sats or more....
lnd-log-RECEIVER.txt
lnd-log-SENDER.txt
Beta Was this translation helpful? Give feedback.
All reactions