[SHUTTING DOWN] [DiceBitco.in | BE THE BANK ! | 1% House Edge]

[Mitchell]

How come they removed the capability to see your seed.Randomize and viewing seeds is now gone from the site.

It works just fine for me:




EDIT:

[1713508596]

1713508596

[1713508596]

1713508596

[galbros]

Wow, while this may not have been intentional, it looks really bad..  I hope dicebitco.in will explain very soon what happened and how they can fix it.  I don't envy them that task.

Dooglus, do you think you could start a dicewatch site and check for stuff like this?

[smalltimer50]

I was sceptical of site when Dooglus offered a position in a multi-sig wallet / verifying the server seeds (something like that, I'm not technically minded) and the site owner DECLINED. Why would he have done that? The site's brand equity would have sky-rocketed! Now you have a site where no one will play... the damage is done, "bug" or not not.



 

[Mitchell]

I was sceptical of site when Dooglus offered a position in a multi-sig wallet / verifying the server seeds (something like that, I'm not technically minded) and the site owner DECLINED. Why would he have done that? The site's brand equity would have sky-rocketed! Now you have a site where no one will play... the damage is done, "bug" or not not.

They declined it because they wanted to stand on their own feet (which is understable in my opinion). However, I wish they had accepted Dooglus offer. It would makes things a lot easier right now.

[itod]

If Dicebitcoi.in thought he can get away from this (rightfully so) paranoid community by skipping some winning bets and go unnoticed he must be an idiot. It's so easy to check if this is the case or not - people with skipped bets please check if those bets would be a winners with skipped nounces. This thing will resolve if it is a scam or not very quickly, today for sure.

[RoooooR]

@bitcoininformation == @manl ?

I need to know. Fuckin cringing.

[Mitchell]

@bitcoininformation == @manl ?

I need to know. Fuckin cringing.

I am not manl and I will do whatever it takes to proof this. My only connection with DiceBitco.in is that I (and Dooglus) both have 5BTC (for a total of 10BTC) in escrow for their signature campaign. That's all.

[marcotheminer]

What a gigantic mess DiceBitco.in have gotten themselves into 

[marcotheminer]

I was sceptical of site when Dooglus offered a position in a multi-sig wallet / verifying the server seeds (something like that, I'm not technically minded) and the site owner DECLINED. Why would he have done that? The site's brand equity would have sky-rocketed! Now you have a site where no one will play... the damage is done, "bug" or not not.

They declined it because they wanted to stand on their own feet (which is understable in my opinion). However, I wish they had accepted Dooglus offer. It would makes things a lot easier right now.

None of this would've happened had they accepted dooglus' offer sheesh

[Mitchell]

None of this would've happened had they accepted dooglus' offer sheesh

Like I said in that very post, I wish they had accepted Dooglus' offer.

[Gws24]

Well, I've checked my own bets at random, especially losing streaks, and found no errors. BUT my last bet was yesterday so it seems to me like this problem/bug/scam only happened today. Anyone found a missing nonce from before today?

[zdaz14]

Well, I've checked my own bets at random, especially losing streaks, and found no errors. BUT my last bet was yesterday so it seems to me like this problem/bug/scam only happened today. Anyone found a missing nonce from before today?

Sure wish my loses were a bug so I can try again haha

[DiceBitcoin]

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.

[RoooooR]

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 .

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)

I lolled.

[zdaz14]

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)

Did this effect only large holding BTC accounts or small as well? How do we verify losses? We use the github link you provided and just paste in the info from bets?

[smalltimer50]

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 .

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)

I lolled.

https://i.imgur.com/SJvuc1Q.png

When was this picture taken? I assume this week? If so, that is very damning and puts a nail the coffin.

[cHoCo]

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.

You are full of S***

[Gws24]

@Dicebitcoin:

- Since when was the malicious code in place? Do you know?
- You say you are going to refund deposits but are you also going to pay the winning bets? For instance if you refund Stars are you going to refund the 2 bitcoin or pay out the 19.8 bitcoin what a win would have netted him?

[GeoRW]

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 ;-)

[shorena]

Last month a prominent question was: how would a new dice site gain trust?

By staying and answering hard questions honestly.