pull down to refresh

Hey @k00b or @ek, I'm getting an error "no wallet to receive available" whenever I try to zap someone.

I just posted the same thing. I think it is ok for people with non custodial wallets. I was able to zap your post.

reply

Darth-I-told-you-so.jpeg incoming

reply

I can zap you

reply

you should be able to zap anyone, this error is not intended

reply

New error "Estimated fees are too high"

reply

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

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

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

I can't zap you

reply

I'm still getting the same error with you and @gnilma.

reply

Should be good now - just rolled out.

reply

Working.

reply

Yep, thanks

reply