Before the game is recorded in the DB, it the hash is recomputed to make sure everything matches up. If the recomputed hash doesn't match the displayed hash, you get the tampering error. I'm having a hard time imagining how what you've described happened. If you open another tab with a new game, it can mess up the site's guess/salt that is stored in the server-side session, but then refreshing wouldn't have fixed it. Was this a fresh game, or had it sat around for a while? Was it submitted previously and had a different error? Was there anything else you did that might provide a hint?
See my post immediately before yours. I had the error happen 3 times in a row, on 3 different hashes. The first time may have been over an hour old, I'm not sure. But the 2nd and 3rd were newly generated.
I ended up sending BTC to the address it told me, and it worked fine. But that may have been my 4th attempt, which didn't show the error.
Is it possible that my double-clicking the hash at the bottom of the game page then control-c'ing to copy it is causing something bad?
Here's a list of unpaid hashes with the same payout address as the one hash you posted:
521b684fc9e8f31020c35ed15d25e07fe7f0c2881970769b616acab41fdacb6f
135f4c3a60b4d8c8fe5215e48c517cac5652cb47c9022b8e67b058d79761c191
e94182f8f76f6ae7b8351efe45580eb40b9d59c8b6b7efea442aa784e43d1222
Yes, it is safe to pay for the tampered ones. The games look to be fine on the server side. Still, we need to figure out why this is happening.
It might be good to let the user see their list of unpaid games for themselves, and possible let them cancel them. Otherwise they have to wait 2 (?) hours for them to expire if they create too many when playing around. Unless there's a good reason not to, of course.
Can you try a Ctl-F5? We made some changes to the javascript and you might be caching an old copy.
[/quote[
Will do.