pull down to refresh
Well, that doesn't really help much, right? You just give me a hash of 16+salt and then I can confirm that I indeed got 16.
Yes, you can, if you think that 16 is coming more times them usual, try your luck....
And where exactly do you return the number+salt ahead of the bet?
In the responses I only see the last number, but I have not found any response that would actually return this field?
You can go to menu->Spins
It's still not ok. Limiting visibility of the hash to the first 7 characters is "provably fair theatre". Very easy to create collisions at only 7 chars. Waiting for them to show the full hash.
I mean the current setup is already "provably fair theatre" no matter if you show the full hash or not.
No. The concept is sound. If the roll is hashed, and the hash is revealed before the spin ends, then the roll is provably fair, because it cannot be changed without changing the hash.
However, It is trivial to create SHA256 hash collisions against a 7 character string. It is impossibly difficult to create collisions with the full 64 character hex string.
The authors know this - they base their entire thesis on this principle. Which is why it smells. They try to give the impression of being provably fair, while limiting the hash to just 7 characters is provably not fair. They have been advertising heavily here, unless this is addressed asap - show me the hash, @SN should reject their advertising sats and tell them to look for suckers elsewhere.
I can't but you can check the hash and salt