Dooglus, that's an interesting point about whether you know that a server is running an executable which is actually compiled from some open source code it's supposed to be compiled from. It seems to me that there might be some way to validate the executable via cryptography, but I don't have a concrete proposal. Very good point.
If you're interested, do a search for Succinct Non-interactive ARgument of Knowledge (SNARK), and you'll find a lot of interesting stuff. You can't validate the executable, but you can validate that it executed faithfully. However, in many ways, a provably fair system is already that. You can't be sure the software on MP.com is actually the software from github, but you can be sure that the crashes are fair.
I dunno, it still hasn't happened for me. So how much is 1000 bits in bitcoin?
There's 1,000,000 bits in a bitcoin. So that means 1,000 bits is 1/1000th (or 0.001) of a bitcoin. If you're having any issues, the friendly robot Shiba will help you out with
!convert 1000 bits to BTC
Well, this opens up a NEW can of worms.... I will most definately look into SNARK and ask around to understand how this work. The crashes might look fair, but if the software running on the server have the ability to interrupt that process, it would hardly be noticed, if it's done once a day.
It would be a big pitty, if this is done. MP is such a great game and this would spoil the fun, if it was rigged.
In my experience with them, everything looks fine.
I have read somewhere that some dice sites publishing a different hash from the acctual hash to fool people into thinking that their service was provably fair.