Quote from: P-Funk on September 15, 2015, 12:57:31 PM

Quote from: Stars on September 15, 2015, 12:50:02 PM

This issue has already been resolved, I've spoken with Unibtc about it. But I will explain in detail, what happened for all you people wondering.

Magicaldice has been open for just over 2 weeks, so when Unibtc came to our website and managed to profit 54 BTC there was definitely red flags raised and questions that needed answering. The main concern being that Uni knew exactly when to switch from hi to lo and knew exactly when to change his bet from 1 btc to 2 btc. This happened on probably 25-30 separate occasions which A LOT of people pointed out to us, so it wasn't only us thinking there was something strange going on, it was others too.

Regardless, we still had no proof so we paid out all of his winnings. Although yesterday we did ask him to show us who he is, he gave us his ID, bank statements and also added me on FB with the same name on the statement + ID so everything seemed to check out. We also got him to verify some of his accounts that he played on, on other dice websites. We thought if he could prove he plays a lot on other sites, this would also strengthen the idea that he really is a legitimate player and just got lucky. After all of that, we we're pretty confident maybe he did just get lucky.

Let me bring you back a week or so to when we experienced a pretty big bug. Our dev was fixing a few things to do with roll speed and he accidentally fucked up pretty big. He made it so all rolls would produce the same result, and the nonce would stay the same. We fixed this issue fairly quickly and nobody got harmed since we re-set balances to the amount they were at before the issue occurred. Unibtc was online when this happened and that was where he managed to cash out 3 btc due to constantly winning (because roll was the same) and kindly gave them back to us. Now we forgot all about this until yesterday when we started thinking about it some more and we thought what if a user didn't re-set their seeds since then, maybe it's a possibility that it could have messed up future rolls or somehow leaked the server seed without us realizing it. So for that reason, we thought ok.. it still may be possible Unibtc has some sort of exploit. Maybe he knows the server seed and that's how he knows when to switch from hi to low and when to switch from 1 btc to 2 btc bets. So because of that possibility, which I admit probably was very small we decided to change Unibtc's server seed without telling him. The reason for not telling him was because we wanted to see if he'd continue to bet and if he did continue to bet then it proves to us that he probably is a legitimate player and we're just being paranoid. The correct decision was to message Uni and kindly ask him to re-set his seeds though, which is where we fucked up. We acted on impulse without thinking about it, our thought process was, "there's a possibility he's using an exploit? Ok, let's remove that possibility".

Like I said, I've spoken with Unibtc and although he was mad at first he did eventually understand where I was coming from and accepted my apology for not telling him in advance about re-setting his server seed.

But if the server seed was changed, why would it retroactively change the hash on an old bet? And why, if the seed was changed, would the old bet still not have a revealed server seed?

I'm wondering why after changing the server seed it didn't reveal his old server seed on his old bets too. My guess is that since our dev did it manually it didn't update on the bet ID, since it maybe only updates on the bet ID after a player re-sets it. Either way, we made a mistake for sure. I will get that question answered when our dev comes online though.