pull down to refresh

We know that a few of you are playing Workit challenges, and we have an important announcement, so please read:
🚨 IMPORTANT ANNOUNCEMENT 🚨
Eight hours ago, an unknown bug was exploited within the app, and the hacker managed to drain one of our wallets, totaling around $800 in Bitcoin.
User funds are safe, and we advise you to transfer them to another wallet until we identify and fix the bug.
The damage was minimal, and the existing challenges will be canceled, with users receiving their funds back.
We are very sorry for the inconvenience. All user funds are safe and unaffected—only Workit suffered a minimal loss of $800 in Bitcoin.
To be extra safe, please transfer your Bitcoin to another wallet. Please wait for our announcement as we resume operations in a few days.
Thanks for the heads up. We so run a club Post and I've shared it there as well. Hopefully it just doesn't deter your plans of launching Android app.
We all wanna know when we'll get Workit on Android?
reply
We are working on it so most likely in spring!
reply
Thanks for letting us know! All sats are safe in one of my wallets. Hope that @grayruby and @Undisciplined are aware.
reply
115 sats \ 1 reply \ @grayruby 25 Feb
Saw that I got my sats back from the challenge we were in but I haven’t withdrawn yet.
reply
Yes, I went for my morning walk and noticed soon after that I had again the sats in the wallet and no active challenge. I have already withdrawn them.
reply
Gotta love Random thieves on the internet this is one thing I hate about the bitcoin ecosystem. Hacks and theft and how it goes unpunished
reply
The good thing is that it happened now and not at a later stage, and we only paid a small price.
reply
Thanks for the heads up! Hopefully your up and going again soon!
reply
Thanks! The problem has been identified, and a fix is being implemented.
reply
Look forward to the next challenge once sorted
reply
Yes, we only need a few days!
reply
I'm having trouble withdrawing
reply
Try withdrawing 90% of your balance first and the remaining in the second transaction using the same logic
reply
Thanks
reply