I tried it with "brew", too. I installed a new "brew" version as explained at brew.sh, then the packages with brew and then a clean "git clone https://github.com/gabriel-eiger/bitcredit.git" and "cd bitcredit". Then "./autogen.sh", "./configure --with-gui" and then "make". Same problem. BTW: The instructions at https://github.com/gabriel-eiger/bitcredit/blob/master/doc/build-osx.md says, I should type "git clone https://github.com/bitcoin/bitcoin.git" and "cd bitcoin", which of course is wrong.

I tried to build it on my Mac, but it stops compiling with this error: http://pastebin.com/QkKx5QM6 Google finds some postings about it, but you already managed to build it, so maybe you know what is wrong. I used the instructions in doc/build-osx and MacPorts.

Nice multiplier, but I like higher bets: https://just-dice.com/roll/114210390

Just to make sure you don't call it "probably fair": it is called "provably fair". The reason is that it is not only probably a fair system, but the user can prove that the server is not cheating.

A good example is just-dice.com. I ported the JavaScript verifiers to Python (see https://bitcointalk.org/index.php?topic=586751.msg10190283#msg10190283 ), so that a user now can verify from the command line, too, that the server doesn't cheat.

Should be easy in PHP as well, because it has hash functions like SHA256. And of course, you can't use rand(), because it might allow users to predict the server random number. You should use a hardware random number generator.

Sure, you can use the script for whatever you like. Additional note: needs Python >=3.

Hush, bad kitty! Don't chew on the server cable!

Just for fun I ported the JavaScript verifier to a simple Python script, I hope it is right, worked for all bets I tested it with:

http://pastebin.com/uB1675LG

How provably fair works: when you click the "randomize" button, write down the server seed hash. Then gamble. Finally hit the randomize button again, click "ok" to generate a new server seed and then the "randomize" button again: it will show you the server seed which was used for your last rolls with the previous server seed. Use this, the hash and your client seed and start my script (or the JavaScript verifiers linked from the "Fair?" page at just-dice.com). It will test, if the server seed hash was created from the server seed and you will see the same lucky numbers. No cheating possible.

Probably your site is not fair

I wonder if it is possible to write some clever algorithm which predicts the next number, if you roll the dice thousands of times and use all the numbers for it, because a new server seed is generated only when I click the randomize button, and all other input numbers are known. The invested money would be gone very fast. Maybe better to generate a new server seed for each roll, of course with the same provably fair concept, that the gambler can see the server seed hash before rolling, and then with the randomize button the client random number can be changed. Just changing the random number independently with the same server seed, might be dangerous, because of some clever algorithm.

Does the site stop, if someone manages to write such a clever algorithm and wins e.g. more than half of the site investment, to investigate it? Or did the site admin get notified, if someone wins with 1000% luck in the stats and similar things?

And how safe is the server seed generator? It should be a true random number generator. Just software is not safe, because you have to assume that the source code is known. "/dev/random" might work, depending on the CPU, but might be not fast enough, with the new server seed generation concept.

Finally how safe are the servers? Is the source code and server setup audited by a security company? Does it have intrusion detection systems, DDoS firewall protection, multiple fallback servers around the world, good data backup systems etc.?