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

[chkgk]

I just copy pasted it but just checked to make sure and there are no spaces or Enters

Maybe someone else can try it to double check?

server seed: 8iALTHbCjKALWRCz4JcS1K1UDftwlNurZBBY0u3Z5g6C2S48J9VMEyeyvKsoN865
client seed: 64363643568560724277224
nonce: 1348

I can confirm that the results differ between the jsfiddle version and the rgbkey github checker for the values you provided.
I too get 14.35 vs. 72.7356.

[1715002185]

1715002185

[1715002185]

1715002185

[1715002185]

1715002185

[1715002185]

1715002185

[1715002185]

1715002185

[DiceBitcoin]

I just copy pasted it but just checked to make sure and there are no spaces or Enters

Maybe someone else can try it to double check?

server seed: 8iALTHbCjKALWRCz4JcS1K1UDftwlNurZBBY0u3Z5g6C2S48J9VMEyeyvKsoN865
client seed: 64363643568560724277224
nonce: 1348

PrimeDice uses different verifier than DB! That is why you get different rolls. The link you are using( jsfiddle version) is to verify PD rolls, not DB. different algorithm.

We are still investigating and we will update you shortly.

[dooglus]

Dooglus, your modified verifier gives different results then rgbkey's version:

You're right. My modified version is for PrimeDice I think. It would need to be changed a little to work with DB.

I think rgbkey's Just-Dice verifier should work for verifying DB rolls though, and can verify many at once:

http://rgbkey.github.io/just-dice/

Sorry for the additional confusion!

[chkgk]

[...]
I think rgbkey's Just-Dice verifier should work for verifying DB rolls though, and can verify many at once:

http://rgbkey.github.io/just-dice/

Sorry for the additional confusion!

It works. Thanks!

[omahapoker]

if it was cheating and was so easy to point it out. does that make sense?



you make a site and it genrates millions of dollars in rev in 3 weeks. cheating would not be the smartest business move

[snarlpill]

if it was cheating and was so easy to point it out. does that make sense?



you make a site and it genrates millions of dollars in rev in 3 weeks. cheating would not be the smartest business move

Refer to my previous posts about how easy it would be for them to scam with server seeds. To scam on verifiable rolls would be stupid. Which is why I don't believe the "bug" with the rolls was intentional.     ....at least not at the moment.

[a1choi]

if it was cheating and was so easy to point it out. does that make sense?
you make a site and it genrates millions of dollars in rev in 3 weeks. cheating would not be the smartest business move

i don't think thats a good argument against them cheating.  just because its not a smart business move doenst mean it couldn't have happened.  people make non-smart biz decisions all the time.

edit: i'm not saying they are, but the evidence does speak for itself.  skipped losing rolls is damning enough.. plus so far only on one account.  we'll see soon enough.

[finnile]

I am still writing my post.
But I think it was deliberate, and something went wrong, which made it happen much more often than intended.

[Gws24]

Dooglus, your modified verifier gives different results then rgbkey's version:

You're right. My modified version is for PrimeDice I think. It would need to be changed a little to work with DB.

I think rgbkey's Just-Dice verifier should work for verifying DB rolls though, and can verify many at once:

http://rgbkey.github.io/just-dice/

Sorry for the additional confusion!

That one works and gives the same result as rgbkey's one. So far all the bets I checked matched the outcome on dicebitco so for me at least it seems as everything is in order.

[a1choi]

Dooglus, your modified verifier gives different results then rgbkey's version:

You're right. My modified version is for PrimeDice I think. It would need to be changed a little to work with DB.

I think rgbkey's Just-Dice verifier should work for verifying DB rolls though, and can verify many at once:

http://rgbkey.github.io/just-dice/

Sorry for the additional confusion!

That one works and gives the same result as rgbkey's one. So far all the bets I checked matched the outcome on dicebitco so for me at least it seems as everything is in order.

now we just need everyone else to verify their own bets as well.  Manl has said no other bets have been affected and that it was just Finnile's but everyone should check anyways.

[snarlpill]

The ones I checked against RGBKey Verifier were good.

EDIT- Still waiting to hear Doog's final personal opinion on whether he thinks the "bug" was intentional or not. I'm sure he is measuring twice and cutting once as they say, treading carefully because there is a lot at stake here.

[finnile]

Well, the whole thing happened with me. And I am sorry if I am not posting this from my original account.

So, I lost over 1.8 BTC on the DB Site at first.
It started with a losing streak of more than 70-80 @ 10%.
And then a Martingale Loss streak of 17. Followed by 1 win, and another losing streak of around 22.
I busted most of my roll there.
Initially I ignored it considering it a bad luck.
But then I started betting again.. and too my surprise, if I clicked Hi, rolls were low. And If I clicked Lo, rolls were Hi.
It wasn;t random, and I was getting Pretty bad losing streaks.  I also had a losing streak of around 25-26.

Almost after every 10 seconds, I was getting a losing streak of 10. and it was crazy. Instead of chasing my losses, I tested my bets with 100 stas bets and it felt Too much rigged than just bad luck. I ran Extremely Bad for 50 minutes. I was losing 80% of the time, and clearly wasn't just a Bad luck.
I recorded my entire session.

Once I was completely convinced, I went over to PRC and commented about this. People just thought it was a  bad run or streak .
Then to prove it to them. I asked them(Bazza and a1choi) to pick Hi or Lo .
And I did 10 rolls.

And that was when these happened:
https://i.imgur.com/qPosVOC.png
https://i.imgur.com/Jjizyvx.png
and the other links doog posted above.

One of them even suggested to try Alternate Hi  or Lo.
And it made no difference :

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

I was simply losing 80-90% of my rolls.

I was pretty much convinced they were rigged. I gave my seeds to Bazza, and a small video :
https://www.youtube.com/watch?v=QmwSP1lBuGY

Bazza , verified the rolls, and brought to everyone's attention. That indeed, it was clearly rigged.

For all those new to the provably fair thing:
So whenever a roll is generated it requires 2 things:
Client seed(provided by you)
and Server seed(a Secret alphanumeric by the site)

They are combined, to produce the rolls.
Everyone is free to verify their rolls on the RGBKEY Site(which you should definitely do) .

 I did verify my rolls on the sites, And Indeed they were correct. BUT I could never see the rolls not shown. I never checked if the nonces were consecutive and hence I never figured it out, until Bazza Pointed it out.
It was clear, they were skipping the winning rolls and just showing the losing one's and this was the smart part about the scam.

I am not sure how many were effected by the bug, but the only way to check that was to go to the My Bets Tab:
and Click on 2 consecutive bets(or rolls) and check if the nonces are consecutive as well. and then verify the bets.

manl the site owner might say this was not deliberate and happened because of a bug, but the main point is that only the winning bets were skipped. I think there was a Bug and a BUG in the scam which made it happen for the entire 2-3 hours for me.

The fact that it happened only on the winning rolls , and only the winning rolls were skipped clearly means it was intended that way and cannot just be a mistake. It might have happened with more users before, who might have not checked if the nonces were consecutive.  
I don't personally care what manl has to say about this, But simply because of only winning bets being skipped, the intentions were pretty obvious and questions the integrity  of the site which has over 7.5K BTC ( ~ 3.5 Million USD invested )

The site's profits also skyrocketed and were 200 BTC just this week. Even though it might be less than expected but this sudden jump is also questionable(I am not saying it certainly is) .

At the end Manl, has refunded me my loss plus a 0.2 BTC compensation. Again, everyone is free to think what they want to.








 

[Stars]

I have been effected by this bug it seems, I will edit this post and post screenshots of each bet.
41235147   0.00000000   9.9000   ↓10.0000   43.7669   -0.00000000
40303808   4.00000000   9.9000   ↓10.0000   16.9612   -4.00000000
40298916   4.00000000   10.0000   ↓9.9000   27.6732   -4.00000000
40296805   2.00000000   10.0000   ↓9.9000   34.8482   -2.00000000
40296789   2.00000000   10.0000   ↓9.9000   28.5250   -2.00000000
40296778   2.00000000   10.0000   ↓9.9000   79.2242   -2.00000000
40161327   4.00000000   9.9000   ↓10.0000   84.6455   -4.00000000
40156138   3.00000000   9.9000   ↓10.0000   33.7365   -3.00000000
40156117   4.00000000   9.9000   ↓10.0000   48.8824   -4.00000000
40156079   2.00000000   9.9000   ↓10.0000   18.7159   -2.00000000
40155389   1.00000000   9.9000   ↓10.0000   75.4344   -1.00000000
40143735   1.00000000   9.9000   ↓10.0000   74.9338   -1.00000000
40143701   2.00000000   9.9000   ↓10.0000   74.6017   -2.00000000
40143529   2.00000000   9.9000   ↓10.0000   37.0200   -2.00000000
40126175   0.50000000   9.9000   ↓10.0000   11.8696   -0.50000000
40126167   0.50000000   9.9000   ↓10.0000   45.0481   -0.50000000
40125973   0.50000000   9.9000   ↓10.0000   56.0960   -0.50000000
40125956   0.50000000   9.9000   ↓10.0000   72.2778   -0.50000000
40125878   0.50000000   9.9000   ↓10.0000   29.6848   -0.50000000
40125765   0.50000000   9.9000   ↓10.0000   10.4268   -0.50000000
40114869   0.20000000   9.9000   ↓10.0000   20.2174   -0.20000000
40114862   0.20000000   9.9000   ↓10.0000   98.2097   -0.20000000
40114855   0.20000000   9.9000   ↓10.0000   66.6403   -0.20000000
40114847   0.20000000   9.9000   ↓10.0000   32.7034   -0.20000000
40114840   0.20000000   9.9000   ↓10.0000   17.8090   -0.20000000
40114830   0.20000000   9.9000   ↓10.0000   11.5631   -0.20000000
40114821   0.20000000   9.9000   ↓10.0000   63.8103   -0.20000000
40114778   0.20000000   9.9000   ↓10.0000   20.1408   -0.20000000
40114754   0.20000000   9.9000   ↓10.0000   54.8034   -0.20000000
40114706   0.10000000   9.9000   ↓10.0000   25.7128   -0.10000000
40114590   0.10000000   9.9000   ↓10.0000   87.5895   -0.10000000
40090065   0.00000000   9.9000   ↓10.0000   54.7736   -0.00000000
40074510   0.00000000   9.9000   ↓10.0000   81.8926   -0.00000000
40069425   0.00000000   9.9000   ↓10.0000   66.0740   -0.00000000
40069157   0.00000000   9.9000   ↓10.0000   56.4644   -0.00000000
40068066   0.00000000   9.9000   ↓10.0000   36.8424   -0.00000000
40064545   0.00000000   9.9000   ↓10.0000   40.8721   -0.00000000
40059935   0.00000000   9.9000   ↓10.0000   44.9864   -0.00000000
40035706   0.00000000   9.9000   ↓10.0000   24.8266   -0.00000000
40032985   0.00000000   9.9000   ↓10.0000   86.7231   -0.00000000
40002267   0.00000000   9.9000   ↓10.0000   38.1810   -0.00000000
39935128   1.00000000   9.9000   ↓10.0000   3.7214   +8.90000000
39934966   2.00000000   9.9000   ↓10.0000   92.6851   -2.00000000
39926750   2.00000000   9.9000   ↓10.0000   42.7513   -2.00000000
39919663   2.00000000   9.9000   ↓10.0000   80.8242   -2.00000000
I need to post the server seed and server hash ID also correct?
EDIT: Screenshot of showing the bets so you can see I haven't skipped it myself. - http://gyazo.com/d60ad7e6c70476dd9513ea1d71bb02bd
Screenshot of nonce : 47 - http://gyazo.com/f82d0eefd74149f1c397db42f0f12c94
Screenshot of the bet below none : 45 - http://gyazo.com/276b9d666663712612ba361b96e3a2f7

[a1choi]

I have been effected by this bug it seems, I will edit this post and post screenshots of each bet.

Hi Stars,

We have a user in the DB chatbox named Kirk that is analyzing all bets for consecutive nonce issues.  Maybe you can pop into chat and provide your range of Bet IDs for him to scan.

[21pilot]

The fact that it happened only on the winning rolls , and only the winning rolls were skipped clearly means it was intended that way and cannot just be a mistake

this +1

this is simply way too suspicious and it´s really sad to see what greed makes of human beings.
manl and gerry were in a really great position to have a solid long-term income (and a huge one) with
dicebitco.in becoming that popular...
i´m sure they even surpassed primedice in terms of wagered volume.

And now they ruin their entire business because being too greedy.

and nevertheless site profit currently is at an all-time high of 284 BTC  
(though investment amount is down over 1000 BTC from peak)

if anyone is interested in a scientific paper regarding greed I can highly recommend this paper:
http://www.ncbi.nlm.nih.gov/pubmed/12872783

[twister]

someone tell me how to check rolls?

[randayh]

I thought something was odd when I lost 34times in a row on 50/50 odds..

I want my 0.2356 back

[twister]

I thought something was odd when I lost 34times in a row on 50/50 odds..

I want my 0.2356 back

Wow 34 times loss on 2x, one would never see a 34 times win in a row on 2x. 

[coingamblingreviews]

DiceBitco.in nearly reaches the 7,000 BTC bankroll level! Amazing watching the real time numbers of this site at the top of the page.

It really puts into perspective how amazing Bitcoin Gambling is compared to normal fiat gambling, and how successful the Bankroll model is for a Gambling business - good to see you guys killing it

[a1choi]

I thought something was odd when I lost 34times in a row on 50/50 odds..

I want my 0.2356 back

Wow 34 times loss on 2x, one would never see a 34 times win in a row on 2x.  

thats more than what JD has seen and JD had WAY More bet volume that DB...

More information is needed about your 34 streak loss. bet ID, etc