@JackpotRacer:
A lot of people bet thousands of bets with the same serverseed. In theory you can keep betting with millions of bets. So the range can be much bigger than 30 bets. However....
If you made a million bets.. what would you really verify? You can calculate all million bet outcomes, but did you keep record of all million bets (and the amount u bet etc)? Probably not, so you would probably just check the latest bets. Therefor in theory it is better to verify every xx bets, where xx is the number of bets on the "My bets" tab. In reality, like I said, most just verify after losing some, which isn't ideal but okay - at least they can know if they were cheated when losing those bets.
any answer why it is not a general model that is used in provably fair casinos?
They should implement the nonce-system imo
RHavar have said a few times that the "per roll method" could be great if there is an "automated script that verifies each outcome after each bet" and I could agree, but in reality it doesn't really exist at the moment.
(I guess "Seuntjies DiceBot" has some verifying option, but -personally- I prefer to not run .exe files and the source code is too big for me to easily check. )
I don't trust most of the dice sites in Bitcoin business. Right now I only prefer to play at Fortunejack. Other than that we all know what happens in other dice sites, crook owners change codes and you can never win anything from them. Don't play at other dice sites.
We are talking about provably fair here. The implementation of FJ is "per roll" which isn't ideal to verify IMO. They do at least generate a random clientseed in the browser, not like my earlier NitrogenSports example. So FJ's implementation for dice (didn't check other games) looks okay enough. Still I do think others have better implementations.