@bartosz546 , you don’t get my point. Current ServerHash is publish to chain prior any bet taking place and each of return result transaction will has the server hash written in memo. At the end of 5minutes interval, the current serverSeed and next serverHash will be reveal. If Epicdice change the ServerSeed, the hashing will not match to serverHash that publish 5 minutes earlier. All the verification can done via
https://geraintluff.github.io/sha256/
And
https://playcode.io/450370?tabs=script.js,preview,console
Why to even use transaction hash now?
A: transactionId being use as nuance, otherwise all result in the 5 minutes interval will be all same.
You are right and I was wrong :)
I forgot about hashed server seed being published.
The small nuance I see at that moment: if you can duplicate transaction hash you might break the system again.
Don't know how complex it could be.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit