Hi Slush,

I posted before the recent D jump to 877k, unfortunately soon after there was the attack on ur pool and I know you were really busy getting it up again. Now I'd like to bring my concern up again. I've not really arrived at an average that is close to my expected rate of BTC before and I have not now.

My expected at current difficulty is ~3.7 BTC/day and with 2% stales it's still ~3.6 BTC/day. I'm seeing 2.7ish and a 7-day average of 2.45ish. This is much similar to my previous post % of around 30% difference between my 7-day average and my expected returns. I've been busy to change my script to test out other pools and I'd like to ask for some sort of justification.

Judging from what I hear from others, they are getting pretty close to the expected value thus I'm feeling like there is some kind of fault on my end, however I'm not seeing it. Your previous reply indicated there might be some problems with my miners. I've stayed with them and I'm seeing no issues, just for info I'm running

Ubuntu 11.04
Phoenix 1.5 w/ phatk @ VECTORS BFI_INT WORKSIZE=256 AGGRESSION=13
CCC 11.5 + SDK 2.1
AMDOverdriveCtrl 1.2.0
2x5970 ~750 Mhash/s ea. (OC @ 850/300 FS: 100% ~ 75 celcius)
5x5850 ~355 Mhash/s ea. (OC @ 900/250 FS: 100% ~ 65 celcius)

Stales at around 2.3% average.

These are on 2 dedicated machines, I've got problems running my other 5850 and 4850 since my 3 year'o 600 W PSU blew but still. Please advice. TIA

he is seeing 2.7ish, don't you read what you quote?



To Slush: Please enable a address lock, this will give ppl time to fix things when shit hits the fan for them. At least the thief can't steal unless the user is away for more than 24hours. PLEASE ENABLE THIS. It will make your pool more secure and I know alot of ppl LOVE BTCGuild because they have this safety feature.

It takes one second to create another one..this is no sollution. I just don't understand why the attacker does not use several(let say 50) different adresses to be less traceable.

I don't think this would stop him but I'm assuming there are a lot of account that have pending wallet transfers. I think it'd be smart to go ahead and revert any pending wallet transfer to that address in the event someone unwittingly confirms it. I think it'd be wise to roll out mandatory password changes, too, or at least send out an advisory email. I didn't change mine because I switched to a different pool and didn't think about it (plus I had only a very small fractional balance left at BPM). Last time I looked at the address on block explorer it didn't look like he'd snagged any big sums of BTC so it could be the case that the only account with weak passwords were idle accounts but better safe than sorry.

Slush-
So do wallet changes automatically need email conformation or how do we set that up? I thought you said you already added this feature.

Why we need 'lock'? I don't see any advantage in that. Email confirmation isn't enough? Afaik it works very well for pool users.

Some users has changed wallet, because attacker entered their account before I released email confirmation. But I detected many intrusions and cancelled attacker address on those accounts. But of course everybody have to check his account if wallet is correct.

As far as I can say, pool accounts are now safe, even if attacker know login/password for them.

I tried the day after it went into effect.  All I got was the "ERROR:  Can't connect to Bitcoin:  Bitcoin returned unparsable JSON" message.

I'm trying to connect as follows:

--url http://me.something:pass@api.mining.cz:8332

what am I missing?

Thanks.

try "telnet api.bitcoin.cz 8332" from a command prompt. if you timeout and don't connect, it ain't your mining software and setup causing you issues.  you will then have to look to your network as the source of the problem.  if you do connect, then something isn't right with the mining client...  give it a try...

Can you confirm that it actually connects using telnet?  If it only says attempting to connect then you are not connecting.  If telnet connects, most likely you will see a blank window with a blinking cursor in top left (on windows).  If it tells you that it's attempting to connect and eventually times out like this:

C:\>telnet blah.blah 8332
Connecting To blah.blah...Could not open connection to the host, on port 8332: Connect failed
C:\>

then it's not your mining client...

Slush, This looks a little hinkey to me. Any idea why the two blocks are so low on payout for the ones I marked with "**"?
#   Block found   Duration   Total shares    Your reward    Block #   Validity   Cluster GHash/S   Your MHash/S

5995    2011-06-24 03:57:24    0:08:32    233715    0.08002712    133047    95 left    2013.97   3223.44
5994    2011-06-24 03:48:52    0:03:31    91624      0.08548592     133045     93 left     1915.85    3275.57
5993    2011-06-24 03:45:21    0:15:37    426907    0.07600799    133043    91 left    2010.15   3055.75
5992    2011-06-24 03:29:44    0:05:02    134393    none            133040      88 left                                    **
5991    2011-06-24 03:24:42    0:27:33    754159    0.02456564    133038    86 left    2012.92   988.97   **
5990    2011-06-24 02:57:09    0:33:19    917871    0.07541716    133033    81 left    2025.84   3055.66
5989    2011-06-24 02:23:50    0:07:10    189786    0.08329346    133028    76 left    1947.29   3243.93
5988    2011-06-24 02:16:40    1:14:23    2046477    0.07619624    133025    73 left    2023.09   3083.04
5987    2011-06-24 01:02:17    1:16:12    2101315    0.07161271    133016    64 left    2027.78   2904.29
5986    2011-06-23 23:46:05    0:30:22    823815    0.06638683    133010    58 left    1994.88   2648.68
5985    2011-06-23 23:15:43    0:34:41    934902    0.07003427    133006    54 left    1982.12   2776.32
5984    2011-06-23 22:41:03    0:22:22    585530    0.07118223    133001    49 left    1925.01   2740.52

This has not happened to me before.

On the 2nd one Cluster GHash/s is blank as well.