I see u guys said it is not rigged, I don't think so. How can you guys explain nitrogen sports' provably fair blackjack, too many people complain their blackjack is 100% rigged, when you get 20, dealer gets 21, when you get 19, dealer gets 20 or 21, when you get 18, dealer gets 19,20,21, when you get 17, dealer gets 18,19,20,21, i estimate players have 20% winning rate on their bj, which is highly suspicious, although nitrogen claims it is a provably fair blackjack.
Like I said:
It is important to realize that provably fair only works when you actually verify your bet outcomes.
Some implementations are worse than others too. If you like to understand the basics of provably fair I advise to read my article:
http://dicesites.com/provably-fairIn the case of NS BJ, the implementation is really bad indeed. Like most BJ games TBH, generally dice sites have better provably fair implementations. You have to do this to make sure it's fair:
1) Open provably fair tab
2) Copy "Next Hash" (note: you cannot easily copy this, you must be using browser developer tools to do this)
3) Change client seed (note: they do not generate it in the browser, but they give it in an AJAX request together with serverseed hash, this is bad and you -must- change clientseed every bet because of this)
4) Make the bet
5) Open provably fair tab
6) Compare "Deck Hash" with copied hash
7) Go to external verifier and fill in all details
And you must do this for
every bet.
They can do the following things to improve the implementation:
1. Allow easy copying of "serverseed hash"
2. Generate clientseed in browser after receiving the next serverseed hash
3. External verifier shouldn't include resources from NS
4. Ideally: use nonce-method which allows easier verifying