pull down to refresh

261 sats \ 8 replies \ @SimpleStacker 7 Dec \ on: Stacker Saloon
Hmm, I haven't been able to receive sats for the last 18 hours or so, even though I've been able to send them. My wallet is up and running and connected, afaict.
write
preview
0 sats \ 0 replies \ @k00b 7 Dec
Issue appears to be prepay probes to LDK producing the wrong error message: https://github.com/lightningnetwork/lnd/discussions/10427
reply
0 sats \ 6 replies \ @k00b 7 Dec
weird, does it say anything in your logs? we updated our node to the latest version of lnd last night. I wonder if there's an incompatibility of some kind.
reply
0 sats \ 5 replies \ @SimpleStacker 7 Dec
Hmm, I see what looks like multiple payment retries
which I think might've been for this zap
Maybe i'll try updating my albyhub and reconnecting
reply
67 sats \ 0 replies \ @k00b 7 Dec
It might be an issue with wrapping the invoices. I’ll see if there’s anything I can figure out on my end
reply
0 sats \ 2 replies \ @k00b 7 Dec
Do you know what's backing your node? Is it LDK? Which version?
reply
100 sats \ 1 reply \ @SimpleStacker 7 Dec
I'm using AlbyHub version 1.21.0 which seems to integrate LDK, though I don't know which version of LDK
reply
0 sats \ 0 replies \ @k00b 7 Dec
Thanks. I'll push an update today that falls back to a fee estimation method that doesn't suffer from this problem.
reply
0 sats \ 0 replies \ @k00b 7 Dec
It looks like LND is having some kind of issue using our direct channel when estimating routes when I ask it to probe (to estimate fees) based on an invoice. I'm not sure why, but I'll keep poking at it.
reply