Start your own profitable casino in few minutes. Better security, new skin!

johny1976

legendary

Activity: 1135

Merit: 1002

Developer

Quote from: alabamafan1 on March 16, 2014, 08:57:02 PM

Quote from: johny1976 on March 16, 2014, 08:54:39 PM

Quote from: RGBKey on March 16, 2014, 08:42:32 PM

Quote from: johny1976 on March 16, 2014, 08:38:09 PM

Quote from: RGBKey on March 16, 2014, 08:31:49 PM

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

1) Server generates the result (0.01-9.99) and gives a random string before it = seed. then shows you sha256 hash of this seed.
2) You place the bet
3) The bet gets a result and the seed is shown to you. You can compare sha256 (which was shown you before betting) hash with the hash of the result and you'll see that the hashes are same.

This isn't provably fair, this is just provable results. The server can generate whatever it wants to make you lose, and all you know is that it doesn't change the results that make you lose before you bet. Afterwards, it shows you that it didn't change the results. The problem with this is that it isn't random, and the user cannot influence the roll in a random way. You need to make use of a client seed to get this to be provably fair.

I do not agree.

The user defines himself which value is winning and which is losing. And it's after the result is generated.

So in this case it's enough, because server doesn't know which result generate to make user lose. Wink

Anyway, the code is open and you can check fairness by yourself.

The server can be manipulated to observe players' betting patterns and recreate hashes before the rolls to go against the players' typical patterns such as a player always betting the number will be high or that the number will be low many times in a row. Loaded rolls are thus a possiblity with your script meaning your script is not provably fair.

Ok, theoreticaly. But you can check the code and see that it actually is fair.

alabamafan1

full member

Activity: 210

Merit: 100

Quote from: johny1976 on March 16, 2014, 08:54:39 PM

Quote from: RGBKey on March 16, 2014, 08:42:32 PM

Quote from: johny1976 on March 16, 2014, 08:38:09 PM

Quote from: RGBKey on March 16, 2014, 08:31:49 PM

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

1) Server generates the result (0.01-9.99) and gives a random string before it = seed. then shows you sha256 hash of this seed.
2) You place the bet
3) The bet gets a result and the seed is shown to you. You can compare sha256 (which was shown you before betting) hash with the hash of the result and you'll see that the hashes are same.

This isn't provably fair, this is just provable results. The server can generate whatever it wants to make you lose, and all you know is that it doesn't change the results that make you lose before you bet. Afterwards, it shows you that it didn't change the results. The problem with this is that it isn't random, and the user cannot influence the roll in a random way. You need to make use of a client seed to get this to be provably fair.

I do not agree.

The user defines himself which value is winning and which is losing. And it's after the result is generated.

So in this case it's enough, because server doesn't know which result generate to make user lose. Wink

Anyway, the code is open and you can check fairness by yourself.

The server can be manipulated to observe players' betting patterns and recreate hashes before the rolls to go against the players' typical patterns such as a player always betting the number will be high or that the number will be low many times in a row. Loaded rolls are thus a possiblity with your script meaning your script is not provably fair.

johny1976

legendary

Activity: 1135

Merit: 1002

Developer

Quote from: RGBKey on March 16, 2014, 08:42:32 PM

Quote from: johny1976 on March 16, 2014, 08:38:09 PM

Quote from: RGBKey on March 16, 2014, 08:31:49 PM

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

1) Server generates the result (0.01-9.99) and gives a random string before it = seed. then shows you sha256 hash of this seed.
2) You place the bet
3) The bet gets a result and the seed is shown to you. You can compare sha256 (which was shown you before betting) hash with the hash of the result and you'll see that the hashes are same.

This isn't provably fair, this is just provable results. The server can generate whatever it wants to make you lose, and all you know is that it doesn't change the results that make you lose before you bet. Afterwards, it shows you that it didn't change the results. The problem with this is that it isn't random, and the user cannot influence the roll in a random way. You need to make use of a client seed to get this to be provably fair.

I do not agree.

The user defines himself which value is winning and which is losing. And it's after the result is generated.

So in this case it's enough, because server doesn't know which result generate to make user lose. Wink

Anyway, the code is open and you can check fairness by yourself.

alabamafan1

full member

Activity: 210

Merit: 100

Quote from: johny1976 on March 16, 2014, 08:38:09 PM

Quote from: RGBKey on March 16, 2014, 08:31:49 PM

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

1) Server generates the result (0.01-9.99) and gives a random string before it = seed. then shows you sha256 hash of this seed.
2) You place the bet
3) The bet gets a result and the seed is shown to you. You can compare sha256 (which was shown you before betting) hash with the hash of the result and you'll see that the hashes are same.

Provably fair means that the server seed and secret are created by you, but the 3rd seed, the client seed, can be changed to anything by the player. This prevents your server from guessing the players next move (like if they always go low or always go high) and giving them "loaded" seeds that will most likely cause them to lose based on their betting patterns.

Your script is not provably fair.

RGBKey

hero member

Activity: 854

Merit: 658

rgbkey.github.io/pgp.txt

Quote from: johny1976 on March 16, 2014, 08:38:09 PM

Quote from: RGBKey on March 16, 2014, 08:31:49 PM

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

1) Server generates the result (0.01-9.99) and gives a random string before it = seed. then shows you sha256 hash of this seed.
2) You place the bet
3) The bet gets a result and the seed is shown to you. You can compare sha256 (which was shown you before betting) hash with the hash of the result and you'll see that the hashes are same.

This isn't provably fair, this is just provable results. The server can generate whatever it wants to make you lose, and all you know is that it doesn't change the results that make you lose before you bet. Afterwards, it shows you that it didn't change the results. The problem with this is that it isn't random, and the user cannot influence the roll in a random way. You need to make use of a client seed to get this to be provably fair.

johny1976

legendary

Activity: 1135

Merit: 1002

Developer

Quote from: RGBKey on March 16, 2014, 08:31:49 PM

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

1) Server generates the result (0.01-9.99) and gives a random string before it = seed. then shows you sha256 hash of this seed.
2) You place the bet
3) The bet gets a result and the seed is shown to you. You can compare sha256 (which was shown you before betting) hash with the hash of the result and you'll see that the hashes are same.

RGBKey

hero member

Activity: 854

Merit: 658

rgbkey.github.io/pgp.txt

Quote from: johny1976 on March 16, 2014, 08:26:56 PM

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

Please explain how the provably fair process works.

johny1976

legendary

Activity: 1135

Merit: 1002

Developer

Quote from: RGBKey on March 16, 2014, 08:21:44 PM

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

It is provably fair. And if I say provably I mean that everybody can check it really is.

Stop trolling around please.

RGBKey

hero member

Activity: 854

Merit: 658

rgbkey.github.io/pgp.txt

Please don't advertise this script as provably fair when it isn't. You're just trying to trick people.

johny1976

legendary

Activity: 1135

Merit: 1002

Developer

Quote from: alabamafan1 on March 16, 2014, 08:15:00 PM

Your scripts have been known to have back door "send all BTC to you or your conspirators" in the code. 2 dice sites have already fallen victim. I'd advise against this people unless you know how to read code 100%.

And many more is running without problems.

The steals wasn't caused by our script, but the buyers had not enough knowledge about server security.

You did not even buy the script.

Quote from: jontstaz on March 16, 2014, 08:15:15 PM

Sure it's profitable until johny goes in through his backdoor and dumps your funds to his wallet. I have this script and various others have also confirmed the intentional backdoor.

Next time try to better secure your server, hackers today are more sophisticated than ever before. The script was controlled by security experts and no backdoor was found

This means that you're just trolling around.

jontstaz

member

Activity: 84

Merit: 10

Sure it's profitable until johny goes in through his backdoor and dumps your funds to his wallet. I have this script and various others have also confirmed the intentional backdoor.

alabamafan1

full member

Activity: 210

Merit: 100

Your scripts have been known to have back door "send all BTC to you or your conspirators" in the code. 2 dice sites have already fallen victim. I'd advise against this people unless you know how to read code 100%.

johny1976

legendary

Activity: 1135

Merit: 1002

Developer

Hey,

Have you ever wanted to run your own profitable casino?

Start your dice site in a few minutes! (auto installation and support included)

CoinDice v3.

https://bitcointalksearch.org/topic/coindice-start-your-own-dice-site-today-507515

Topic: Start your own profitable casino in few minutes. Better security, new skin! (Read 760 times)