Since everybody else here considers "newbies" inherently cheaters and Stake can never be in the wrong
.
~
3.2 seconds is enough time to stop a bot and place a bet.
Bugs can happen, but it requires proof or the player should be able to reproduce the bug.
Even if OP can reproduce the bug, there's still the question of evidence.
I was thinking of using epoch time to build that evidence. But unfortunately, it couldn't be.
All the other bets in OP's JSON file have a difference of around 1.3 seconds, except for the bet in question(which has 3.2 seconds).
I would suggest OP to record their bets as they happen in the future. Use a screen recorder.
I didn't realize until now that autobet settings are not provably fair, but then again, the same applies to clicking a high/low button.
Combine this with the fact that a casino knows your next roll(stake knows all three things: nonce+operator unhashed seed+client seed when you use their autobet feature).
If you believe that OP is telling the truth then there's a good chance of something like this happening:Since Stake can predict the winning bet beforehand, they could have very well slowed down OP's winning roll(there's a delay of 1.9 seconds in this case), and manipulated their auto-bet setting.
They don't provide any recorded history of autobet setting in their json data either.A website knows whether a user is on mobile or not, and through javascript can also determine whether the website's window is active or not.
If the user is on mobile and the website's window isn't active then it means the user isn't recording the rolls of the auto-bet, Stake can manipulate the autobet scot-free. Even if they get caught, they will refund the user and call it a bug. A customer with evidence will be compensated and he won't bother fighting over whether it was a bug or not. A customer with no evidence(like in this case) can do nothing.
Stake can turn off the auto-bet abruptly, right before the winning roll. In this case, the bettor can blame no one and will be left complaining even with evidence.
This scheme can be implemented on a large scale to farm additional profit alongside house edge.
This is a hypothesis, not an accusation.Or maybe it was just a bug.
Or maybe OP is lying.We will never know the real truth
It's
lost in time like tears in rainSuggestion to OP: Never ever use a site's own autobet feature. Always build your own script, and randomize client seed on each roll.