https://i.ibb.co/YDx0Ytg/rotfl.pngDear Dennis from Nanogames,
If I was making false accusations before, according to you, it is safe to say you're just playing dumb now. If you're that expert at using the verifier (I've probably used it more times than you, and know better than you how it works, and you work here.), show me the proof that game #884,335, for example, had the same hash both in the verifier and on the website.
Oh, let me simplify the work for you. I have fed the verifier with game #1,684,355 hash: 1b955c61cdf11f2462c6c2ed59fdb9ea3bbde2f480d7568e5f879804f07cbe8d. I've verified 800,000 rounds: according to the verifier, 800,000 rounds before the hash was 904e97bcb8586d0c4355ae9b311b54c390b762708210c070e7c71490971d5f2d. (you probably don't even know how to hash 800,000 times without making it crash your browser rotflmao.) The verifier calculated it because all it did was hash the hash I fed it 800,000 times, and that was the result.
Now prove to me that was the actual hash used in the games on the website. Do you say that the website shows all bets? Wrong. All it does is show 200 pages of 20 bets each, that's the latest 4000 bets. It says it can't go beyond page 200 cause it's too high. Now, since the official hash posted by Mrbit is wrong, tell me how we are supposed to verify that the chain wasn't switched (potentially multiple times) hundreds of thousands of bets ago, and that it actually played the hash 904e97bcb8586d0c4355ae9b311b54c390b762708210c070e7c71490971d5f2d on the Nanogames website, using the VERIFIER.
Since you are so expert at using it, apparently, and I'm the dumb one who doesn't know how to use it. Go ahead.
