I'll be betting 0.08 + 0.09 + 0.10 + 0.11 + 0.12 = 0.50 BTC. 3 bets today, and 2 tomorrow.
0.08 BTC: #190 30d33b08fedc8d4f5f987838509a0a1efae33b21b2f16bda50d9785d0d371855
0.09 BTC: #192 69e62c58b3f6a9810c67c40c44ceef2e21d6c5a5d56d470b1179b63674eaa5e3
0.10 BTC: #193 3fb5024c93a5a3b8d3b2c3bd4bfb70c257b7ace0263ee1698b2324c7cf79f49e
Probably best not to ask what happened with #191; it's a little embarrassing...
My bets are currently hovering one row up from the bottom - presumably awaiting confirmation before I get to see if I won or not:
Edit: but the title of this thread says it's a "zero conf" game. And one of my bets is confirmed now anyway but I still don't see if I won or not. The site could use a 'FAQ' page which talks about how many confirmations are required.
Edit2: my 3 bets now all have at least 12 confirmations, but they're still 'pending' on the site. I wanted to check the result for myself, since the daily secret is now revealed, but the description is a little unclear:
Quote
Then the 1st 2 bytes are used. If the bit is 1 the ball goes left if it is 0 it goes right.
The first 2 bytes have 16 bits in total, but there are only 14 decisions to make so it would be better to be explicit about which bits are used and in which order. The Python script does so, but maybe say it in English too.
I used bitaddress to check that the published secret does correspond to the previously published public key:
Turns out all 3 of my bets lost (I modified the Python script to take command line arguments, and to tell me the payout):
Quote
# 190
$ ./path.py 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b 30d33b08fedc8d4f5f987838509a0a1efae33b21b2f16bda50d9785d0d371855
For Private Key : 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b
and Transaction : 30d33b08fedc8d4f5f987838509a0a1efae33b21b2f16bda50d9785d0d371855
the path taken is: rlrllrlrlrrrrl
payout is : 0
# 192
$ ./path.py 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b 69e62c58b3f6a9810c67c40c44ceef2e21d6c5a5d56d470b1179b63674eaa5e3
For Private Key : 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b
and Transaction : 69e62c58b3f6a9810c67c40c44ceef2e21d6c5a5d56d470b1179b63674eaa5e3
the path taken is: lrlrlrrlllrrll
payout is : 0
# 193
$ ./path.py 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b 3fb5024c93a5a3b8d3b2c3bd4bfb70c257b7ace0263ee1698b2324c7cf79f49e
For Private Key : 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b
and Transaction : 3fb5024c93a5a3b8d3b2c3bd4bfb70c257b7ace0263ee1698b2324c7cf79f49e
the path taken is: rrrlrlrrrrrllr
payout is : 0
$ ./path.py 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b 30d33b08fedc8d4f5f987838509a0a1efae33b21b2f16bda50d9785d0d371855
For Private Key : 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b
and Transaction : 30d33b08fedc8d4f5f987838509a0a1efae33b21b2f16bda50d9785d0d371855
the path taken is: rlrllrlrlrrrrl
payout is : 0
# 192
$ ./path.py 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b 69e62c58b3f6a9810c67c40c44ceef2e21d6c5a5d56d470b1179b63674eaa5e3
For Private Key : 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b
and Transaction : 69e62c58b3f6a9810c67c40c44ceef2e21d6c5a5d56d470b1179b63674eaa5e3
the path taken is: lrlrlrrlllrrll
payout is : 0
# 193
$ ./path.py 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b 3fb5024c93a5a3b8d3b2c3bd4bfb70c257b7ace0263ee1698b2324c7cf79f49e
For Private Key : 59b54e617bd0f7501cb4b635b3f2fd7e9196efb89a67ba32d370b41293135a7b
and Transaction : 3fb5024c93a5a3b8d3b2c3bd4bfb70c257b7ace0263ee1698b2324c7cf79f49e
the path taken is: rrrlrlrrrrrllr
payout is : 0
This provably sucks!
