FlukyBet.com WIN 135% of your bet, 75+ % of players WIN [3rd Party escrow used] - page 2.

ninjaboon

legendary

Activity: 2128

Merit: 1002

Quote from: ninjaboon on February 04, 2015, 11:17:36 AM

Quote from: fluky on February 04, 2015, 11:16:02 AM

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

vote done.

any firm decision to the votes for Round 2?

ninjaboon

legendary

Activity: 2128

Merit: 1002

Quote from: fluky on February 04, 2015, 11:16:02 AM

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

vote done.

fluky

newbie

Activity: 42

Merit: 0

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

bloodyboy

full member

Activity: 199

Merit: 100

Quote from: ndnh on February 04, 2015, 03:49:39 AM

Quote from: bloodyboy on February 04, 2015, 03:45:04 AM

It will be better to refund this round before changing rules and start new one with clear rules for players IMHO

I agree with that. Or probably you should let it go on and let the cheaters lose their money. Grin

Hehe, it's tempting but it would be rather professional cancel this round

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Quote from: bloodyboy on February 04, 2015, 03:45:04 AM

It will be better to refund this round before changing rules and start new one with clear rules for players IMHO

I agree with that. Or probably you should let it go on and let the cheaters lose their money. Grin

bloodyboy

full member

Activity: 199

Merit: 100

It will be better to refund this round before changing rules and start new one with clear rules for players IMHO

Watoshi-Dimobuto

hero member

Activity: 840

Merit: 524

Yes!

Quote from: ndnh on February 04, 2015, 01:37:18 AM

I am going to make 1 more 000 hit in 4minutes to complete the check.

EDIT: Done. https://blockchain.info/rawtx/8ede8d6cc6059e2c846c9acadd8b648ff45444fd180f86503988e73157df7c9c

The checking is complete now.

Result: The method of using timestamp as a means of determining the order is exploitable.

Suggestion: Pick a different method. any mentioned above by funtotry or me or something else.

Great work, ndnhc. Cheesy

You did good. You didn't try to steal money of players and instead helped them. You certainly deserve something.

Keep up the good work, bro,

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Quote from: fluky on February 04, 2015, 02:17:42 AM

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:
45040

Yes, I think that will do.

fluky

newbie

Activity: 42

Merit: 0

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:
45040

Btw, thanks

, I sent back your coins from another wallet:
https://blockchain.info/tx/ef0c0a564e1ad69b2bdbb0dbc587540838951bc0b4fad0a028dbfc948863ea3a

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Quote from: fluky on February 04, 2015, 01:34:18 AM

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?

Yes. the check was done completely manual. I have no knowledge of coding and programming. Never created a bot in my life.
Now, I can do it very good with max error of 1 to 2 seconds. and 70%+ accuracy

I am going to make 1 more 000 hit in 4minutes to complete the check.

EDIT: Done. https://blockchain.info/rawtx/8ede8d6cc6059e2c846c9acadd8b648ff45444fd180f86503988e73157df7c9c

The checking is complete now.

Result: The method of using timestamp as a means of determining the order is exploitable.

Suggestion: Pick a different method. any mentioned above by funtotry or me or something else.

fluky

newbie

Activity: 42

Merit: 0

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?

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Results: (will be updated here.)
Target less than 100

1st one miss

2nd and 3rd : 138, 438 miss
Huh

4th : big miss

I think a bot can do it. I am doing manual second count.

Upgraded my mrthod.

TARGET:007

FAILED: BY 3 seconds

NEW: 009

FAILED: By 2 seconds : 1423027898

Changed my method to a better one.

NEW : 000

MISSION ACCOMPLISHED: https://blockchain.info/rawtx/6ed48e492ca760e6ce59528320eeca6ebec438a949a2ca02904fdf09cf019ea5

NEW : 003

1 sec miss: time:1423028299,

1 sec miss again: https://blockchain.info/rawtx/d239ed85d88abc722634bae851743b6aba1062328a1dff595c1d05fdd8b0a3ed

HIT: https://blockchain.info/rawtx/3b6277a7c0251d29b0a3387e12566adedc95e809face634885a93ff4601927e2

Now I know exactly when to make the transaction.

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Quote from: fluky on February 03, 2015, 11:43:12 PM

Quote from: ndnh on February 03, 2015, 10:12:11 PM

Quote from: ndnh on February 03, 2015, 10:07:25 PM

Quote from: fluky on February 03, 2015, 09:58:38 PM

Quote from: funtotry on February 03, 2015, 07:22:59 PM

Quote from: ninjaboon on February 03, 2015, 06:37:41 PM

Quote from: funtotry on February 03, 2015, 12:10:57 PM

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?

Yes I will be checking the timestamp method.

fluky

newbie

Activity: 42

Merit: 0

I took your advice @funtotry, thx!, and put it in the previous post what do you think?

fluky

newbie

Activity: 42

Merit: 0

Quote from: bobc1994 on February 03, 2015, 11:09:02 PM

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 = 724

or 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.

funtotry

sr. member

Activity: 420

Merit: 250

Ever wanted to run your own casino? PM me for info

Quote from: fluky on February 03, 2015, 09:58:38 PM

Quote from: funtotry on February 03, 2015, 07:22:59 PM

Quote from: ninjaboon on February 03, 2015, 06:37:41 PM

Quote from: funtotry on February 03, 2015, 12:10:57 PM

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.

Timestamp cant be changed but you can still resent the tx if the time received is bad. Also anyone can hash block height with the txid and then resent if its bad. Maybe hash the block hash of the next block that it confirms in, I am not sure if you can guess the next block hash but I dont think you can.

fluky

newbie

Activity: 42

Merit: 0

Quote from: ndnh on February 03, 2015, 10:12:11 PM

Quote from: ndnh on February 03, 2015, 10:07:25 PM

Quote from: fluky on February 03, 2015, 09:58:38 PM

Quote from: funtotry on February 03, 2015, 07:22:59 PM

Quote from: ninjaboon on February 03, 2015, 06:37:41 PM

Quote from: funtotry on February 03, 2015, 12:10:57 PM

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?

bobc1994

sr. member

Activity: 269

Merit: 250

this is generated from random numer ? Provably Fair ?

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Quote from: ndnh on February 03, 2015, 10:07:25 PM

Quote from: fluky on February 03, 2015, 09:58:38 PM

Quote from: funtotry on February 03, 2015, 07:22:59 PM

Quote from: ninjaboon on February 03, 2015, 06:37:41 PM

Quote from: funtotry on February 03, 2015, 12:10:57 PM

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.)

ndnh

legendary

Activity: 1302

Merit: 1005

New Decentralized Nuclear Hobbit

Quote from: fluky on February 03, 2015, 09:58:38 PM

Quote from: funtotry on February 03, 2015, 07:22:59 PM

Quote from: ninjaboon on February 03, 2015, 06:37:41 PM

Quote from: funtotry on February 03, 2015, 12:10:57 PM

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.

Topic: FlukyBet.com WIN 135% of your bet, 75+ % of players WIN [3rd Party escrow used] - page 2. (Read 5726 times)