 Show Posts
|
|
Pages: « 1 [2] 3 »
|
Could you just show the hash on the page itself instead of burying it in the source code? It would be a lot easier to find and verify.
I thought about that, but wanted to keep the screen clean. I'll see what I can do. It looks like there are too many different sessions, checking into it. |
|
|
|
<!--
PROVABLY FAIR GAME INFO
6d08e7fe50f578642b19b8f009c00c2b115a6894ddb5aca97c9e034b9a1a1b65361dcaaaf287227 18898d49acc83b0dc3c3fd2f2047dc9bde135202193fc4cbd"
final hash: 2b9e1cef6692d072afd5d990b7529de268d952cf36030f82e03935e82ae17ed88638ff5765a2bd1 e1f5b4b3e598d7e68ee31be7a755c7bd5a07004c401bacd96
1NMuPoU6UW8qMziB5pVwc7YYDVjLQGhGDJ
Sent, thanks!  https://blockchain.info/address/1NMuPoU6UW8qMziB5pVwc7YYDVjLQGhGDJ |
|
|
|
No worries. Chrome does that, but I see the transaction. Do you want payment sent to this address? 1dR8EUiuDWczZvPDHeKLHu2ndYTkbGUE2Also congratulations on your win. |
|
|
|
Oh crap, didn't copy my game hash and closed the window.
No worries. I sent it. |
|
|
|
played demo lost straight away
my address 14bS9EdfWb3AkM3DeDQ9AJEtKqeKSRvmPZ
lol  Please make a deposit and play a live game for the .1 BTC giveaway. |
|
|
|
How many confirmations does a deposit have to have before a payout is sent? Just wondering. Currently have 2 for my .01 deposit, no .04 sent yet.
It's currently set at 3 confirmations. |
|
|
|
|
There are 4 more slots left for the .1 BTC giveaway!
Thanks to everyone helping test. Things are going well!
|
|
|
|
I would like to suggest to add a feature for partial payouts rather than bet all or withdraw all.
I'll look into that. Thanks for the feedback! |
|
|
|
Hey I deposited .01 BTC to 13vzAUnSynSPvVDpnmyLh9gJQBbuFD27x3. Won twice Can you please send my .04 BTC payout to 12U4MN1sNvtjAjVGQMcJKM4Sz3rQxUCWPd. Also can you please send my .1 free to 12U4MN1sNvtjAjVGQMcJKM4Sz3rQxUCWPd. Thanks! Sent .1 BTC to 12U4MN1sNvtjAjVGQMcJKM4Sz3rQxUCWPd https://blockchain.info/tx/518a15c805e1e8bef1d12971eca72ead0e59d9ab1f78e72fc483098a46289c96The system processes cash outs automatically after a few confirms of your deposit, so please be patient for that one. |
|
|
|
I think that's a great idea.
But you don't need to tell us what random number you got. Just tell us 'left' or 'right', with junk on the end, and hashed.
Then we don't need to worry about a 'secret', how to run hmac, etc. We just put the "left:wklfjslfkhrewg" string the you show after the game into a webpage that offers sha512 to people who don't know how to command line, check that the hash is the same as the one you showed before the game, and you're done.
Good point! I'll simplify it that way. Thanks! |
|
|
|
Here is the address it wants me to send to, you can credit .1 directly to my account thanks!
13ZY8SsE5HB8Zd8stSpexZiVz8NqJKSUqi
I couldn't find any deposit you made for 13ZY8SsE5HB8Zd8stSpexZiVz8NqJKSUqi I deposited 0.001 to try out the game to 13sCVRnMXKh2ZqhsrBo2aJJPaPEzcqxJSR , won once for 0.002 then lost it, not sure where to find the game hash, I would like to take the 0.1 btc offer to address 1ERd9wQz7pJ2S4EedrMLQoSbivPpZh8gCD
Sent .1 BTC to 1ERd9wQz7pJ2S4EedrMLQoSbivPpZh8gCD https://blockchain.info/tx/0522f7cebdf2d377fcab1df790cbaccf6138f05296108f7d638c6693608c15ebThanks! |
|
|
|
Here is the code in PHP:
Here's what I meant about a command line. See the bottom of this page? https://coinroll.it/bet/fa870f1e518eCommand line verification (bash shell)
echo -n 'b8d60cff5ca2fcd20fbd27987c671a65b32d40ed127c7a4bcaeb251600fc1365:0' | openssl dgst -sha512 -hmac 'WW4hgGFOiVZ0ITgIt89xG2R5OuAiEBTx3FDk2y2oDfJc94JkurVqn2mDwyk9oyr7' | sed 's/^.* //' | cut -c1-4 | xargs -I{} printf "%d\n" 0x{} Also, it's still not clear how you decide which card is the red one. Is it just whether the random number is even or odd? Edit: also, I think your scheme is overly complex. All you need to do is: 1) pick 'left' or 'right' at random 2) pick a longish random string 3) concatenate 1) and 2) 4) sha512 hash 3) 5) publish 4) before the game, and 3) after. No need for hmac, or a 'secret', or even a random number. Just a result (1) and a string to make reversing the hash impossible (2). Edit2: I wouldn't normally send coins to games with no history or reputation, but I figured it wouldn't be worth your while buying a domain for a 0.0006 BTC scam... Yes, you can check the value various ways. The point is the value can be verified and can't be changed by the house. If the last digit of the random number is odd the Red Ace is positioned left, and right if even. Sorry for not adding that in this thread, it's on the Provably Fair page. I agree the system can be done differently. The game you see now is slightly different from how it started. The main thing I wanted to achieve was true randomness, so I could even play the game myself. There was a study done by some professor that asked if people had some ability to predict the future. He used a game similar to this and over trials found some people seemed to be able to predict the right choice with slightly better than 50%, and it was a mystery how that happened. So I take truly random numbers from random.org to ensure randomness and run them through the system. |
|
|
|
Hi dooglus, I was waiting for your verdict You actually found a minor bug. Not a bug really, just the need to add " Hash: " to the message given to the player for the provably fair info. It's now updated. So, to check you would take that message and apply HMAC SHA-512, then append that hash to the message, and hash the whole thing which gives the final game hash. Here is the code in PHP: <?php
$secretkey = "796330129344107608179585"; //put the secret key here
$randomnumber = "527128"; //put the random number here
$message = "Random number is $randomnumber. Hash: ";
$hashmessage = hash_hmac('sha512', $message, $secretkey);
$messageandhash = $message.$hashmessage;
$finalhash = hash_hmac('sha512', $messageandhash, $secretkey);
echo ("<p>Message: $message <p> Message and hash: $messageandhash <p>Final hash: $finalhash");
?>
Here is the output for those values: Message: Random number is 527128. Hash:
Message and hash: Random number is 527128. Hash: ff72d43539e7dd82fc0bb861c77d87a286ab49e13149744e42e6980ba2b9495dd952461ecaadff301575b152a58f5db7d02a7b280adc3c5ec5ef0ac249efb449
Final hash: 0f8a39ef65dfbfb74239a956447b94e84c10695765d2520d020c9e20acb7301002a07186372d61b1a6d6e2062262bd981225aff5c5c1a60be1fe9952055785ed
Your .1 BTC has been sent. Thanks! |
|
|
|
No idea what my game hash is, but it wants me to pay to 13Bp6ytDR4J3v734y14ytSXFS76K7JfzD5.
The wallet you may send the 0.1 BTC to is 1QtHuSHkeMyZnKFHhf7UeEs4NusVnrVQq
EDIT:
Also from first post:
Experience ZERO House Fee during testing!
How about a 50/50 game where you actually do something
Your task is to find the Red Ace! It's a 50/50 chance which is provably fair. We use true random numbers from random.org. If you choose correctly your coins are DOUBLED (less 1.9% house fee).
-----
So what is it?
To start playing a game send an amount (.0006 to 1 BTC during testing) to the address it tells you. Your game starts automatically. If you click to view the page source code you will see your game hash just under the [body] tag. This is how you know the game is provably fair. After you make your choice you can click to view the source code again and you will see the message with random number used and secret key under the [body] tag as well as the game hash. Using these values anyone can verify that the random number is the same as before you made your choice, because it's not possible to change it and get the same hash value. Changing even one thing would dramatically change the hash. The 1.9% house fee is waived during testing. |
|
|
|
|
Okay, I'll send .1 BTC to the first 10 people to post their game hash and desired wallet address. Your game hash is available by clicking to view the page source code of your game.
|
|
|
|
|
