pull down to refresh

Can you elaborate on "provably fair"? How can I verify?
Absolutely! Here’s how we do it:
Before each spin, we generate a random number (0..36) and a salt, then publish the SHA-256 hash of num:salt After the spin, we reveal the salt, so you can re-hash the exact same num:salt combination. If the hash matches what we published before the spin, you know the result couldn’t have been altered.
reply
21 sats \ 3 replies \ @nout 11 Jan
So you could easily be generating number 16 slightly more often and insider would use this to their advantage, right? The hashing doesn't prevent that?
reply
Contrary to the popular belief, the house actually never wants to do this. It is in house's best interest to have as much random spread as possible, because non random leads to exploits.
reply
If you are talking major casino that wants to sit there for decades, then yeah. But in this case they can just for fun squeeze couple megasats out of this and shut it down.
reply
That's a good point, didn't think of that. Seems like there's always a way to get fucked over by the house :D
reply
101 sats \ 5 replies \ @pycan 4 Jan
Is the random number generated and hash published before any placed bets? Otherwise, you can still pick the number that is not in favor of most participants.
reply
Yes, absolutely. We publish the hashed result (random number + salt) before any bets are placed. Once it’s publicly hashed, we can’t just choose another salt or number afterward. Because of how SHA-256 works, forging a second salt to match the exact same hash is essentially impossible. When the spin ends, we disclose the salt so you can verify we didn’t alter the result based on bets.
reply
Where is it published?
reply
you can navigate to spins menu
reply
Right on. I see it. Cool.
reply
That makes sense, sounds good!
reply
Mint
reply
Wow, cool way to do provably fair! The logic checks out. I zapped ya 1K sats for that!
reply