pull down to refresh

If you zapped a custom amount (= long press) and wondered why it didn't send sats:
We're currently missing a flag in that case. We fixed it yesterday for default zaps but missed it for custom zaps.
@k00b will deploy the fix when he is online.
Thanks to @rblb for the fix!
Also, wen ek get deploy privileges lol
reply
Other than checking my connected wallet every time I zap, how can I tell if I sent sats or CCs? Is there a notification I likely have turned off?
reply
you can click on ... next to an item and then click on details
we will probably also show it in satistics soon
reply
So now's a good time to post my offer undercutting you?
reply
LOL I should get a tax for this meme šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚šŸ˜‚
reply
David Lynch:
reply
Memes are public domain and shall stay that way!
reply
reply
reply
This explains a lot as i do a lot of custom zaps. i just did 3 custom zaps , one worked and sent sats from wallet others sent CC
reply
Thanks. I noticed this. Long-press custom zap sent CCs... default zap used wallet.
reply
0 sats \ 0 replies \ @k00b 5 Jan
done
reply
That's odd. I have only been custom zapping and always sent sats.
My only issue is related to coinos and zaps under 30 sats sent or received turning into cowboy credits.
reply
I'm getting something similar, although not always. sending darth 12 sats from coinos works for example so maybe some of it is to do with how other people have their receiving wallet set up
reply
Cool! Is this the bug I reported?
reply
51 sats \ 3 replies \ @ek OP 5 Jan
very likely
reply
What about random zaps? I think I should've sent sats just now instead of CCs.
reply
random zaps are not affected by this bug
reply
Just testing! Did you receive any CCs or sats?
@ek edit: CCs were sent instead of sats nwc
reply
You guys are on it
reply