probiwon.com: New gambling shooting game with 94.2% return

[bitcoinex]

A technical request. Could you share the part that process the bets? ex. How does it know a when a bet is made and I assume it later calls the gambling system.

It is just uses new 'listtransactions' call to bitcoind:
https://www.bitcoin.org/smf/index.php?topic=2343.0

I am interested in this to put an ATM where you can get the local currency for Bitcoins. This help would be appreciated.

I suppose you are using the PHP library. Do you query it constantly(Ex. each 5 seconds) or does the client(bitcoind[.exe|.app|]) report on any transaction? I just want to know if there is a more practical way to do it.

Unfortunately, bitcoin not able to report that that has received a new transaction - bitcoin concept contains only the probability of obtaining money defined by a number of confirmations, as I understand it. But a 1 confirmation is already a very good chance that you got the money.

So I just ask regularly bitcoind. It is important not to miss a transaction, becouse listtransactions do not report number of transactions - it is gives only list latest from them.

[1713952696]

1713952696

[1713952696]

1713952696

[1713952696]

1713952696

[1713952696]

1713952696

[bitcoinex]

A quick question. Could you show some pseudocode of how you handle the bets? Does the acceptor plays any role in the odds?

After creation of a new addresses pair (your address + acceptor address) site generates random secret, shows sha256(secret) to you and waits for your bet. After bet is accepted and game played new random secret generated immediately and site waits bet again.

I haven't played this yet, and I'm curious how this hash verification works.  If I understand correctly, you display the sha256 of some unique data, AKA "secret" before the player places his bet.  Then the player bets whatever amount they like up to 15 BTC, and is shown the ring that was hit, along with the "secret" used.  While it is easy to verify the secret matches the hash, I don't understand is how the "secret" relates to which ring is hit, as that would be the most important part to verify that the game is fair.

It determine coordinates of the hit by getting first 4 bytes from this secret number. For example:

hash of secret: 4d1cb8895e10ed6f6dfc0013049df07f7e9794fd716b3b8e509f6581f2b934e3

After accepting your bet you will see secret and coords of hit:

secret: 0d37cc844521dbfdb92399be793a1bc3
x=0.05162127107652399481 (d37 / ffff)
y=0.79890135042343785763 (cc84 / ffff)

[sputnik]

Some statistics:
Num. Out  In
1.     0.50 0.25
2.     0.52 0.90
3.     0.30 0.10
4.     0.10 0.02
5.     0.90 0.18
6.     0.02 0.10
7.     0.18 0.36
8.     0.09 0.00
9.     0.37 1.11

Total
Out 2.98
In   3.02

[bitcoinex]

Too few attempts

[bitcoinex]

Added short sound when accepting bets. A very long time new blocks are generating, so it is convenient to hear when bid will be accepted.

[Mahkul]

Added short sound when accepting bets. A very long time new blocks are generating, so it is convenient to hear when bid will be accepted.

Nice!

[bitcoinex]

Total income: -103.88 BTC

Hmmm...

[bitcoinex]

Total income: -103.88 BTC

Hmmm...

What are you referring to in that statement? The total income of your website??! If so, that's sad; you need a better business strategy...  fast!  

This is advertising, this amount casino already paid to players!

Also, on another note, regarding the lost Bitcoins I talked to you a while back about, I can't find the exact acceptor addresses I sent the Bitcoins to, but I do know the withdrawal address I used was 1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv. I hope that helps...  

All acceptors addresses used with this withdrawal address with creation time:

Code:

	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	19QUUtv2TyxxbczwqPWBeP8bzc5h7bjsnW	2011-01-23 01:55:33.594254+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1H5ES6ACsfFHzZUxRHvSCZT5qNgnkGa3kR	2011-01-23 02:41:28.648046+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1JgUxnEyEXz5n7skmhxNeiyFzCPWDLCG4S	2011-01-23 02:41:32.067698+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1JX8Ppp1ngSFsL3fL7xnXjr8vHyrt1wrFS	2011-01-23 02:55:53.804441+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1CEUfrY9VFmmj5YaegEwrbEogmtQ4rR1Rq	2011-01-23 03:08:16.74418+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1DFwb5f1oHUt5Kaacz3nNhr5SLVXRa4CCi	2011-01-23 03:17:41.802131+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1K7MxZSBuubmWc2QpDGpi6zMkf6HVezaAa	2011-01-23 03:22:08.67082+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	16n6mDpdMj25CwkxhAEfjuyPVuGQDU2FHM	2011-01-23 04:11:42.299522+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	16FmHBZHTRE1916BrvZLzWKWqP7EtfySVD	2011-01-23 04:17:38.03376+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	14FBS1Gc8xjE1ifKuHztyEa4fUhPN3WjWc	2011-01-23 04:17:42.120958+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1JeJcfPCBCyfSAg1XSN39bJrCTgPobcx73	2011-01-23 04:19:35.922011+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1GB9gBnk57FgEYaYU1uefPDYBxru1scgJY	2011-01-23 04:36:24.986563+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	13HcyEJorVxqgLCWZvsNXwEzY2ijhDdw9d	2011-01-23 11:26:38.706237+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1AGakRiCUs3CsCGLmmBzgHWsQWbVwBoDh8	2011-01-23 11:34:39.681204+07
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	18y6LBr1qYdgYFwRDMR9ui8kFN6rEQDsfL	2011-01-23 15:27:42.394185+07

prizes (from backup, until January 25):

Code:

	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	3.00
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	1.30
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	2.25
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	3.75
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	3.00
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	8.00
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	5.00
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	2.40
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	4.80
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	2.50
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	2.40
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	4.00
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	2.40
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	4.80
	1MSgUtNsS2Nmfd4NH9ocXMhKRHoCAHEHKv	2.40

Do not use these old addresses - it is deleted from DB because code was rewritten

[bitcoinex]

Maximum bet is increased to 25 BTC!

[MDKing]

hmm am I doing something wrong, I've sent a bet to the acceptor address and it has currently 6 confirmations. Going to the main page, I just see my address in the field and acceptor address and a New Game Hash near the bottom. When I click Ok nothing happens.

[MDKing]

hmm am I doing something wrong, I've sent a bet to the acceptor address and it has currently 6 confirmations. Going to the main page, I just see my address in the field and acceptor address and a New Game Hash near the bottom. When I click Ok nothing happens.

Figured it out, I guess I missed the animation that I missed the target altogether

[dissipate]

A quick question. Could you show some pseudocode of how you handle the bets? Does the acceptor plays any role in the odds?

After creation of a new addresses pair (your address + acceptor address) site generates random secret, shows sha256(secret) to you and waits for your bet. After bet is accepted and game played new random secret generated immediately and site waits bet again.

I haven't played this yet, and I'm curious how this hash verification works.  If I understand correctly, you display the sha256 of some unique data, AKA "secret" before the player places his bet.  Then the player bets whatever amount they like up to 15 BTC, and is shown the ring that was hit, along with the "secret" used.  While it is easy to verify the secret matches the hash, I don't understand is how the "secret" relates to which ring is hit, as that would be the most important part to verify that the game is fair.

It determine coordinates of the hit by getting first 4 bytes from this secret number. For example:

hash of secret: 4d1cb8895e10ed6f6dfc0013049df07f7e9794fd716b3b8e509f6581f2b934e3

After accepting your bet you will see secret and coords of hit:

secret: 0d37cc844521dbfdb92399be793a1bc3
x=0.05162127107652399481 (d37 / ffff)
y=0.79890135042343785763 (cc84 / ffff)

That's all well and good, but how do we know the secret was randomly and fairly generated?

[deMangler]

That's all well and good, but how do we know the secret was randomly and fairly generated?

I would say that it impossible to *know*, randomness and fairness are very often debated in maths universities and school playgrounds and it is a subject that is easily mis-understood (which is mostly why people gamble).
However, I have done a lot of gambling and poker over the years and the successful houses are the ones that are trusted - especially in on-line gambling.
That is why the more respected sites continue to plow so much resources into spotting cheating and robot players, because -in poker and other games of skill fairness is important, not so much with pure random games, where the honesty of the house about the odds is important.
The successful houses know that the easiest way to do this is to actually be fair, take your cut, be open about it, and you will still make a fortune.
As soon as a site is rumored to not be fair they shed players massively - even though such rumors are usually false - at least with the established providers, so it is just not worth it to cheat in providing gambling services - unless you are a very short-term scammer, who wants to make a quick buck and run. Which would be stupid as you will almost certainly make more money in the near to long term by being honest.

I don't know the provider of this site, but I have played it and I do like it.
Just responding to that particular question.
dM

[deMangler]

I did just notice something strange,

I have played quite a few times,
One of my payments to Acceptor address:14XFTVDQrBhw79jYScyiZBx6bp17XHQq6f  - for 10 BTC has not been confirmed after over 3 hours.
Yet other payments have been ok (but not to this address I just doublechecked) - I am even up by a few BTC, but I thought I would let you know in case there is a bug.
Is that address one of your Acceptor addresses? I am sure I cut and pasted it from your site while I was playing.
dM

[bitcoinex]

A quick question. Could you show some pseudocode of how you handle the bets? Does the acceptor plays any role in the odds?

After creation of a new addresses pair (your address + acceptor address) site generates random secret, shows sha256(secret) to you and waits for your bet. After bet is accepted and game played new random secret generated immediately and site waits bet again.

I haven't played this yet, and I'm curious how this hash verification works.  If I understand correctly, you display the sha256 of some unique data, AKA "secret" before the player places his bet.  Then the player bets whatever amount they like up to 15 BTC, and is shown the ring that was hit, along with the "secret" used.  While it is easy to verify the secret matches the hash, I don't understand is how the "secret" relates to which ring is hit, as that would be the most important part to verify that the game is fair.

It determine coordinates of the hit by getting first 4 bytes from this secret number. For example:

hash of secret: 4d1cb8895e10ed6f6dfc0013049df07f7e9794fd716b3b8e509f6581f2b934e3

After accepting your bet you will see secret and coords of hit:

secret: 0d37cc844521dbfdb92399be793a1bc3
x=0.05162127107652399481 (d37 / ffff)
y=0.79890135042343785763 (cc84 / ffff)

That's all well and good, but how do we know the secret was randomly and fairly generated?

https://www.bitcoin.org/smf/index.php?topic=3031.msg42895#msg42895

[bitcoinex]

I did just notice something strange,

I have played quite a few times,
One of my payments to Acceptor address:14XFTVDQrBhw79jYScyiZBx6bp17XHQq6f  - for 10 BTC has not been confirmed after over 3 hours.
Yet other payments have been ok (but not to this address I just doublechecked) - I am even up by a few BTC, but I thought I would let you know in case there is a bug.
Is that address one of your Acceptor addresses?

Yes

I am sure I cut and pasted it from your site while I was playing.
dM

10 BTC payment to this address is unconfirmed

[bitcoinex]

Site was changed. Please clear your cache and cookies.

[deMangler]

I did just notice something strange,

I have played quite a few times,
One of my payments to Acceptor address:14XFTVDQrBhw79jYScyiZBx6bp17XHQq6f  - for 10 BTC has not been confirmed after over 3 hours.
Yet other payments have been ok (but not to this address I just doublechecked) - I am even up by a few BTC, but I thought I would let you know in case there is a bug.
Is that address one of your Acceptor addresses? I am sure I cut and pasted it from your site while I was playing.
dM

The payment has now been accepted and the game played. (I won - yeehaaa!)
It was not a problem with the Probiwon site - it was a network delay.
Thanks.
dM

[Delia]

That's all well and good, but how do we know the secret was randomly and fairly generated?

In theory, it should be possible to generate a provably random number. I don't know whether PIW's customers care enough for it to be worthwhile to implement. The protocol would go like this:

PIW generates a secret.
Secret: 0cd645b8cc7325838b2fa809f308e28ef9463494

PIW sends hash of secret to user.
Hashed-Secret: d18b235bd2c80890a8aee4c564cfbce251633bb3

User records hashed secret.
User generates a nonce.
Nonce: ce61948f0d95be1746017cc327b8d28316055c8f

Secret and Nonce are concatenated and hashed to form the final random result.
Concatenation: 0cd645b8cc7325838b2fa809f308e28ef9463494ce61948f0d95be1746017cc327b8d28316055c8 f
Random: 4f20d70d465fd0743a808048b7a7780e76627d58

[bitcoinex]

Need a scheme that will work in user's browser.