She asked for "facts and evidence". Not vague hand-waving. "Red flags"? Come on...
I have no agenda against your site at all. I see you doing things that are likely to put people off playing there, including being too heavy-handed with your suspicions about friends colluding. You've said before that you thought Doug and I were the same person because we both had "British Columbia IPs". The province of British Columbia is a big place, bigger than France, hence my silly "I hope you're not in the same province as your girlfriend" quip.
|
|
|
"-A" could also give you away. E.g. you'll have "G-Sense Error Rate" high then its a proof of a dropped laptop. Same things with "Power On Hours", "Power Cycles" and "Temperature Celcius" if you were fiddling with the computer.
I don't know how to read the information. What does this tell you? I really don't think the computer has ever been dropped or even bumped. chris@chris:~$ sudo smartctl -A /dev/sda smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-25-generic-pae] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1064 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 100 5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 837 10 Spin_Retry_Count 0x0033 102 100 030 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 94 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 15 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 823 194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 42 (Min/Max 20/51) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 16 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 2 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0 222 Loaded_Hours 0x0032 099 099 000 Old_age Always - 625 223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0 224 Load_Friction 0x0022 100 100 000 Old_age Always - 0 226 Load-in_Time 0x0026 100 100 000 Old_age Always - 256 240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0 If that's saying I've turned the computer on and off 94 times, then I find that hard to believe. I would expect something less than 20 to be the true figure - possibly even less than 10. Unless it's counting when I close the lid and it goes into a suspended state, in which case I can quite believe the number. I often have uptimes of over a week, and never reboot into Windows. Edit: weird how bold spaces are narrower than regular spaces, messing up the table layout
|
|
|
smartmontools are the best friend of smart disk drive users.
Do you think it's worth printing out some smartmontools output to put in the package with the laptop when I send it back? What's a good smartctl command to get a reasonable amount of output for printing? What I don't want is to wait 10 days and get the laptop back with a note saying "looks fine to us". The 'long' test just finished: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 00% 836 153439088 # 2 Short offline Completed without error 00% 834 - Edit: I notice that the '-H' (health) check tells me it 'passed': $ sudo smartctl -H /dev/sda smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-25-generic-pae] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED
|
|
|
To post an attacking rant like you did is simply unprofessional and offensive.
In my experience running bars and poker games IRL, it's better to do this out in the open. You & petrescuerz have walked with $715.49, a majority of that in bonuses and free prizes. You've been paid out. This is not a mind-bending amount of money we're talking about, but you certainly can't say we haven't been a nice spot for you to play at. We are simply asking you to leave now because we don't like how your various accounts are set up, and how they interact. I'm not gonna get back into the details of the things we think you did. We paid you, we're square, now go somewhere else. I'm not disputing that you paid us. Thanks a lot for the free money, and it has been mostly a very pleasant experience playing at your casino and interacting with the other players. What I could have done without was the string of false accusations from the CEO. My friends and I aren't the only targets of your paranoia; I've been at a poker table before watched as you accused JoeyMajik of being an undercover cop come to catch you in the act of letting USA players gamble, and the Portuguese players have also had their own share of trouble for daring to want to play poker together. I understand you need to be cautious in your position because people will try to scam you but you can't go throwing your weight around willy nilly like you do, or you'll scare all your players away. And if you do feel you have reasonable doubt about people's identities, instead of "you're a liar, your girlfriend is imaginary and you have multiple personalities", it might be better to say "could you and your girlfriend please send me copies of your ID documents?" Or carry on as you are. Makes no difference to me now.
|
|
|
perhaps I'm best off returning it for replacement.
Comments?
If you like the laptop then keep it and use it. Repair the bad blocks, monitor for any new bad blocks and get the replacement drive under warranty if you get any more bad blocks without a reason, like jostling. What is worth more: a spare hard drive lying on the shelf or your time wasted with no laptop? The laptop manufacturer seems to think that the warranty only lasts for 90 days. I didn't buy an extended warranty. I can manage without the laptop for the 7 to 10 days they claim the repair will take. Thanks for your input though. Maybe if I hadn't just spent 24 hours backing up the hard drive and arrange for a courier to pick it up I would consider just remapping the bad sectors.
|
|
|
Here Dooglus. I unlocked the thread. Beat your brains out. But I'm done responding to this.
Thanks. I tried replying before when I noticed the thread was unlocked, but you locked it again before I could finish typing. I ended up posting my reply here, but now I'll put it here where it belongs. We do not know, and cannot know, the full truth about the dooglus / petrescuerz situation. We do not believe that petrescuerz is an imaginary person, but we also don't believe that she has always been in control of that account. Dooglus has asked me to retract the post calling him a liar, and her imaginary. I'll say that she is not imaginary. Whether she's the person who was playing on his computer is impossible to know.
So to be clear you're not retracting the part about me being a liar? Beyond that, I'm reluctant to alter the history of this thread and would prefer it to be removed completely, as he and I have both asked the mods to do.
I have asked for no such thing. Where do you get this stuff from? We have asked him to leave, and he's elected to take his friends, referrals, et. al. with him and send a lot of emails and chats to people criticizing me, which is his right.
I didn't elect to take them with me, you asked me to. Remember the following? From now on, I'd prefer that you (plural) don't play. And if petrescuerz cashes out and you guys take your business elsewhere, that would be better for everybody. I don't want you or your friends around anymore.
I contacted my friends, giving them a link to this thread so they could see what was going on. I agree that it makes you look bad, but I don't think any of that is my doing. I apologize for losing my temper in this thread. This is not however an invitation to keep trolling this thread, or an apology for what I've written here. Nor is this an invitation for anyone to come back to the site. He is simply not invited anymore, and we won't change our mind on the subject.
Dooglus would like this thread removed. I have no objection to that, and I have asked the moderators to do so if that's within their power.
I don't want the thread removed. I want it to stand as a warning to potential customers to the type of treatment they can expect to receive from your company. It's quite incredible how badly you have managed this. If you had any doubts about the identity of the players at your site you should have spoken to them. I'm sure they would have been happy to video chat with you, send you copies of passports, driving licenses, or whatever. To post an attacking rant like you did is simply unprofessional and offensive.
|
|
|
I'm totally fine with letting that thread stand if you don't want it removed.
Are you done now?
I would prefer to be able to refute your claims in the thread in which you made them. I also wish you would tell the truth, rather than this talk of me wanting threads deleted and electing to take my friends with me.
|
|
|
I had an issue with a 6 week old laptop a couple of days ago where it just hung while running Linux, and after rebooting it, the blockchain files were corrupted. I asked for advice on the ##linux freenode IRC channel and got the following: 20:43 < dooglus> I bought a new laptop a few weeks ago, and the hard drive seems to be playing up already: 20:43 < dooglus> Jul 10 11:40:09 chris smartd[6083]: Device: /dev/sda [SAT], 16 Currently unreadable (pending) sectors 20:44 < dooglus> is that to be expected, and it will mark the bad sectors and work around them, or should I take it back for repair? 20:44 < bjonnh> dooglus: take it back now 20:44 < bjonnh> dooglus: a failing harddrive on its early life is always worse two month later 20:45 < dooglus> I see 20:45 < bjonnh> dooglus: most of the time dead 20:45 < MooingLemur> dooglus: currently pending sectors means it couldn't read them, but would remap them on the next write. If they're happening now, exchange it. Don't trust it at all. 20:46 < KsM> start backing up 20:46 < MooingLemur> dooglus: sometimes it's worth going directly to the HDD manufacturer and just getting an advance RMA rather than trying to deal with the laptop manufacturer 20:46 < dooglus> is there any way I can get an identifier for the hdd so I can see whether they really replace the hdd or just reformat it? 20:47 < MooingLemur> dooglus: smarctl -i /dev/sda 20:47 < MooingLemur> you'll get a serial from that Is that reasonable advice? I didn't know about the 'badblocks' command to remap bad blocks, but if it's the case that bad disks tend to get worse quickly perhaps I'm best off returning it for replacement. I ran the 'short' SMART test mentioned above, and that passed: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 834 - and the 'long' test is currently running. I bought the laptop 5.5 weeks ago, and according to the test result above, it's been on for 834 hours (4.9 weeks). So it does look like it was new when I got it, and it worked flawlessly until it didn't. Comments?
|
|
|
The thread I'm replying to was temporarily unlocked then relocked again before I could reply, so I'm posting here instead. I hope that's acceptable. If the original thread is ever unlocked I'll move this post there. We do not know, and cannot know, the full truth about the dooglus / petrescuerz situation. We do not believe that petrescuerz is an imaginary person, but we also don't believe that she has always been in control of that account. Dooglus has asked me to retract the post calling him a liar, and her imaginary. I'll say that she is not imaginary. Whether she's the person who was playing on his computer is impossible to know.
So to be clear you're not retracting the part about me being a liar? Beyond that, I'm reluctant to alter the history of this thread and would prefer it to be removed completely, as he and I have both asked the mods to do.
I have asked for no such thing. Where do you get this stuff from? We have asked him to leave, and he's elected to take his friends, referrals, et. al. with him and send a lot of emails and chats to people criticizing me, which is his right.
I didn't elect to take them with me, you asked me to. Remember the following? From now on, I'd prefer that you (plural) don't play. And if petrescuerz cashes out and you guys take your business elsewhere, that would be better for everybody. I don't want you or your friends around anymore.
I contacted my friends, giving them a link to this thread so they could see what was going on. I agree that it makes you look bad, but I don't think any of that is my doing. I apologize for losing my temper in this thread. This is not however an invitation to keep trolling this thread, or an apology for what I've written here. Nor is this an invitation for anyone to come back to the site. He is simply not invited anymore, and we won't change our mind on the subject.
Dooglus would like this thread removed. I have no objection to that, and I have asked the moderators to do so if that's within their power.
I don't want the thread removed. I want it to stand as a warning to potential customers to the type of treatment they can expect to receive from your company. It's quite incredible how badly you have managed this. If you had any doubts about the identity of the players at your site you should have spoken to them. I'm sure they would have been happy to video chat with you, send you copies of passports, driving licenses, or whatever. To post an attacking rant like you did is simply unprofessional and offensive.
|
|
|
I fixed a bug in the analysis script that was misclassifying some small "lessthan 64000" and "lessthan 48000" wins as refunds. Results: 2012-Jul-11 12:27pm (up to block 188606)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 7311 | 0 (0.00000) | 7048 | 263 | 28.32 | 0.01 | 16.01 | 28.30 | 0.068 1dice1Qf4 2 0.00003 | 960 | 0 (0.00000) | 891 | 69 | 7.43 | 0.00 | 5.38 | 7.43 | 0.024 1dice2pxm 4 0.00006 | 1460 | 0 (0.00000) | 1429 | 31 | 12.68 | 0.00 | 1.22 | 12.68 | 0.044 1dice2vQo 8 0.00012 | 1228 | 0 (0.00000) | 1190 | 38 | 17.20 | 0.00 | 3.15 | 17.20 | 0.028 1dice2WmR 16 0.00024 | 1426 | 0 (0.00000) | 1397 | 29 | 22.21 | 0.01 | 5.85 | 22.19 | 0.076 1dice2xkj 32 0.00049 | 3201 | 1 (0.00031) | 3189 | 11 | 96.99 | 100.40 | 1.29 | -3.40 | 103.510 1dice2zdo 64 0.00098 | 4952 | 6 (0.00122) | 4929 | 17 | 194.29 | 120.67 | 55.64 | 73.62 | 62.106 1dice37Ee 128 0.00195 | 6049 | 13 (0.00217) | 5989 | 47 | 1222.67 | 1142.73 | 39.25 | 79.94 | 93.462 1dice3jkp 256 0.00391 | 4490 | 21 (0.00469) | 4457 | 12 | 470.16 | 331.94 | 11.11 | 138.21 | 70.602 1dice4J1m 512 0.00781 | 6214 | 37 (0.00596) | 6172 | 5 | 1196.30 | 354.02 | 9.35 | 842.27 | 29.593 1dice5wwE 1000 0.01526 | 8235 | 112 (0.01360) | 8121 | 2 | 1664.95 | 854.50 | 1.80 | 810.44 | 51.323 1dice61SN 1500 0.02289 | 6507 | 148 (0.02277) | 6353 | 6 | 2726.25 | 3014.61 | 15.00 | -288.36 | 110.577 1dice6DPt 2000 0.03052 | 6940 | 215 (0.03099) | 6722 | 3 | 2679.79 | 2151.78 | 9.24 | 528.01 | 80.296 1dice6gJg 3000 0.04578 | 6412 | 311 (0.04856) | 6094 | 7 | 4447.46 | 5564.70 | 24.99 | -1117.24 | 125.121 1dice6GV5 4000 0.06104 | 6717 | 422 (0.06285) | 6292 | 3 | 2292.97 | 2032.27 | 31.20 | 260.70 | 88.630 1dice6wBx 6000 0.09155 | 12411 | 1167 (0.09407) | 11239 | 5 | 7229.29 | 7636.41 | 7.01 | -407.12 | 105.632 1dice6YgE 8000 0.12207 | 22857 | 2826 (0.12364) | 20031 | 0 | 4411.04 | 3968.68 | 0.00 | 442.35 | 89.972 1dice7EYz 12000 0.18311 | 15796 | 3000 (0.18998) | 12791 | 5 | 6458.12 | 6719.99 | 14.50 | -261.87 | 104.055 1dice7fUk 16000 0.24414 | 38932 | 9410 (0.24175) | 29515 | 7 | 11130.51 | 10567.06 | 97.79 | 563.44 | 94.938 1dice7W2A 24000 0.36621 | 28408 | 10490 (0.36967) | 17887 | 31 | 12540.05 | 12526.28 | 212.63 | 13.76 | 99.890 1dice8EMZ 32000 0.48828 | 283749 | 138222 (0.48734) | 145402 | 125 | 84751.02 | 86109.84 | 2173.21 | -1358.81 | 101.603 1dice97EC 32768 0.50000 | 118730 | 59259 (0.49939) | 59403 | 68 | 42161.69 | 40927.90 | 789.19 | 1233.79 | 97.074 1dice9wcM 48000 0.73242 | 71404 | 52477 (0.73534) | 18887 | 40 | 41687.34 | 40205.86 | 442.88 | 1481.47 | 96.446 1dice9wVt 64000 0.97656 | 5698 | 5452 (0.97846) | 120 | 126 | 4952.80 | 4761.02 | 239.20 | 191.78 | 96.128 -------------------------------------------------------------------------------------------------------------------------------------------- | 670087 | 283589 | 385548 | 950 | 232401.64 | 229090.79 | 4206.99 | 3310.85 | 98.575 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 3310.85104294 BTC (1.425%) Cumulative Fees Paid: 337.22142500 BTC SD Profit after fees: 2973.62961794 BTC (1.280%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 1985935 : SatoshiDice Tx: 1243858 (62.6%) Blockchain MB: 839.2 : SatoshiDice Tx: 507.2 (60.4%)
|
|
|
It's not like I chose to segfault. That's not something I have much control over in this case. If I can prevent phenomenon from happening, then I will try, but I don't have any control over that behavior until I find the precise cause.
I wonder if you can provoke the bug into happening more often by running a modified bitcoind that simulates blocks being found very rapidly, so there's a much greater chance of the two events coinciding.
|
|
|
Incidentally, I noticed recently that your SatoshiDice script incorrectly identifies a few hundred winning "under 64000" bets as having been refunded. The multiplier for those bets is so low that even when you win, you sometimes don't cover the transaction fee that they take off for sending your winnings back to you. So your returned amount can be slightly more than your bet, and still be a win, and your returned amount can be very close to your bet amount and not be a refund.
It happens with 'under 48000' bets too. Here are couple of examples: bet wins 71 satoshis less than the stake bet wins 453 satoshis more than the stake
|
|
|
Oh, I misunderstood. I thought you said it used to work and now doesn't. Sounds like it always works, except for one hard crash recently during loading blockchain. Is that correct?
In that case, I suspect a very inconveniently timed blk000X.dat update from the Satoshi client may have messed up (reading a partial write). I always wondered if that would happen, and maybe that's what happened here. Thus confirming it is possible but rare.
I'm not sure there's a good way to fix it (since Satoshi client always has that file open for writing), and I might just have to take the 1/100 chance of that happening until Armory starts managing its own blockchain file.
Am I understanding you?
Yes, it only segfaulted once. And I was running bitcoin-qt at the time, so you're probably right that the blockchain file was updated while it was being read. It doesn't seem like it should be all that rare to me - it takes a minute to read the blockchain, and it gets updated every 10 minutes or so, so that sounds like a 1-in-10 chance to me. I guess maybe it needs to be reading the right bit of the file, and that's why it's rarer. Either way, perhaps you can't stop it being an error, but probably you could do something other than segfaulting when it happens... Incidentally, I noticed recently that your SatoshiDice script incorrectly identifies a few hundred winning "under 64000" bets as having been refunded. The multiplier for those bets is so low that even when you win, you sometimes don't cover the transaction fee that they take off for sending your winnings back to you. So your returned amount can be slightly more than your bet, and still be a win, and your returned amount can be very close to your bet amount and not be a refund.
|
|
|
The first part of the solution is to recompile. Go into the cppForSwig directory, do a "make swig".
I had already done that. I did a 'make clean' then 'make swig' when I updated from git (which I had to do because my 32 bit Python was getting MemoryError exceptions after the blockchain grew to a certain size, and I was hoping you had fixed the problem in git. The second part of this is: I updated the sample code to work, by making the following replacements throughout the code: FROM:for tx in txList: ...
TO:for txref in txList: tx = txref.getTxCopy() ...
Additionally, you must replace all calls to "getTxInRef" and "getTxOutRef" with "getTxIn" and "getTxOut". I have updated the script in the dev branch, though I suspect you have heavily modified it (based on your satoshidice posts... thanks for keeping that up, btw!). So I figured you might want to manually update it. That's all I did just now to modify the script to work with 0.81+ compiled utilities. I had already done something similar, like this: for tx in txList: tx = tx.getTxCopy()
which I think would have the same effect as your suggested change. I also had already replaced the getTx*Ref with getTx* - (else the script threw exceptions and failed). Like I say, the script works almost all the time - it only crashed the once, and I've run it a lot of times since switching to the dev branch.
|
|
|
If I ask blockchain.info's wallet to send to 1FVRij1uYQ4E823kwGV55QZQft9QVTJV24, it tells me it's an invalid to address, but if I ask to send to 1FVRij1uYQ4E823kwGV55QZQft9QVTJV23 it asks me for the private key for one of my addresses to do the spend.
So either they've fixed the bug, or you were copy/pasting it wrongly. Maybe your paste had some invisible formatting in it or something. Try typing the address rather than copy/pasting it - does that work better?
|
|
|
I just ran the armory sample_armory_code.py to generate SatoshiDice stats and got a crash. The script said "Let's look at all the bets ever placed at SatoshiDice.com" then "Segmentation fault (core dumped)".
The logfiles showed:
==> /var/log/kern.log <== Jul 11 02:26:26 chris kernel: [128656.317555] python[29564]: segfault at 4 ip b6c060ed sp bf864c50 error 4 in _CppBlockUtils.so[b6ade000+390000]
This was in git revision 60d513aaee8085, which was the head of the 'dev' branch last time I fetched from the repository (5th July).
I've run the same script many times without a problem, so I can't reproduce the bug, or provide any extra information that might be of use, sorry. Just: there's a serious crashing bug in there somewhere...
|
|
|
I've spent all day re-downloading the blockchain after a hard drive failure corrupted my copy. Here's an update to the SatoshiDice stats. Looks like the site is up over 1000 BTC since the last time I posted. Results: 2012-Jul-11 02:33am (up to block 188553)
Address Target Should Win | #Bets | Win | Lose | Refunds | BTC In | BTC Out | Refund | Profit | RTP -------------------------------------------------------------------------------------------------------------------------------------------- 1dice1e6p 1 0.00002 | 7243 | 0 (0.00000) | 6981 | 262 | 28.11 | 0.01 | 15.91 | 28.09 | 0.068 1dice1Qf4 2 0.00003 | 958 | 0 (0.00000) | 889 | 69 | 7.41 | 0.00 | 5.38 | 7.41 | 0.024 1dice2pxm 4 0.00006 | 1457 | 0 (0.00000) | 1426 | 31 | 12.65 | 0.00 | 1.22 | 12.65 | 0.044 1dice2vQo 8 0.00012 | 1226 | 0 (0.00000) | 1188 | 38 | 17.18 | 0.00 | 3.15 | 17.18 | 0.028 1dice2WmR 16 0.00024 | 1422 | 0 (0.00000) | 1394 | 28 | 22.18 | 0.01 | 4.95 | 22.16 | 0.076 1dice2xkj 32 0.00049 | 3197 | 1 (0.00031) | 3185 | 11 | 96.95 | 100.40 | 1.29 | -3.44 | 103.553 1dice2zdo 64 0.00098 | 4746 | 6 (0.00127) | 4723 | 17 | 189.63 | 120.67 | 55.64 | 68.96 | 63.633 1dice37Ee 128 0.00195 | 6037 | 12 (0.00200) | 5978 | 47 | 1221.85 | 1142.24 | 39.25 | 79.61 | 93.484 1dice3jkp 256 0.00391 | 4487 | 21 (0.00469) | 4454 | 12 | 469.95 | 331.94 | 11.11 | 138.00 | 70.634 1dice4J1m 512 0.00781 | 6106 | 35 (0.00574) | 6066 | 5 | 1194.44 | 346.61 | 9.35 | 847.82 | 29.019 1dice5wwE 1000 0.01526 | 8142 | 110 (0.01351) | 8030 | 2 | 1654.70 | 848.15 | 1.80 | 806.54 | 51.257 1dice61SN 1500 0.02289 | 6489 | 146 (0.02252) | 6337 | 6 | 2725.20 | 3010.39 | 15.00 | -285.19 | 110.465 1dice6DPt 2000 0.03052 | 6873 | 209 (0.03042) | 6661 | 3 | 2670.04 | 2129.62 | 9.24 | 540.42 | 79.760 1dice6gJg 3000 0.04578 | 6397 | 309 (0.04836) | 6081 | 7 | 4446.51 | 5562.59 | 24.99 | -1116.08 | 125.100 1dice6GV5 4000 0.06104 | 6694 | 419 (0.06262) | 6272 | 3 | 2292.38 | 2030.50 | 31.20 | 261.87 | 88.576 1dice6wBx 6000 0.09155 | 12181 | 1153 (0.09469) | 11023 | 5 | 7201.29 | 7611.02 | 7.01 | -409.72 | 105.690 1dice6YgE 8000 0.12207 | 22679 | 2807 (0.12377) | 19872 | 0 | 4396.67 | 3957.72 | 0.00 | 438.94 | 90.016 1dice7EYz 12000 0.18311 | 15757 | 2996 (0.19020) | 12756 | 5 | 6437.21 | 6701.99 | 14.50 | -264.78 | 104.113 1dice7fUk 16000 0.24414 | 38674 | 9347 (0.24173) | 29320 | 7 | 11004.63 | 10455.74 | 97.79 | 548.89 | 95.012 1dice7W2A 24000 0.36621 | 28312 | 10452 (0.36958) | 17829 | 31 | 12506.80 | 12496.78 | 212.63 | 10.02 | 99.920 1dice8EMZ 32000 0.48828 | 283521 | 138117 (0.48736) | 145279 | 125 | 84697.01 | 86053.02 | 2173.21 | -1356.01 | 101.601 1dice97EC 32768 0.50000 | 118103 | 58967 (0.49957) | 59069 | 67 | 41961.41 | 40734.94 | 789.19 | 1226.46 | 97.077 1dice9wcM 48000 0.73242 | 71043 | 52202 (0.73522) | 18800 | 41 | 41553.51 | 40079.90 | 442.88 | 1473.61 | 96.454 1dice9wVt 64000 0.97656 | 5697 | 4598 (0.97457) | 120 | 979 | 4901.48 | 4709.70 | 287.60 | 191.78 | 96.087 -------------------------------------------------------------------------------------------------------------------------------------------- | 667441 | 281907 | 383733 | 1801 | 231709.32 | 228424.06 | 4254.38 | 3285.25 | 98.582 --------------------------------------------------------------------------------------------------------------------------------------------
SD Profit before fees: 3285.25987455 BTC (1.418%) Cumulative Fees Paid: 335.89477500 BTC SD Profit after fees: 2949.36509955 BTC (1.273%) ---- Since Satoshi Dice started, there have been: Blockchain Tx: 1975820 : SatoshiDice Tx: 1239235 (62.7%) Blockchain MB: 835.1 : SatoshiDice Tx: 505.3 (60.5%)
|
|
|
Does anyone know why this was a problem with Tradehill but not MtGox?
We don't know if it wasn't a problem with MtGox. We just know if it was, they weren't crippled by it. We don't even know that. They apparently take weeks to honour bank wire USD withdrawals, and blame it on something to do with Dwolla. Maybe they were crippled by it but are trying to trade their way out of the mess...
|
|
|
It looks to me like the stated house edge is incorrect.
I figured out what's going on. The house edge is 3.5% on winning bets, and -0.5% on losing bets, making 3.0% overall.
|
|
|
|