pull down to refresh

New error "Estimated fees are too high"
242 sats \ 3 replies \ @ek 20 Nov
That is intended and should only show up in your logs but not break zaps.
It means reaching your node is too expensive for that zap so we fall back to credits.
Btw, we found the issue for no wallet to receive available. We'll deploy the fix soon.
reply
50 sats \ 0 replies \ @ek 20 Nov
oh, but we should use WARN and not ERROR for Estimated fees are too high
reply
I have a channel open with SN and the fee is very low, so why would that error happen?
reply
48 sats \ 0 replies \ @ek 20 Nov
Oh, you have a direct channel with SN? Then that's weird, we will also look into that. No network fees from SN to you should apply in that case.
edit: do you have enough inbound liquidity on that channel?
reply