1. because of the flash or whatever else type of program it uses, after a bit of play, the game significantly slows down (meaning i cant press the bet button quicker if I chose to)
Did you try closing and opening up the browser again to see if it made a difference? We had a leak causing something similar before and maybe it made its way back in the new version of the game. I will try as soon as we get back up.A: Yes. I have to do that all the time. But it always resorts back to getting very slow.
2. After a number of bets rolled, the bet amount keeps increasing gradually. Sometimes I will bet at 0.001 and without my knowledge, it has changed to 0.00167 (which means that from 0.001, it went to 0.00113, 0.001146......... gradual increase)
Was it doing this gradual increase just from betting or did deposits perhaps arrive and got confirmed? It probably happens when there's a mismatch between general balance call responses and the client side balance.A: Yes, it does it from gradual increase just from betting. No deposits were added.
3. granted that the site shows the provably fair hashes for the previous bet rolled but I have way too many times, enough to the point that i have taken notice that, bet a roll at lower than 6618 and the bet outcome, when its a close roll) coincidentally a roll between 6640-6714 (estimated range)
This is just coincidence, an apparent patterns that happen in gambling. We use a proper random generator server side and outcome is also dependent on the "client random" in your browser that can be verified from the js code. Players can also provide their own client rolls if in doubt.Primitive random generators back in the days actually used to have sequences like this. However we're using proper randomisation and also the rand function in your browser on top of that.
