pull down to refresh

0 sats \ 5 replies \ @SimpleStacker 7 Dec 2025 \ parent \ on: Stacker Saloon

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

write
preview
67 sats \ 0 replies \ @k00b 7 Dec 2025

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 2025

Do you know what's backing your node? Is it LDK? Which version?

reply
100 sats \ 1 reply \ @SimpleStacker 7 Dec 2025

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 2025

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 2025

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