pull down to refresh
100 sats \ 7 replies \ @SimpleStacker 3 Apr \ on: Bitcoin Dev mailing list deplatformed from Google Groups bitcoin
@k00b @ek
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.
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
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.