 Show Posts
|
|
Pages: [1] 2 3 »
|
dont give up yet, all new sites starts from the bottom, even PD and JD start at the bottom where the interest of gamlbing there is pretty low, you should make your site more trustable anyway  Thank you for the encouragement WEBcreator, I know that, I just didn't invested enough time and effort promoting it, as I'm busy with another projects, now I can't do it for now, I know trust is hard to earn but what would you recommend? I was thinking in giving more prizes from my own wallet, and getting more known, unfortunately, many scam sites keep appearing and each day it's more difficult for people to trut new sites. Thank you so much ninjaboon, for you service, I highly recommend you. I totally forgot about this, but I still think this is very nice idea.
One thing that I would like to see changed is max deposit amount, difference between max an min can't be 100x IMHO unless site becomes super-popular.
Thank you pozmu, I may continue the site later, but with more variety of games and options, once I get enough time and have some extra-money to invest in the site. And you're completely right, I think a 10x should be good enough.  |
|
|
|
|
Thank you very much Ninjaboon for acting as escrow for flukybet.com. You're a very trustable and accountable person.
I highly recommend him!
|
|
|
|
Hi, Sorry for my abscence, as the interest declined, I'll declared the game closed for the moment. Thank you to every participant, to ninjaboon for helping as escrow (I highly recommend him) and congrats to all the winners!!   Note: The last person to deposit will get his btc refunded. |
|
|
|
Yep, as an admin of the site, I can confirm, any possible exploit is now covered. Thank you to the users who pointed that out in Round #2 so any issue was prevented. Round #3 has just started!! |
|
|
|
Transactions refunded, thank you to ninjaboon for his work, the round continues now with the new draw number rules. Good luck to everyone! |
|
|
|
Ok, so the voters decided. We'll refund your whole deposit for this round and start again. Because our escrow provider is not available right now, your funds will be sent back at 12:00 PM GMT, that is aprox. 6 hours after this message, thank you for your patience! and all new deposits will follow the new rules for this Round 2 Reloaded |
|
|
|
Ok, so we have a tie score. Extented voting time, please vote to decide it |
|
|
|
Ok, what would you like to be done with this round (Continue or refund)?. The decision would be taken according to this poll, Please vote http://strawpoll.me/3560796 |
|
|
|
Thank you! So this would be the method: the txid + hash of the next block from the block_height that included the transaction, then hashed, then the 13,14,15,16 digit then to decimal, like this: b1efe3ed66420f5c0956dfab0f17baaf08626a763d59501d92f3790c4a1071a9 So: b1efe3ed66420f5c0956dfab0f17baaf08626a763d59501d92f3790c4a1071a9 +
00000000000000000fbceb08d7f309339f2307a5941104dace6da723077f112c (That's the next block hash of the block-height 341854 which included that transaction)
Then hashed it's:
4b6ecf89594caff0ef2528e636ee682b774e30ae7a180d534a8e9dc2178081b2
So the digits are:
aff0
So the draw number would be:
45040Btw, thanks , I sent back your coins from another wallet: https://blockchain.info/tx/ef0c0a564e1ad69b2bdbb0dbc587540838951bc0b4fad0a028dbfc948863ea3a |
|
|
|
|
Oh, I see your transactions, actually that could make the game exciting, trying to get the lowest millisecond, but if there's a bot it would screw everything, do you know something about what @funtotry said?
Timestamp cant be changed but you can still resent the tx if the time received is bad.
Edit: I see your 000, wow well done, did you manually got that?
|
|
|
|
|
I took your advice @funtotry, thx!, and put it in the previous post what do you think?
|
|
|
|
this is generated from random numer ? Provably Fair ?
Yes! For the first round it was based on some digits of the txid of the deposit (the 1st post has details), but we noticed one player probably tried to alter it to gain advantage, so we're testing and deciding if we go with the unix timestamp of the deposit. i.e. b1efe3ed66420f5c0956dfab0f17baaf08626a763d59501d92f3790c4a1071a9 1423018427 = 724or with the txid + hash of the next block from the block_height that included the transaction, then hashed, then the 13,14,15,16 digit then to decimal, like this: b1efe3ed66420f5c0956dfab0f17baaf08626a763d59501d92f3790c4a1071a9 So: b1efe3ed66420f5c0956dfab0f17baaf08626a763d59501d92f3790c4a1071a9 + 00000000000000000fbceb08d7f309339f2307a5941104dace6da723077f112c (That's the next block hash of the block-height 341854 which included that transaction) Then hashed it's: 4b6ecf89594caff0ef2528e636ee682b774e30ae7a180d534a8e9dc2178081b2 So the digits are: aff0 So the draw number would be: 45040 But, every method can be checked and verified by all users so yes it's provably fair. |
|
|
|
Problem with the system i could keep submitting raw hex transactions and keep going for the tx id that I want, and don't broadcast it if its a txid that makes you win. Maybe hash the tx with a secret key, and you provide the sha256 hash of that secret key to verify that you aren't change it. This would make the random number not predictable if you don't know the secret key, which is released at the end of the day (week in this case)
makers sense now. Fluky will be using the unix timestamp from now. thanks all. Unix timestamp with milliseconds, seconds can be changed, also with the timestamp can't you just end at 01 seconds instead of 60 and be in first? Doesn't make sense to me Thanks for your reply, You say that the unix time stamp can be changed? The value will be taken from the "received time" by blockchain.info that value can't be changed, can it? Also 00 will win over 01 because the number would be taken from the 3 first digit of the inversed unix time: like 1422265904 = 409. Althought the players could try to get it in the lowest digit it's very easy to fail and get a higher number. Another option is adding the TXID with the hash of the block-height where it was included then hashed again, that way I think there's no way it can be changed, what do you think? Btw, while this get sorted out, the round will be increased by 24 hrs. Btw, we've noticed some other strange transactions. Yeah, good thing the order is reversed. I think it is okay. Most games like this hash the txid and use it to determine the winner, etc. I personally use blockchain wallet, on which doing so is either not possible or unknown? Just check it with someone else, since personally I am not so much into bitcoin and blockcain tech. I rechecked, but I think I could myself be able to use this to win. Do you want me to do a check? All i take is probably a few tries and I will come up with a good method to do it. Can you provide an address for me to check? (I have helped many sites with similar and different explitable systems, and I don't make a profit out of this. You can trust me. I will use only small amounts to check. and to your address so that you can see, please return the amount after the test.) Sure, you can test here 18aR3Buve9nFMrhEpVxxaBku3Kg2sxjU6W I'll return your amount, and a little tip after you finish. You'll try the timestamp method right? |
|
|
|
Problem with the system i could keep submitting raw hex transactions and keep going for the tx id that I want, and don't broadcast it if its a txid that makes you win. Maybe hash the tx with a secret key, and you provide the sha256 hash of that secret key to verify that you aren't change it. This would make the random number not predictable if you don't know the secret key, which is released at the end of the day (week in this case)
makers sense now. Fluky will be using the unix timestamp from now. thanks all. Unix timestamp with milliseconds, seconds can be changed, also with the timestamp can't you just end at 01 seconds instead of 60 and be in first? Doesn't make sense to me Thanks for your reply, You say that the unix time stamp can be changed? The value will be taken from the "received time" by blockchain.info that value can't be changed, can it? Also 00 will win over 01 because the number would be taken from the 3 first digit of the inversed unix time: like 1422265904 = 409. Althought the players could try to get it in the lowest digit it's very easy to fail and get a higher number. Another option is adding the TXID with the hash of the block-height where it was included then hashed again, that way I think there's no way it can be changed, what do you think? Btw, while this get sorted out, the round will be increased by 24 hrs. Btw, we've noticed some other strange transactions. |
|
|
|
So, someone finally developed a honest and transparent escrowed ponzi . Good to see such things. Thanks for the props! |
|
|
|
Suspicious tx in ROund #1 17 1CG1R4BimSyaFUhaEqiANLsuX28UpziYBt 0.09 0.1215 a3f12bb... [007b] 2/1/2015 9:54:03 AM UTC 123 Win d14e39c... The fact that the highest amount was put in by the same user makes it even more suspicious.Thanks for the tip, didn't know about it sorry  , it seems a possibility , it looks to me like a cheater, if so, I'll refund that amount to the players that lost fair playing. Now about the system, It'll be changed to the unix timestamp of the transaction, i.e. for that one https://blockchain.info/rawtx/a3f12bb4f79f007ba4589367aab8e0bcbab90a65faff1d4571de2b5c4dcded8bit would be 1422784443 = 344 I'm almost sure that couldn't be changed, what do you think? |
|
|
|
Congratulations !!, And to all the winners! Btw I changed the rounds to just 72 hours so the wait should be shorter now! Congrats to Round #1 winners too. I helped in the payouts as the official escrow. Yep, thank you for that. leme try to turn my .005btc into 1btc here Good luck!! |
|
|
|
Congratulations !!, And to all the winners! Btw I changed the rounds to just 72 hours so the wait should be shorter now! |
|
|
|
Yep!! A couple of hrs were added to the timer, last chance to enter the round, new round will start at the end of the last one |
|
|
|
Just 40 hours left till payout  Some players already looking like winners like Player #11 and #4 |
|
|
|
|
