pull down to refresh
50 sats \ 4 replies \ @SimpleStacker 15h \ on: Lightning payment probing behavior is implementation dependent lightning
I'm guessing issues with my node is partly what triggered this? Would it make any difference if I receive via a lightning address instead of NWC? Or is the issue independent of that?
It seems like the fact that I have a direct channel is part of what's causing the problem?
The issue is related to the implementation of your Lightning node - method of requesting an invoice and your channels are not relevant.
I deployed a fallback, but it doesn’t work because the first attempt to probe scores the channel as invalid temporarily, then the fallback fails too.
I’ll deploy a workaround tomorrow rather than a fallback and that should get LDK-backed Alby Hub folks back to receiving sats for zaps.
reply
Interesting. Still trying to understand the problem better. I was able to receive my rewards from last night, as well as withdraw sats from my SN account. Does that mean you don't use probing for those payments?
reply
reply
ah, got it
reply