The tournament started. It was noisy. I clicked 'no sounds' in the bottom left of the table. It went quiet. I made it to the final table and it got noisy again. The 'no sounds' thing was still turned on. I tried turning it off and on again, but it didn't help immediately. But eventually I managed somehow to get it to shut up again.
Even when "no sounds" is turned on (and why have a toggle with 'no' in its name? Why not just call it 'sounds' instead, dropping the negative?) there are still sounds if you're slow to act.
|
|
|
My girlfriend tried playing a pmpoker tournament this morning. She got the 5 MB update automatically, but when the game started she saw hundreds of error messages, just like I used to. She tried restarting the client several times, but kept getting the error messages. The ones about being unable to update SQL tables, with JSON debug strings.
I'm waiting for a tournament to start at the moment. The client is just sitting there doing nothing, but it's still using 25% of my CPU. That's not really acceptable for an idle process. What's it doing with all that CPU?
|
|
|
My Casascius Coins website issued a payment address starting with"1Fake" and the customer did not know if he got a real or a test address. Suspicious, he redid his order and paid the new (non-1Fake) address he was issued, then wrote to tell me about it. The 1Fake address was a real address and a genuine coincidence.
Can I buy this address off of you? Why would you want his Fake address, when you could just use a vanitygen to get your own Fake address? Maybe his Fake address was the first one, so has a "firstbits" of 1fake? That's the only reason I could think of.
|
|
|
Thanks for the advice! We've updated Roulette so that it temporarily changes the "Double Bets" button to say "Doubling..." after it's clicked. This should hopefully provide good feedback that it has been clicked.
Yes, that's perfect. It's quick enough not to get in the way, but noticeable enough that I'm not in any doubt as to whether the click worked before. I think before the problem was that although the screen updated when I clicked 'double bets', the button itself didn't change, and that's where my eye was pointing at the time. The parts of the screen that did update were small enough that my peripheral vision didn't notice it. tldr: thanks ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
wow there will be a lot to check, thank you guys ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) hamdi, that satoshitable, i can't understand what's the game, they don't say anything at the site, just ask you to send money? there are 100 spots on the table each spot costs 0.01 BTC to buy when all 100 spots are sold, one is chosen randomly (?) as the winner and gets 0.98 BTC the house keeps 0.02 BTC you get to pick an image and a URL for your spot to link to, so you can advertise anything of your choice, for 0.01 BTC per spot That's about it, as I understand it.
|
|
|
What is the probability of these two events happening directly one after the other?
I think a better question could be what is the probability the drop happened directly before a dividend payment... I really can't think that the drop and reversal were both orchestrated by SD to avoid paying a dividend this month. The reversal means they've just put off this dividend until next month. If SD wanted to screw their investors, they'd arrange for a drop and NO reversal, thereby taking the month's profits for themselves.
|
|
|
Results: 2012-Nov-05 09:15am (up to block 206611)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 35420 | 0 (0.00000) | 34958 | 462 | 238.64 | 0.01 | 37.27 | 238.62 | 0.008 1dice1Qf4 2 0.00003 | 2191 | 0 (0.00000) | 2105 | 86 | 32.84 | 0.00 | 10.45 | 32.83 | 0.005 1dice2pxm 4 0.00006 | 3413 | 0 (0.00000) | 3371 | 42 | 45.97 | 0.03 | 5.65 | 45.93 | 0.086 1dice2vQo 8 0.00012 | 4272 | 2 (0.00047) | 4226 | 44 | 75.69 | 16.07 | 5.65 | 59.61 | 21.240 1dice2WmR 16 0.00024 | 5562 | 1 (0.00018) | 5522 | 39 | 165.05 | 4.30 | 8.40 | 160.75 | 2.607 1dice2xkj 32 0.00049 | 7401 | 3 (0.00041) | 7386 | 12 | 474.38 | 303.40 | 1.29 | 170.97 | 63.958 1dice2zdo 64 0.00098 | 9283 | 8 (0.00086) | 9251 | 24 | 751.03 | 124.64 | 55.64 | 626.38 | 16.597 1dice37Ee 128 0.00195 | 11351 | 20 (0.00177) | 11274 | 57 | 1671.79 | 1277.34 | 48.25 | 394.44 | 76.406 1dice3jkp 256 0.00391 | 12690 | 57 (0.00450) | 12616 | 17 | 1862.15 | 2624.97 | 13.12 | -762.82 | 140.965 1dice4J1m 512 0.00781 | 19487 | 147 (0.00755) | 19327 | 13 | 3578.88 | 3435.67 | 9.35 | 143.21 | 95.998 1dice5wwE 1000 0.01526 | 42984 | 661 (0.01538) | 42310 | 13 | 10409.05 | 10080.42 | 1.80 | 328.63 | 96.843 1dice61SN 1500 0.02289 | 17635 | 423 (0.02400) | 17204 | 8 | 5781.74 | 6016.97 | 15.00 | -235.22 | 104.068 1dice6DPt 2000 0.03052 | 25366 | 807 (0.03182) | 24554 | 5 | 6533.94 | 6117.21 | 9.24 | 416.73 | 93.622 1dice6gJg 3000 0.04578 | 18130 | 841 (0.04641) | 17281 | 8 | 7865.59 | 9151.85 | 24.99 | -1286.26 | 116.353 1dice6GV5 4000 0.06104 | 18142 | 1123 (0.06191) | 17015 | 4 | 5218.05 | 4768.30 | 31.20 | 449.74 | 91.381 1dice6wBx 6000 0.09155 | 24758 | 2339 (0.09455) | 22399 | 20 | 11499.20 | 11737.28 | 7.01 | -238.07 | 102.070 1dice6YgE 8000 0.12207 | 99667 | 12265 (0.12309) | 87378 | 24 | 14606.41 | 13028.51 | 0.00 | 1577.90 | 89.197 1dice7EYz 12000 0.18311 | 24592 | 4581 (0.18641) | 19994 | 17 | 9942.81 | 10201.00 | 14.50 | -258.19 | 102.597 1dice7fUk 16000 0.24414 | 114327 | 27903 (0.24412) | 86398 | 26 | 70332.54 | 68836.16 | 566.79 | 1496.38 | 97.872 1dice7W2A 24000 0.36621 | 81124 | 29827 (0.36790) | 51247 | 50 | 60789.94 | 61428.79 | 212.64 | -638.84 | 101.051 1dice8EMZ 32000 0.48828 | 648336 | 316689 (0.48881) | 331183 | 464 | 380822.62 | 376856.13 | 2923.42 | 3966.49 | 98.958 1dice97EC 32768 0.50000 | 244577 | 121932 (0.49894) | 122451 | 194 | 233953.37 | 229824.74 | 1709.77 | 4128.62 | 98.235 1dice9wcM 48000 0.73242 | 174474 | 128394 (0.73624) | 45998 | 82 | 170363.62 | 168653.13 | 704.58 | 1710.48 | 98.996 1dicec9k7 52000 0.79346 | 17962 | 14270 (0.79503) | 3679 | 13 | 28901.42 | 28886.24 | 1187.00 | 15.17 | 99.947 1dicegEAr 56000 0.85449 | 16791 | 14364 (0.85668) | 2403 | 24 | 28288.82 | 28264.33 | 400.00 | 24.49 | 99.913 1diceDCd2 60000 0.91553 | 9322 | 8548 (0.91766) | 767 | 7 | 23137.49 | 23168.94 | 0.00 | -31.45 | 100.136 1dice9wVt 64000 0.97656 | 8421 | 8106 (0.98005) | 165 | 150 | 17958.12 | 17678.11 | 239.21 | 280.00 | 98.441 -------------------------------------------------------------------------------------------------------------------------------------------- small (bets < 4 BTC) | 1643114 | 665898 | 975531 | 1685 | 406809.15 | 398814.08 | 157.84 | 7995.07 | 98.035 big (bets >= 4 BTC) | 54564 | 27413 | 26931 | 220 | 688492.10 | 683670.57 | 8084.50 | 4821.52 | 99.300 -------------------------------------------------------------------------------------------------------------------------------------------- | 1697678 | 693311 | 1002462 | 1905 | 1095301.26 | 1082484.66 | 8242.34 | 12816.60 | 98.830 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 12816.60044335 BTC (1.170%) Cumulative Fees Paid: 891.41377500 BTC SD Profit after fees: 11925.18666835 BTC (1.089%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 5722319 : SatoshiDice Tx: 3148621 (55.0%) Blockchain MB: 2414.4 : SatoshiDice Tx: 1287.4 (53.3%) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fz5kvp.png&t=663&c=A5Yaj2OBPmvvgw)
|
|
|
Is it possible to write a bot that will monitor for losing bets and then try to cancel it by double spending the money to a wallet controlled by himself?
If he controls a large pool he could direct it to give preference to his cancellation transaction to make sure it propagates faster.
Is this possible in practice? How does SDICE defend against it?
I think a more practical attack would be to always get your pool to attempt to mine a block which includes a transaction that spends your coins to yourself, then as soon as you find a block, hold off publishing it for a few seconds while you place a bet at SD double-spending those same coins on "lessthan 1000". On the rare occasion that your bet wins, you "forget" to publish the block your pool found (maybe claim some other pool beat you to it), and let the winning SD bet stand. The rest of the time you publish your block, which effectively cancels your losing SD bet. I don't know if this happens in practice, or whether SD has anything in place to prevent it working.
|
|
|
The probability of this happening depends on the house edge, and the house's bank.
And don't forget the maximum bet. If they didn't limit the size of your bet, you could get lucky and bankrupt them in a single bet. They've very sensibly been reducing the max bet recently in the face of losses.
|
|
|
When you create a bug, it should be a good one.
They're usually fun to hunt down, but they're not all as cute as this one. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
In roulette, I often hit 'double bets', and then can't be sure whether I clicked properly or not. It feels like there's not enough visual feedback that the click was received. I know the bet amounts double, but they're in a pretty small font. I'm wondering whether changing the button to "doubling" for a fraction of a second would be useful.
+1 more confirmation on placing last bet and doubling buttons Maybe just make the button go bright when it's clicked, and fade back to normal colour over the next second or so. That could perhaps be a default behaviour for all the buttons in all the games if it looks nice.
|
|
|
So roughly what percentage has now been paid back?
In my case, 43.37% of the initial investment, so far.
|
|
|
In roulette, I often hit 'double bets', and then can't be sure whether I clicked properly or not. It feels like there's not enough visual feedback that the click was received. I know the bet amounts double, but they're in a pretty small font. I'm wondering whether changing the button to "doubling" for a fraction of a second would be useful. Or something like that.
This has bugged me before, but it seemed kind of trivial so I never mentioned it. But it continues to annoy me each time I play, so there it is... Treat it as you will...
|
|
|
October Statement
Bad news - October was a bad month for the house. Site lost 2,071 BTC. There is thus no October dividend for S.DICE (technically a dividend of 0.00000001 btc was paid today to mark the date)
Now I REALLY wish I had sold my shares on GLBSE... To clarify, shareholders are not liable for any house losses, they just didn't earn any money last month. It's a little worse than that isn't it? Not only did they not earn any money last month, but as I understand it they won't earn anything from future house profits until the house wins enough to cover last month's losses.
|
|
|
one casino will consistently rake less profit proportionally if their bet range is larger than the other casinos
I still disagree. Expected profit is proportional to house edge (if we ignore progressive jackpots) and nothing to do with bet range. Changing the bet range can change the variance, but the expected profit is always going to be the house edge times the amount wagered. If you have a house edge of 1%, and I wager 1000 BTC, you can expect to keep 10 BTC of it, no matter how I split up the 1000 BTC into smaller bets. I'm sorry I don't have time now to address your post in more detail. What you say about progressive pots is interesting. I suppose it's possible that there are some games out there where the progressive pot is big enough that it's 'worth' playing for the player, mathematically speaking. I know the SatoshiDice progressive game used to be like that, for a very short time until the rules were changed.
|
|
|
In a true 50/50 game, even if you've just seen 10 reds in a row, the next turn is still 50/50. The Monty Hall problem, which you're referring to, isn't and never was 50/50. You picked a door, you have 1/3 probability of having picked the car. The other two doors have a 2/3 probability of having the car behind one of them. Since the host knows where the car is, he can always open one of the remaining two doors and show that it doesn't hide a car. By offering you the choice to switch, he is effectively letting you chose both the other two doors, which doubles your chance of success. As you can see, this is in no way similar to a new independent 50/50 dice roll. me: "I'm thinking of a number between 1 and a million. Guess what it is" you: "665566" me: "I'll give you a clue. the number is either 888888 or 665566. it's nothing else. want to switch?" There's a 1 in a million chance that your first guess was right. There's a 999999 in a million chance that your first guess was wrong, and that my number was 888888. If you switch, you have 999999 times more chance of winning. If you still reason "well, there are two numbers it could be, so it's 50/50" then I don't know how to help you... Does that clear things up? I've tried to explain the Monty Hall problem to people before. Some of them really don't get how it isn't a 50/50 choice even given the above exaggerated situation. I've never been able to understand why; I don't see what it is they can't understand, but would like to.
|
|
|
SD Profit before fees: 12345.29413471 BTC (1.138%)
Small Straight! What odds for such a sequence? ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Given that we're bouncing around between 7500 and 12500, there's 5000 different integer values it can be. So about 5000-to-1 against? But you'd probably be equally amazed if it was exactly 12000, or 12121, or 11111, or 9999, etc. So in that sense it's less amazing. And without further ado: Results: 2012-Nov-04 08:59am (up to block 206455)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 34691 | 0 (0.00000) | 34229 | 462 | 235.51 | 0.01 | 37.27 | 235.49 | 0.008 1dice1Qf4 2 0.00003 | 2164 | 0 (0.00000) | 2078 | 86 | 32.59 | 0.00 | 10.45 | 32.59 | 0.005 1dice2pxm 4 0.00006 | 3388 | 0 (0.00000) | 3346 | 42 | 45.63 | 0.03 | 5.65 | 45.59 | 0.085 1dice2vQo 8 0.00012 | 4002 | 2 (0.00051) | 3956 | 44 | 75.02 | 16.07 | 5.65 | 58.95 | 21.428 1dice2WmR 16 0.00024 | 5542 | 1 (0.00018) | 5502 | 39 | 164.82 | 4.30 | 8.40 | 160.52 | 2.610 1dice2xkj 32 0.00049 | 7126 | 3 (0.00042) | 7111 | 12 | 473.52 | 303.40 | 1.29 | 170.12 | 64.073 1dice2zdo 64 0.00098 | 9022 | 8 (0.00089) | 8990 | 24 | 750.11 | 124.64 | 55.64 | 625.46 | 16.617 1dice37Ee 128 0.00195 | 11089 | 20 (0.00181) | 11012 | 57 | 1670.45 | 1277.33 | 48.25 | 393.11 | 76.467 1dice3jkp 256 0.00391 | 12660 | 57 (0.00451) | 12586 | 17 | 1861.59 | 2624.97 | 13.12 | -763.38 | 141.007 1dice4J1m 512 0.00781 | 19175 | 147 (0.00767) | 19016 | 12 | 3574.74 | 3435.66 | 9.35 | 139.07 | 96.109 1dice5wwE 1000 0.01526 | 42459 | 655 (0.01543) | 41791 | 13 | 10385.82 | 10058.65 | 1.80 | 327.16 | 96.850 1dice61SN 1500 0.02289 | 17614 | 423 (0.02403) | 17183 | 8 | 5781.15 | 6016.96 | 15.00 | -235.81 | 104.079 1dice6DPt 2000 0.03052 | 25337 | 806 (0.03182) | 24527 | 4 | 6533.35 | 6117.18 | 9.24 | 416.17 | 93.630 1dice6gJg 3000 0.04578 | 18093 | 840 (0.04645) | 17245 | 8 | 7863.03 | 9149.71 | 24.99 | -1286.67 | 116.364 1dice6GV5 4000 0.06104 | 18112 | 1123 (0.06202) | 16985 | 4 | 5217.45 | 4768.30 | 31.20 | 449.14 | 91.391 1dice6wBx 6000 0.09155 | 24616 | 2329 (0.09469) | 22267 | 20 | 11487.98 | 11733.97 | 7.01 | -245.99 | 102.141 1dice6YgE 8000 0.12207 | 99216 | 12209 (0.12308) | 86983 | 24 | 14460.32 | 12874.54 | 0.00 | 1585.77 | 89.034 1dice7EYz 12000 0.18311 | 24479 | 4564 (0.18658) | 19898 | 17 | 9932.70 | 10193.12 | 14.50 | -260.42 | 102.622 1dice7fUk 16000 0.24414 | 113211 | 27642 (0.24422) | 85543 | 26 | 69563.33 | 68188.38 | 566.79 | 1374.94 | 98.023 1dice7W2A 24000 0.36621 | 80470 | 29594 (0.36799) | 50826 | 50 | 59415.28 | 60102.10 | 212.64 | -686.82 | 101.156 1dice8EMZ 32000 0.48828 | 646462 | 315764 (0.48880) | 330235 | 463 | 379025.84 | 374900.53 | 2923.41 | 4125.31 | 98.912 1dice97EC 32768 0.50000 | 242107 | 120740 (0.49910) | 121174 | 193 | 231883.68 | 228051.89 | 1709.77 | 3831.79 | 98.348 1dice9wcM 48000 0.73242 | 173652 | 127780 (0.73619) | 45790 | 82 | 169504.89 | 167671.12 | 704.58 | 1833.76 | 98.918 1dicec9k7 52000 0.79346 | 17795 | 14141 (0.79524) | 3641 | 13 | 28854.34 | 28846.46 | 1187.00 | 7.87 | 99.973 1dicegEAr 56000 0.85449 | 16615 | 14219 (0.85703) | 2372 | 24 | 28230.34 | 28205.68 | 400.00 | 24.66 | 99.913 1diceDCd2 60000 0.91553 | 8881 | 8142 (0.91751) | 732 | 7 | 22936.72 | 22971.12 | 0.00 | -34.40 | 100.150 1dice9wVt 64000 0.97656 | 8404 | 8090 (0.98013) | 164 | 150 | 17953.13 | 17673.12 | 239.21 | 280.01 | 98.440 -------------------------------------------------------------------------------------------------------------------------------------------- small (bets < 4 BTC) | 1632142 | 662009 | 968452 | 1681 | 404369.21 | 396442.72 | 157.83 | 7926.48 | 98.040 big (bets >= 4 BTC) | 54240 | 27290 | 26730 | 220 | 683544.25 | 678866.69 | 8084.50 | 4677.56 | 99.316 -------------------------------------------------------------------------------------------------------------------------------------------- | 1686382 | 689299 | 995182 | 1901 | 1087913.46 | 1075309.41 | 8242.34 | 12604.05 | 98.841 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 12604.05221580 BTC (1.159%) Cumulative Fees Paid: 880.08697500 BTC SD Profit after fees: 11723.96524080 BTC (1.078%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 5689945 : SatoshiDice Tx: 3128577 (55.0%) Blockchain MB: 2399.3 : SatoshiDice Tx: 1279.1 (53.3%) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FXW4Mv.png&t=663&c=dInxIgyAiMmpFw)
|
|
|
Game "froze" during the 2-hour freeroll (still is frozen even as I post this) when three afk's were forced to go all-in by themselves with no seated players calling. The board was dealt, but apparently the dealer didn't know who to ship the pot to since none of the afk's had any cards and no one who was present was in the hand at that point.
That's a nice bug. Make a rule that players who aren't present aren't allowed to win any pots, then have a hand where all the players are away. The code loops around the table skipping the away players trying to find a regular player to give the pot to. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Results: 2012-Nov-03 11:36am (up to block 206304)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 34084 | 0 (0.00000) | 33623 | 461 | 234.74 | 0.01 | 37.17 | 234.72 | 0.008 1dice1Qf4 2 0.00003 | 2159 | 0 (0.00000) | 2073 | 86 | 32.47 | 0.00 | 10.45 | 32.47 | 0.005 1dice2pxm 4 0.00006 | 3375 | 0 (0.00000) | 3333 | 42 | 45.13 | 0.03 | 5.65 | 45.09 | 0.086 1dice2vQo 8 0.00012 | 3997 | 2 (0.00051) | 3951 | 44 | 74.97 | 16.07 | 5.65 | 58.89 | 21.445 1dice2WmR 16 0.00024 | 5539 | 1 (0.00018) | 5499 | 39 | 164.63 | 4.30 | 8.40 | 160.33 | 2.613 1dice2xkj 32 0.00049 | 7113 | 3 (0.00042) | 7098 | 12 | 473.41 | 303.40 | 1.29 | 170.01 | 64.088 1dice2zdo 64 0.00098 | 9008 | 8 (0.00089) | 8976 | 24 | 746.86 | 124.63 | 55.64 | 622.23 | 16.688 1dice37Ee 128 0.00195 | 11069 | 19 (0.00173) | 10993 | 57 | 1670.23 | 1274.84 | 48.25 | 395.39 | 76.327 1dice3jkp 256 0.00391 | 12653 | 57 (0.00451) | 12579 | 17 | 1861.54 | 2624.97 | 13.12 | -763.43 | 141.011 1dice4J1m 512 0.00781 | 19142 | 145 (0.00758) | 18985 | 12 | 3574.26 | 3434.41 | 9.35 | 139.84 | 96.087 1dice5wwE 1000 0.01526 | 41424 | 635 (0.01533) | 40776 | 13 | 10165.27 | 9748.42 | 1.80 | 416.85 | 95.899 1dice61SN 1500 0.02289 | 17608 | 422 (0.02398) | 17178 | 8 | 5780.80 | 6004.17 | 15.00 | -223.36 | 103.864 1dice6DPt 2000 0.03052 | 25327 | 806 (0.03183) | 24517 | 4 | 6533.16 | 6117.18 | 9.24 | 415.98 | 93.633 1dice6gJg 3000 0.04578 | 18088 | 840 (0.04646) | 17240 | 8 | 7862.01 | 9149.71 | 24.99 | -1287.69 | 116.379 1dice6GV5 4000 0.06104 | 18091 | 1122 (0.06203) | 16965 | 4 | 5216.69 | 4768.29 | 31.20 | 448.39 | 91.405 1dice6wBx 6000 0.09155 | 24528 | 2325 (0.09487) | 22183 | 20 | 11463.84 | 11733.31 | 7.01 | -269.46 | 102.351 1dice6YgE 8000 0.12207 | 98972 | 12177 (0.12306) | 86771 | 24 | 14432.22 | 12849.31 | 0.00 | 1582.91 | 89.032 1dice7EYz 12000 0.18311 | 24441 | 4557 (0.18658) | 19867 | 17 | 9929.17 | 10192.73 | 14.50 | -263.56 | 102.654 1dice7fUk 16000 0.24414 | 112702 | 27496 (0.24403) | 85180 | 26 | 69093.72 | 67985.85 | 566.79 | 1107.87 | 98.397 1dice7W2A 24000 0.36621 | 80169 | 29484 (0.36800) | 50635 | 50 | 59232.02 | 59842.46 | 212.64 | -610.43 | 101.031 1dice8EMZ 32000 0.48828 | 645878 | 315496 (0.48883) | 329919 | 463 | 378639.60 | 374658.17 | 2923.41 | 3981.43 | 98.948 1dice97EC 32768 0.50000 | 240960 | 120167 (0.49910) | 120600 | 193 | 231488.39 | 227736.60 | 1709.77 | 3751.78 | 98.379 1dice9wcM 48000 0.73242 | 172911 | 127223 (0.73612) | 45607 | 81 | 169149.08 | 167252.42 | 704.58 | 1896.65 | 98.879 1dicec9k7 52000 0.79346 | 17635 | 14010 (0.79503) | 3612 | 13 | 28793.72 | 28778.25 | 1187.00 | 15.47 | 99.946 1dicegEAr 56000 0.85449 | 16466 | 14098 (0.85739) | 2345 | 23 | 27858.00 | 27860.31 | 400.00 | -2.30 | 100.008 1diceDCd2 60000 0.91553 | 8668 | 7949 (0.91779) | 712 | 7 | 22282.08 | 22272.89 | 0.00 | 9.19 | 99.959 1dice9wVt 64000 0.97656 | 8345 | 8032 (0.98011) | 163 | 150 | 17949.37 | 17669.37 | 239.21 | 279.99 | 98.440 -------------------------------------------------------------------------------------------------------------------------------------------- small (bets < 4 BTC) | 1626230 | 659851 | 964701 | 1678 | 403375.90 | 395340.12 | 157.73 | 8035.77 | 98.008 big (bets >= 4 BTC) | 54122 | 27223 | 26679 | 220 | 681371.61 | 677062.09 | 8084.50 | 4309.51 | 99.368 -------------------------------------------------------------------------------------------------------------------------------------------- | 1680352 | 687074 | 991380 | 1898 | 1084747.51 | 1072402.21 | 8242.24 | 12345.29 | 98.862 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 12345.29413471 BTC (1.138%) Cumulative Fees Paid: 874.04977500 BTC SD Profit after fees: 11471.24435971 BTC (1.058%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 5669272 : SatoshiDice Tx: 3118057 (55.0%) Blockchain MB: 2390.1 : SatoshiDice Tx: 1274.7 (53.3%) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Frw0wo.png&t=663&c=5b_ieJGgSf0Uww)
|
|
|
|