And now you stopped being provably fair, cause every server seed can be adjusted to the results given in this 5 minutes time.
Other words: no metter the results in this 5 minutes, there always exist a seed which explain them.
Edit:
I was wrong.
You are viewing a single comment's thread from:
@bartosz546 Next ServerHash is publish to the chain when previous ServerSeed reveal. There is no way server Seed can change the other yet still produce same hash via SHA256 . Do you mind elaborate how ServerSeed can change and still manage to hash the same serverHash.
You don't get my point. No matter the result they will provide you in this five minutes they can reveal hash they chose by their own.
Example let's say epicdice makes all games being lost in this five minutes, they can calculate hash which will justify it and then publify it.
Other thing:
Why to even use transaction hash now?
It doesn't make any sense in current implementation, if there is server hash, you could just forget about transaction hash and just reveal server hash once per five minutes.
In my opinion they got lost in their ideas.
@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.