Pages:
Author

Topic: Gambling Idea? Go or No? (Read 1672 times)

sr. member
Activity: 420
Merit: 250
October 18, 2013, 06:12:56 AM
#35
No. The second hash is generated by blockchain.info API, over which we have 0 control. The way their api works is like this:

A player deposits money to a blockchain.info address - with a generated by the player transaction id
blockchain.info reroutes the transaction towards the final destination (our wallet address) - blockchain.info generates their own transaction id

We combine the player transaction hash and the blockchain.info generated hash to receive the final value.

We don't have control over either one, since we don't initiate either transaction of the 2. We cannot manipulate either one, and the player cannot manipulate the blockchain.info one. So it cannot be cheated by either party.

You're using the receive method in their api then?  (https://blockchain.info/api/receive?method=create&address=$receiving_address&callback=$callback_url)

If so, then I no longer believe you have the ability to alter the results in your instant win game.  Thanks for clearing that up.


Yes that's correct. And it very much reproduces marcotheminer's idea (or a very similar one) in a non-cheatable way.
The real concern is that there could be a chance that Blockchain.info is generating TXIDs, until it creates one that benefits the casino. We all know that the chance of this happening is probably zero, but it is not 100% provably fair. This could cause players to be concerned, even though it is very unlikely that there is a cooperation between blockchain.info and bit777.

The provably fair system implemented by casinos such as satoshidice cannot be rigged by the operator or any other parties, since it is backed by cryptography.

Is this not correct?

Yes, technically you are correct. If there is a hidden alliance between us and blockchain.info, then the fairness can be jeopardized.
b!z
legendary
Activity: 1582
Merit: 1010
October 17, 2013, 11:30:51 PM
#34
No. The second hash is generated by blockchain.info API, over which we have 0 control. The way their api works is like this:

A player deposits money to a blockchain.info address - with a generated by the player transaction id
blockchain.info reroutes the transaction towards the final destination (our wallet address) - blockchain.info generates their own transaction id

We combine the player transaction hash and the blockchain.info generated hash to receive the final value.

We don't have control over either one, since we don't initiate either transaction of the 2. We cannot manipulate either one, and the player cannot manipulate the blockchain.info one. So it cannot be cheated by either party.

You're using the receive method in their api then?  (https://blockchain.info/api/receive?method=create&address=$receiving_address&callback=$callback_url)

If so, then I no longer believe you have the ability to alter the results in your instant win game.  Thanks for clearing that up.


Yes that's correct. And it very much reproduces marcotheminer's idea (or a very similar one) in a non-cheatable way.
The real concern is that there could be a chance that Blockchain.info is generating TXIDs, until it creates one that benefits the casino. We all know that the chance of this happening is probably zero, but it is not 100% provably fair. This could cause players to be concerned, even though it is very unlikely that there is a cooperation between blockchain.info and bit777.

The provably fair system implemented by casinos such as satoshidice cannot be rigged by the operator or any other parties, since it is backed by cryptography.

Is this not correct?
sr. member
Activity: 420
Merit: 250
October 17, 2013, 03:33:55 PM
#33
No. The second hash is generated by blockchain.info API, over which we have 0 control. The way their api works is like this:

A player deposits money to a blockchain.info address - with a generated by the player transaction id
blockchain.info reroutes the transaction towards the final destination (our wallet address) - blockchain.info generates their own transaction id

We combine the player transaction hash and the blockchain.info generated hash to receive the final value.

We don't have control over either one, since we don't initiate either transaction of the 2. We cannot manipulate either one, and the player cannot manipulate the blockchain.info one. So it cannot be cheated by either party.

You're using the receive method in their api then?  (https://blockchain.info/api/receive?method=create&address=$receiving_address&callback=$callback_url)

If so, then I no longer believe you have the ability to alter the results in your instant win game.  Thanks for clearing that up.


Yes that's correct. And it very much reproduces marcotheminer's idea (or a very similar one) in a non-cheatable way.
sr. member
Activity: 285
Merit: 262
October 17, 2013, 03:31:13 PM
#32
No. The second hash is generated by blockchain.info API, over which we have 0 control. The way their api works is like this:

A player deposits money to a blockchain.info address - with a generated by the player transaction id
blockchain.info reroutes the transaction towards the final destination (our wallet address) - blockchain.info generates their own transaction id

We combine the player transaction hash and the blockchain.info generated hash to receive the final value.

We don't have control over either one, since we don't initiate either transaction of the 2. We cannot manipulate either one, and the player cannot manipulate the blockchain.info one. So it cannot be cheated by either party.

You're using the receive method in their api then?  (https://blockchain.info/api/receive?method=create&address=$receiving_address&callback=$callback_url)

If so, then I no longer believe you have the ability to alter the results in your instant win game.  Thanks for clearing that up.
full member
Activity: 154
Merit: 100
October 17, 2013, 03:14:34 PM
#31
I don't believe it's a good idea.
sr. member
Activity: 420
Merit: 250
October 17, 2013, 12:57:31 PM
#29
No. The second hash is generated by blockchain.info API

Oh, that's completely fine then. Assuming you don't have a secret kind of alliance with blockchain.info. Wink

Unfortunately we don't! I would love to have our game right inside the wallet similar to the way SD has theirs Smiley
legendary
Activity: 1134
Merit: 1118
October 17, 2013, 12:54:31 PM
#28
No. The second hash is generated by blockchain.info API

Oh, that's completely fine then. Assuming you don't have a secret kind of alliance with blockchain.info. Wink
sr. member
Activity: 348
Merit: 250
October 17, 2013, 12:53:36 PM
#27
following this discussion now with big interest. I hope at the end we all will know what really is and who is provably fair.
sr. member
Activity: 420
Merit: 250
October 17, 2013, 12:49:20 PM
#26
No. The second hash is generated by blockchain.info API, over which we have 0 control. The way their api works is like this:

A player deposits money to a blockchain.info address - with a generated by the player transaction id
blockchain.info reroutes the transaction towards the final destination (our wallet address) - blockchain.info generates their own transaction id

We combine the player transaction hash and the blockchain.info generated hash to receive the final value.

We don't have control over either one, since we don't initiate either transaction of the 2. We cannot manipulate either one, and the player cannot manipulate the blockchain.info one. So it cannot be cheated by either party.
legendary
Activity: 1134
Merit: 1118
October 17, 2013, 12:40:54 PM
#25
Just to be clear, the bit777 instant gamble uses the hash of the txid of the incoming transaction plus the txid of a second transaction, and this second transaction originates from the bit777 wallet, correct?  If this is so, then it would be trivial for bit777 to determine the result of any instant gamble through methods described in this thread.

Yep, you're right about that. bit777 could create any bet result quickly.
sr. member
Activity: 285
Merit: 262
October 17, 2013, 12:02:01 PM
#24
Just to be clear, the bit777 instant gamble uses the hash of the txid of the incoming transaction plus the txid of a second transaction, and this second transaction originates from the bit777 wallet, correct?  If this is so, then it would be trivial for bit777 to determine the result of any instant gamble through methods described in this thread.

I have no reason to believe this is actually happening, but I think that is the point b!z is trying to make.  Regardless, the majority of the games on bit777 aren't provably fair as defined by the bitcoin community anyway, so I doubt it matters to anyone gambling there.  You could easily just use the sdice method of generating a secret per day, hashing it, and releasing the hash.  Generate your result as secret+hash and then no one can complain.
legendary
Activity: 1134
Merit: 1118
October 17, 2013, 11:55:14 AM
#23
I can use rawtransactions and bankrupt your casino within a few minutes-an hour depending on my bankroll. Terrible idea.
sr. member
Activity: 420
Merit: 250
October 17, 2013, 11:37:54 AM
#22
We don't have control over either of the 2 hashes. They both come from the blockchain. Hence, we cannot manipulate the outcome in any way. Hence it is provably fair.

That's not how it supposed to work. Provably fair means you give the players a key before they place the bet, which they can then use after they've lost or won to confirm that there was no cheating.

If you check our explanation on site, you will see that we give the players an option to check each transaction themselves.
b!z
legendary
Activity: 1582
Merit: 1010
October 17, 2013, 09:58:11 AM
#21

It is not provably fair, and the link he provided does not claim that it is provably fair.

From what I can see, you can prove how the results are calculated, but you cannot prove that it is fair.



No, I am not. Maybe you should sit down and think about how wrong you are.
newbie
Activity: 42
Merit: 0
October 17, 2013, 09:04:04 AM
#20
Alright so I came across this idea for gambling using the TX ID of bets which would be sent through.

Simply send a bet to (address here) and if the last digit of the TX ID is an even number you win 1.98X your bet in return,

What I want to know is: Is this a good idea and Can someone exploit this in any way?


https://lh3.ggpht.com/--nlocNUuLjk/TdE91pktk_I/AAAAAAAAAGQ/J6D2FEXdj3s/s400/LabelForItSucks.jpg
legendary
Activity: 1008
Merit: 1007
October 17, 2013, 08:54:00 AM
#19
We don't have control over either of the 2 hashes. They both come from the blockchain. Hence, we cannot manipulate the outcome in any way. Hence it is provably fair.

That's not how it supposed to work. Provably fair means you give the players a key before they place the bet, which they can then use after they've lost or won to confirm that there was no cheating.
sr. member
Activity: 420
Merit: 250
October 17, 2013, 02:56:59 AM
#18
We don't have control over either of the 2 hashes. They both come from the blockchain. Hence, we cannot manipulate the outcome in any way. Hence it is provably fair.
newbie
Activity: 42
Merit: 0
October 17, 2013, 02:55:40 AM
#17

It is not provably fair, and the link he provided does not claim that it is provably fair.

From what I can see, you can prove how the results are calculated, but you cannot prove that it is fair.

http://static2.fjcdn.com/comments/Are+you+for+real+man+Jesus+Christ+do+you+not+_84dee4bd81a89f503bbb65ca10940327.jpg
b!z
legendary
Activity: 1582
Merit: 1010
October 17, 2013, 02:20:11 AM
#16
You should take a look at our instant gamble. We have already built this game and it works rather well: https://www.bit777.com/support/instant_gamble.aspx . We have had this game for the past 2 months. It can't be cheated by the method above, because it also uses the 2nd hash generated by blockchain.info api when rerouting the transaction towards the final address.

How can that possibly be provably fair? The outgoing transaction contains the winnings which means the odds have already been computed, so you can't possibly use that hash to compute the random number.

It is not provably fair, and the link he provided does not claim that it is provably fair.

From what I can see, you can prove how the results are calculated, but you cannot prove that it is fair.
Pages:
Jump to: