No, sir, that was me funding the pot a bit which is why there is no listed transaction for it on the satoshidice web page. Ahhh. Very good...
|
|
|
As for the progressives, I thought that it was too confusing to have the three.
It looks like it's still confusing. Someone just bet 100 BTC when the pot was 42.1294. If they win, they'll get 92.1294 BTC back (half of their bet goes into the pot they can win), for a loss of around 8 BTC. And if they lose, they won't get anything back. It's a lose/lose proposition.
|
|
|
Why was the "under 64000" bet retired? It was one of the more profitable bets for the house.
And what happened to the progressive bets? Two of the three have disappeared from the site overnight, including the one with the 98% RTP.
|
|
|
It looks like those are all pending now.
Yes. Almost caught up now. The following are still outstanding: 728e71fa953478cdedddc7e7eb7fe971c04f2c09baf01a01d37ca50ba184d843 2 187088 14:00:50 Jul-01-12 6e38d52d19270f7e474ad8bc0ffdc750bc601d19e05446c34cf2d960146d09e2 1 187102 15:52:06 Jul-01-12 aa95e33dcd43c3828c929dcae22f56ad3a4ec7ab813174a8112d97cff6b38011 1 187102 15:52:06 Jul-01-12 3eb016af4edbb4e53372fbd870bb28e0113ca3e865d320f0c790c4217384d7e3 1 187108 17:22:12 Jul-01-12 692755a16ac619706aebeef61d71297ef9c99277a706a585cdfcb27c7ee80382 1 187122 20:03:43 Jul-01-12 0032dad95af4f2f7a3838f51a35c852bbd6096b21f1fe73783562fe9d7823668 8 187124 20:20:27 Jul-01-12 0032dad95af4f2f7a3838f51a35c852bbd6096b21f1fe73783562fe9d7823668 4 187124 20:20:27 Jul-01-12 56bde8eb17b73859b622390a9b99df1acf1028bc059939ba2ecb5b7fc2f3236f 1 187124 20:20:27 Jul-01-12 82dc968eedb8706d8190b7a3849922134a57726d6c5eb3ecfd6e8864a6755272 17 187124 20:20:27 Jul-01-12 a16a360065317d2f7ef0c908f1ae89afbf83978efd01bcb9ab83d5849320a7a7 13 187124 20:20:27 Jul-01-12 76b24949282b27eff1e23f43a2cb013b091e8ccc50530a1fef345e303c376203 9 187131 21:33:50 Jul-01-12 0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 3 187135 22:11:05 Jul-01-12 0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 9 187135 22:11:05 Jul-01-12 7ba07cf788097760a83152cc7fbd9d2e8a8464613d9b03037527e3e8f3938728 9 187135 22:11:05 Jul-01-12 06b032a68ac001b2a22c4b75e9e980cc61f51e85a91036f8d42b91f5196b6c9c 6 187135 22:11:05 Jul-01-12 0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 4 187135 22:11:05 Jul-01-12 b2f1078df67bbd11161107f9ee6e419cac68c9a724c2a7b170cd172e33da0aed 1 187140 22:42:16 Jul-01-12 85302fbce2cb97d8bf1f888032cb5238dfb379094982bbeb26cb1420e0bb035d 1 187150 00:43:25 Jul-02-12 3fdadb9c8c052348183c2e229953cfcd1d072689c0122c7bf35b8f7370812d7d 0 187156 02:01:59 Jul-02-12 1c8b0bc4b58b2925a6c674b2a1c3a2e5dedd4b5c129f3c050d6771025f665aed 1 187174 03:59:22 Jul-02-12 19a08e829dd7547eae74cd9093810de267231125ee565728b6f4fee7d35aa201 0 187186 05:07:16 Jul-02-12 033a588bcdee73c23a646856436068cfef811e3a0a38b5f8c04fc878be82281a 1 187189 05:30:35 Jul-02-12 401b92e4f20ef50f8024e58ad0d9e78ace486be48e08e98a9d5540af6b3be28a 0 187189 05:30:35 Jul-02-12 b70bc1680b32280d5cf85f07f371aa13a90c21e21e90e3b4d279c8fa63974db7 1 187199 06:18:57 Jul-02-12 2e44b11c4fdf49fbf1808dac96fba90c10d13da094c7882c210f6c79b2d53794 1 187199 06:18:57 Jul-02-12 8353b7513d2f925f3b725304ba5a11b3cdf5972941fd3dc525dc64aac57298f0 1 187199 06:18:57 Jul-02-12 66051fe4fe6d720b70b4390ac49df2126abfd11bc9cf36283593b81d0b623bec 1 187220 08:53:50 Jul-02-12 Are they on your radar too? I checked the first 3 and they don't have unconfirmed payments - it looks like you didn't process them yet.
|
|
|
Yeah, I think I worked out the issue here. Basically transactions were being saved into the wallet db and not the tracking/bet db so I didn't see that they were not being confirmed. I've corrected some ordering there so it should always be left in a state such that if anything is wrong it will be clear in my reports.
These are still pending and more than 2 days old: 2b7f6c3bf01743d298950143e7a65ba675a5328b734308555e41cf92dc43e00c 1 186466 03:55:03 Jun-27-12 45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12 23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12 12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12 16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12 2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12 10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12 0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12 3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12 02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12 440a0b3b6554f03f2b9d3e160e418ec8c7903ae5f6d8844676cdef774c6e4093 0 186763 05:41:43 Jun-29-12 298df14aeab863473212cf017bb1c54ecd79ddbd0b5e37a68078310524c6b427 0 186852 20:55:59 Jun-29-12
|
|
|
Results: 2012-Jul-02 01:23pm (up to block 187242)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Profit | RTP ----------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 6250 | 0 (0.00000) | 5992 | 257 | 21.71 | 0.01 | 21.69 | 0.088 1dice1Qf4 2 0.00003 | 888 | 0 (0.00000) | 821 | 67 | 7.15 | 0.00 | 7.14 | 0.025 1dice2pxm 4 0.00006 | 1397 | 0 (0.00000) | 1367 | 30 | 12.15 | 0.00 | 12.15 | 0.046 1dice2vQo 8 0.00012 | 1102 | 0 (0.00000) | 1064 | 38 | 15.19 | 0.00 | 15.18 | 0.031 1dice2WmR 16 0.00024 | 1358 | 0 (0.00000) | 1330 | 28 | 21.01 | 0.01 | 20.99 | 0.076 1dice2xkj 32 0.00049 | 3092 | 1 (0.00032) | 3080 | 11 | 89.89 | 100.38 | -10.48 | 111.666 1dice2zdo 64 0.00098 | 4460 | 5 (0.00113) | 4438 | 17 | 176.73 | 110.74 | 65.99 | 62.661 1dice37Ee 128 0.00195 | 5901 | 12 (0.00205) | 5840 | 47 | 1197.34 | 1142.16 | 55.17 | 95.392 1dice3jkp 256 0.00391 | 4399 | 20 (0.00456) | 4366 | 12 | 458.86 | 330.67 | 128.18 | 72.064 1dice4J1m 512 0.00781 | 5462 | 32 (0.00587) | 5424 | 5 | 748.28 | 330.60 | 417.67 | 44.182 1dice5wwE 1000 0.01526 | 6656 | 93 (0.01398) | 6558 | 2 | 1377.12 | 711.48 | 665.64 | 51.664 1dice61SN 1500 0.02289 | 5172 | 108 (0.02091) | 5057 | 6 | 1913.72 | 2135.76 | -222.03 | 111.602 1dice6DPt 2000 0.03052 | 5628 | 174 (0.03096) | 5447 | 3 | 1786.52 | 1635.04 | 151.47 | 91.521 1dice6gJg 3000 0.04578 | 5518 | 277 (0.05028) | 5232 | 7 | 3791.62 | 4916.50 | -1124.87 | 129.667 1dice6GV5 4000 0.06104 | 5586 | 344 (0.06163) | 5238 | 3 | 1619.49 | 1429.16 | 190.33 | 88.247 1dice6wBx 6000 0.09155 | 9550 | 893 (0.09358) | 8650 | 4 | 6146.27 | 6745.93 | -599.66 | 109.756 1dice6YgE 8000 0.12207 | 10612 | 1297 (0.12232) | 9306 | 0 | 2952.77 | 2544.50 | 408.26 | 86.173 1dice7EYz 12000 0.18311 | 14629 | 2789 (0.19087) | 11823 | 5 | 5962.82 | 6312.56 | -349.74 | 105.865 1dice7fUk 16000 0.24414 | 35975 | 8723 (0.24258) | 27236 | 6 | 9011.21 | 8694.07 | 317.13 | 96.481 1dice7W2A 24000 0.36621 | 24066 | 8887 (0.36977) | 15147 | 30 | 10854.86 | 11103.44 | -248.57 | 102.290 1dice8EMZ 32000 0.48828 | 272702 | 132734 (0.48701) | 139817 | 121 | 80984.06 | 82596.47 | -1612.40 | 101.991 1dice97EC 32768 0.50000 | 106458 | 53176 (0.49984) | 53210 | 64 | 36476.09 | 35805.28 | 670.81 | 98.161 1dice9wcM 48000 0.73242 | 66349 | 48731 (0.73487) | 17581 | 32 | 38074.31 | 36695.62 | 1378.68 | 96.379 1dice9wVt 64000 0.97656 | 5694 | 4598 (0.97457) | 120 | 975 | 4901.49 | 4709.70 | 191.79 | 96.087 ----------------------------------------------------------------------------------------------------------------------------------------- | 608904 | -----------------------------------------------------------------------------------------------------------------------------------------
Cumulative Wagers: 212865.75014757 BTC Cumulative Rewards: 212275.45778249 BTC Cumulative Fees Paid: 306.38627500 BTC Cumulative Unreturned: 39.71568201 BTC ---- SD Profit on Completed Bets : 244.19040807 BTC ---- Since Satoshi Dice started, there have been: Blockchain Tx: 1761683 : SatoshiDice Tx: 1136393 (64.5%) Blockchain MB: 746.3 : SatoshiDice Tx: 462.7 (62.0%)
|
|
|
I assume the next major release will be 0.7, we'll be running out of 0.x headroom pretty soon After 0.9 come 0.10 and 0.11; they're not decimals. When a period is used to separate sequences, it does not represent a decimal point, and the sequences do not have positional significance. An identifier of 2.5, for instance, is not "two and a half" or "half way to version three"
Most free software packages treat numbers as a continuous stream, therefore a free software or open source product may have version numbers 1.7.0, 1.8.0, 1.8.1, 1.9.0, 1.10.0, 1.11.0, 1.11.1, 1.11.2, etc.
|
|
|
If it weren't for the big bets, SatoshiDice would be almost 4000 BTC up by now, but instead they're 500 BTC down.
Sounds like SatoshiDice is lazy and use big amounts for their statistics-skewing transactions masqueraded as real bets.</AlexJones> It occurred to me that it was their way of taking a profit. But if that's the case, why have they lowered the max bet and kept it low? It doesn't make any sense to be decreasing the bet sizes as the profits grow.
|
|
|
Almost all bets eventually get paid. It's not unusual for different bets in a single transaction to be processed at different times. I've no idea why that happens.
|
|
|
I was dealt two aces against a dealer jack. I split them, and the two hands were blackjack and ace-ace. I was not given an opportunity to split the second ace-ace and was forced to accept a value of 12
We discussed this a couple of days ago. I thought the rules had changed since then to allow hitting split aces, but I guess not: I think I will change the rules to allow for both hitting and re-splitting of split aces, which is more fun, and it'll bring the housed edge down to a meager 0.398%.
|
|
|
It's still in plaintext like you said, EXCEPT for the hole cards, which are now hashed with sha256 using the private session key the server gives out at the start of the connection. Was very easy to figure out what the client was doing though. As I mentioned, this was implemented with the last client update they did back when I was actively playing.
So how does the client know what its cards are if they are sha256 hashed with the session key. sha256 is a one-way hash. Does it have to brute-force them? Seems unlikely, especially for omaha where you have 4 cards, not just 2.
|
|
|
I noticed a few months ago that the flash client communicates in plain text with the server, but didn't do anything with it. I think at the time it was sending my hole cards in the clear too, but maybe that's changed now.
I don't understand what you're talking about when you say you could use sha256 though.
|
|
|
Is satoshi dice currently choking on sendmany transactions?
I have a tx where a bet doesn't seem to have gotten into your db: 9ebfdbeb116616e748bc8654131b90ab21a7125ba376935a0984939159cd6f0f
No, it just chokes apparently at random on a very small percentage of transactions. I don't know what causes it - I occasionally post a list of outstanding transactions, and fireduck sometimes fixes them. I posted a list yesterday, but they're still not fixed.
|
|
|
Wouldn't this still be traceable back to you?
Yes. Everyone can see "address A bet X BTC and asked for their winnings to be sent to address B". Not ideal for money laundering!
|
|
|
You mean Satoshi lose more money with big bets ? is the graph now right ?
He lose alote of money with big bets ans makes money with small bets ? is this right so ?
Yes, that's what I mean. The graph is right, but a little out of date. Here's an up-to-date one; Results: 2012-Jul-01 02:44pm (up to block 187092)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Profit | RTP ----------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 6201 | 0 (0.00000) | 5943 | 256 | 21.36 | 0.01 | 21.34 | 0.090 1dice1Qf4 2 0.00003 | 882 | 0 (0.00000) | 814 | 67 | 7.12 | 0.00 | 7.12 | 0.025 1dice2pxm 4 0.00006 | 1382 | 0 (0.00000) | 1351 | 30 | 11.99 | 0.00 | 11.99 | 0.047 1dice2vQo 8 0.00012 | 1092 | 0 (0.00000) | 1055 | 36 | 15.05 | 0.00 | 15.05 | 0.031 1dice2WmR 16 0.00024 | 1349 | 0 (0.00000) | 1321 | 27 | 20.65 | 0.01 | 20.64 | 0.075 1dice2xkj 32 0.00049 | 3075 | 1 (0.00033) | 3062 | 11 | 89.10 | 100.38 | -11.27 | 112.650 1dice2zdo 64 0.00098 | 4438 | 5 (0.00113) | 4415 | 17 | 175.99 | 110.74 | 65.24 | 62.927 1dice37Ee 128 0.00195 | 5843 | 12 (0.00206) | 5803 | 26 | 1176.62 | 1142.07 | 34.54 | 97.064 1dice3jkp 256 0.00391 | 4369 | 20 (0.00459) | 4335 | 12 | 458.47 | 330.67 | 127.80 | 72.125 1dice4J1m 512 0.00781 | 5402 | 32 (0.00593) | 5364 | 5 | 723.43 | 330.50 | 392.93 | 45.685 1dice5wwE 1000 0.01526 | 6570 | 92 (0.01402) | 6472 | 2 | 1306.15 | 695.34 | 610.80 | 53.236 1dice61SN 1500 0.02289 | 5088 | 108 (0.02125) | 4974 | 6 | 1598.74 | 2134.22 | -535.47 | 133.494 1dice6DPt 2000 0.03052 | 5583 | 173 (0.03103) | 5403 | 3 | 1750.55 | 1619.07 | 131.48 | 92.489 1dice6gJg 3000 0.04578 | 5445 | 275 (0.05057) | 5163 | 6 | 3608.20 | 4704.79 | -1096.58 | 130.392 1dice6GV5 4000 0.06104 | 5515 | 340 (0.06171) | 5170 | 3 | 1602.86 | 1402.21 | 200.65 | 87.481 1dice6wBx 6000 0.09155 | 9358 | 879 (0.09400) | 8472 | 4 | 5961.81 | 6560.49 | -598.68 | 110.042 1dice6YgE 8000 0.12207 | 10325 | 1259 (0.12204) | 9057 | 0 | 2891.30 | 2498.25 | 393.04 | 86.406 1dice7EYz 12000 0.18311 | 14500 | 2768 (0.19109) | 11717 | 5 | 5905.06 | 6230.00 | -324.94 | 105.503 1dice7fUk 16000 0.24414 | 35833 | 8688 (0.24253) | 27134 | 6 | 8967.36 | 8620.49 | 346.86 | 96.132 1dice7W2A 24000 0.36621 | 23916 | 8841 (0.37015) | 15044 | 30 | 10783.37 | 11044.96 | -261.59 | 102.426 1dice8EMZ 32000 0.48828 | 270535 | 131680 (0.48700) | 138711 | 120 | 80495.15 | 82188.83 | -1693.67 | 102.104 1dice97EC 32768 0.50000 | 105990 | 52945 (0.49986) | 52975 | 61 | 36154.48 | 35516.80 | 637.68 | 98.236 1dice9wcM 48000 0.73242 | 66124 | 48556 (0.73470) | 17534 | 31 | 38033.84 | 36657.31 | 1376.52 | 96.381 1dice9wVt 64000 0.97656 | 5692 | 4598 (0.97457) | 120 | 973 | 4901.49 | 4709.70 | 191.79 | 96.087 ----------------------------------------------------------------------------------------------------------------------------------------- | 604507 | -----------------------------------------------------------------------------------------------------------------------------------------
Cumulative Wagers: 210867.93922406 BTC Cumulative Rewards: 210773.98925246 BTC Cumulative Fees Paid: 304.16610000 BTC Cumulative Unreturned: 30.63706275 BTC ---- SD Profit on Completed Bets : -240.85319115 BTC ---- Since Satoshi Dice started, there have been: Blockchain Tx: 1737546 : SatoshiDice Tx: 1128216 (64.9%) Blockchain MB: 736.9 : SatoshiDice Tx: 459.5 (62.4%)
|
|
|
I really don't care either way, this was just a little toying with gambling and free spare change, I'm just curious what happened to that .02 that seems to have vanished and what implications that would have on larger gambles. As shown by my wallet, it obviously wasn't in that payment.
The 0.05240186 payment is your winnings from this bet. You bet 0.04 on "lessthan 48000" and won: http://www.satoshidice.com/lookup.php?tx=5df14eb7a279fb557dea1afae70cdcca23bfe6821c55ae9553dbc18904f2640aYour winnings of 0.0787528 appeared in the same block. Look at the 'transactions' tab. Do you see it there? The 'overview' tab that you showed us only shows the 3 most recent transactions.
|
|
|
Here's an interesting graph: It splits the profit/loss into that caused by bets under 4 BTC and that caused by bets of 4 BTC or more. There's a marked difference. Small bets are very profitable. Big bets are very expensive. If it weren't for the big bets, SatoshiDice would be almost 4000 BTC up by now, but instead they're 500 BTC down. Everything was looking fine until the first week of June. Since then there's been a big difference between the profitability of "big" and "small" bets. Edit: fixed the graph. the >= and < labels were the wrong way around
|
|
|
That got missed, maybe it wasn't old enough when I ran my program. I was basically deleting transactions that haven't confirmed in over two days. It is handled now.
It looks like you're still missing bets: transaction id out block timestamp ---------------------------------------------------------------- --- ------ ------------------ 2b7f6c3bf01743d298950143e7a65ba675a5328b734308555e41cf92dc43e00c 1 186466 03:55:03 Jun-27-12 45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12 23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12 12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12 16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12 2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12 10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12 0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12 3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12 02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12 It doesn't seem to be just that the payment isn't confirmed, because the bets aren't in your database at all as far as I can see.
|
|
|
You, um ... , you don't get out much into the real world nowadays anymore, do you?
I think a pretty small percentage of the population would know what 6.2e-07 ฿ means.
|
|
|
I don't know if the hashing on the customer side is really necessary, but it's a nice touch, and you implemented it well.
Provable fairness is a nice feature. Most people won't ever check it, and those that do won't check many hands, but it's reassuring to have it there. Now you just need a full-time customer service staff to handle Dooglus... and watch out, he wins more than he loses That's funny. I'm not doing too well so far. I blame it on the positive house edge - they shuffle the deck before every hand, can you believe it???
|
|
|
|