Quote from: DiceBitcoin on September 07, 2014, 06:54:52 PM

We finally found what caused this "issue". We are in a very difficult position here because this indeed has been done deliberately.

4 weeks ago we started interviewing engineers in order to have one join our team (because we had so many features / fixes that we needed to implement). The interviewing process took about 1 week and we settled for one guy with pretty good knowledge of our technology stack.

This "dude" (he used to say all the time) had accomplished to commit code into production that DID SKIP WINNING BETS on specified accounts. When he wanted to "alter" an account he added a field that flagged the account and made it skip winning rolls with maximum skips = 1.

The agreement was that he would get a % cut from our shared profit (commission from investments) that pretty much explains why he could do this.

We currently do not know the extent of the damage that this guy has done to us and only time will tell. We are working really REALLY hard in order to deliver what you are enjoying at Dicebitco.in and what this guy has done to us just makes us wonder why. Well we do not blame this scumbag only, we put most of this on us and we take full responsibility, because we failed to review the code as we supposed to (not relying only on passing tests - as we had no test for this scenario).

We are looking to find all the accounts that have been affected by this (we have found some: Focus, James, marie_lemke, finnile), but in the meantime we are calling all the users that have lost bitcoins to verify their bets and if even only one bet has been skipped we will refund their deposit up to one satoshi. We want to make clear that every refund WILL NOT AFFECT INVESTORS as we decided to pay this from our pocket. Its not THEIR fault, its OUR fault for not reviewing the code. So we pay for it.

And to all those people accusing us: Don't you think if we were scammers, NOW it would be the best time for us to take the bankroll and run? Well the answer is that we are NOT. We worked hard for this and we certainly do not want to end like that. Go into gamblers' logic: You lose. Wouldnt be checking that your rolls are fair be the first thing to do?

One user asked for a screenshot of the code that introduced this. Well here it is: http://imgur.com/bATFWPI

For the time being you can use this verifier: http://rgbkey.github.io/just-dice/ in order to generate a sequence of rolls (just omit the first 2 input boxes)

Again, this affected only few users and only for the last week.

We are going though all bets done now last 1 week, and fixing where appropriate. All support tickets will be answered now.

That piece of code doesn't say much. Must be some IF statement above that is interesting ;-)