pull down to refresh

I had same thing happen when I zapped you 15 sats now.
I wonder if SN thinks (the code doesn't reconginse) we don't have attached wallets for some reason.
For everything, SN prioritizes using cowboy credits. The one exception is when both the sender AND receiver of a zap have wallets attached.
that's so weird, i have had WoS attached for ages and do get zaps from here regularly, so i know it's working.
and yet i was also sent a CC
but reading the post below, and seeing the fee message, does this just mean that doing little zaps of 10 etc is simply too small an amount?
if so, is there any way we can change it, or will i have to mentally adjust to a new, more terrifying zap threshold?
reply
31 sats \ 0 replies \ @k00b 4 Jan
In your settings, you can control these dust limits for yourself. If the sender wants to send you CCs though, you'll receive CCs regardless of these settings.
reply
117 sats \ 1 reply \ @k00b 4 Jan
Anything in the wallet logs?
reply
135 sats \ 0 replies \ @Wumbo 4 Jan
Yes, That is first place I checked.
Initially there was no log records so I decide to submit my reply above.
But now there is a log record:
[lnAddr] ERROR invalid invoice: Estimated fees are too high (1073 > 330)
My apologies, everything makes sense to me now.
reply