pull down to refresh

I zapped 2,370 CCs to this post, which I think might be a bug of some kind. I did try to zap 30 sats to it, and you can see that it failed and retried multiple times until finally succeeding. But somehow it also made me spend 2,370 CCs (my entire CC balance) on it.
I'm pretty sure it's not user error, because zapping that much would have required me to long-press and enter 2,370 into the field, which I'm 100% sure I didn't do.
100 sats \ 5 replies \ @k00b 22h
Leading hypothesis is that saunter's attached wallet times out slowly, and because we have network error retry logic on the client, we retry as it times out, then those retries time out, which triggers the retry again, and so on.
I've disabled the retry logic on the client for anything that costs money. We are currently trying to reproduce to confirm this is the exact issue.
reply
0 sats \ 4 replies \ @k00b 22h
I'll refund all zappers on this item. Looks like saunter's wallet triggered the bug perfectly well for nearly everyone that zapped it. Me most of all.
reply
I think you refunded me more than what was lost. I got a 9,000 refund but only lost 2,370 to this bug.
reply
30 sats \ 1 reply \ @k00b 17h
Consider it a bonus for alerting us + extra for pain and distress. :)
reply
Like I said, u lawful bro
reply
0 sats \ 0 replies \ @ek 22h
It hit you the most because you had the most CCs I guess
reply
0 sats \ 0 replies \ @k00b 3 Apr
This bug affected me too. Looking into it.
reply