[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[Sebz4n]

I am mining on two 5850 cards, but one of them keeps experiencing a connection error... why is this?

[cosurgi]

I am mining on two 5850 cards, but one of them keeps experiencing a connection error... why is this?

what software do you use? an old version of phoenix had this kind of problem.

[SicKk]

No, calculation on profile page is made from shares of current round and it is expected to be very inaccurate. Actually 1Ghash from real 1.3 Ghash is pretty good estimation, nothing to worry about.

better if you check your daily reward. This MHash on your profile is hidden for the reason, that this calculations is not accurate. It varies wildly. Prettly likely that you will obseve also 1600 MHash/sec for a brief while.

thanks guys for the quick answers  

[pokermon919]

I am mining on two 5850 cards, but one of them keeps experiencing a connection error... why is this?

what software do you use? an old version of phoenix had this kind of problem.

I have the same problem with one of my 5870's.

Specs:
Win 7 Ultimate 64bit
GUI Miner
3 5870's roughly Core=960-970 & Mem = 330
5870 that dc's, Core 970 & Mem 325

I've tried lowering the core clock but I still get the same problem.

[SchizophrenicX]

Yea, I mean. I don't really get how all these works. It's in the name of reducing exploits and all I get it. If it's luck I get it. It's almost a 7th day and my average is going no where near my calculated. This is not right, I thought all these is not suppose to affect your reward 'that' much. We're still suppose to be able to go close to the calculated (expected) reward. It was 3.18 the day I posted about this. That is less than 50%, it's 5 on the last graph. My expected is 7.33 my 7-day average is 4.37. What's going on?

P.S And it even had a high system reward on the last graph 2800 BTC.

Yes, score system should not affect mining income so much and definitely not over so long period. Do you see any troubles on miner side? Unusually high invalid ratio, idling miners or something? Do you use separate worker accounts for every gpu? It may be really something small....

Not sure what qualifies as Unusually high invalid ratio, miner's idle for awhile. I usually spot it if it goes no work or idle as I'm always monitoring the accounts page, I'll reset it by running another miner on that GPU before closing it. I use separate worker accounts for every GPU, I thought that is how it goes.

EDIT: I have around 2.3% Rejects on Phoenix and I'm guessing lesser on poclbm, they are running headless so I'm not sure.

My expected is 7.33 my 7-day average is 4.37. What's going on?

what is your configuration? How many GPUs? which miner software do you use? How many worker accounts have you configured? Do you see on your profile page, that each of your worker accounts is accumulating shares?

I currently have systems running
1. 4x5850 running on poclbm (since phoenix w/ phatk didn't do much of a diff in the hash and poclbm runs more stable) | LinuxCoin | Uptime: 24/7
2. 2x5970 + 1x5850 running on phoenix w/ phatk | LinuxCoin | Uptime: 24/7
3. 1x5850 running on poclbm | LinuxCoin | Uptime: 24/7
4. 1x4850 running on guiminer | Windows 7 | Uptime: 24/7
5. 2x4870 running on guiminer | Proxy (Friend) | No OC | Uptime: 6 hr/day
6. 1x5770 running on guiminer | Proxy (Friend) | No OC | Uptime: 24/7
7. 1x5870 running on guiminer | Proxy (Friend) | No OC | Uptime: 6 hr/day

Reason on LinuxCoin being I'm still trying very hard to install Ubuntu and everything to work. LinuxCoin sometimes logs out for no apparent reason and I have to manually set all GPU to mining again.

I have all GPU to individual workers. (5970 - 2 Workers, 1 GPU ea.)
5850 are OC'd @ 900/300 doing 350~360 Mhash/s | -v -w256 -f30 | VECTORS BFI_INT WORKSIZE=256 AGGRESSION=7
5970 are OC'd @ 850/300 doing 370~375 Mhash/s (per core) | VECTORS BFI_INT WORKSIZE=256 AGGRESSION=7
The 4850 is just doing it's 65~75 Mhash/s
5770 is doing 170 Mhash/s average
5., 6. & 7. are my friends running their cards for me
I'd safely say I have around
(4x370) + (6x350) + 170 = 3.75 Ghash/s as a baseline and I'm expecting around 6.65 BTC at the least

Yes I see my workers are accumulating Shares and Scores every round. I just don't know why I'm averaging less than my expected and sometimes doing so badly.

[Sebz4n]

I am mining on two 5850 cards, but one of them keeps experiencing a connection error... why is this?

what software do you use? an old version of phoenix had this kind of problem.

I am using the newest version of GUIMiner.
This has never been a problem before I switched to slush's pool.

Any fix? Can it be because I've clocked my card too much?

[kosovito]

Any way to see my last 24h gets??

thanks

[SchizophrenicX]

Update of the graph. I got 4.693. 7-day average is 4.54
I'll be waiting for advice.

[allinvain]

Slush you better check your security as my account on your pool just got hacked even though I had a super long randomly generated password (used from a password generation site). Whoever hacked in switched the payout address to the following:

15iUDqk6nLmav3B1xUHPQivDpfMruVsu9f



Uploaded with ImageShack.us

Visual proof...

Hmm, at this point I'm not sure whether to trust this pool anymore. There is no way someone could've brute forced my password. Maybe it's time to jump to a pool that does not require a username/password.

[allinvain]

Ok, fuck this I'm moving somewhere else..it happened again right after I changed the password to the account. This time the address was changed to:

176LRX4WRWD5LWDMbhr94ptb2MW9varCZP

http://blockexplorer.com/address/176LRX4WRWD5LWDMbhr94ptb2MW9varCZP

AND the payout was reset back to 1.

[finnthecelt]

Ok, fuck this I'm moving somewhere else..it happened again right after I changed the password to the account. This time the address was changed to:

176LRX4WRWD5LWDMbhr94ptb2MW9varCZP

http://blockexplorer.com/address/176LRX4WRWD5LWDMbhr94ptb2MW9varCZP

AND the payout was reset back to 1.

Is your password for the site the same as the password for your registered worker?

[allinvain]

Ok, fuck this I'm moving somewhere else..it happened again right after I changed the password to the account. This time the address was changed to:

176LRX4WRWD5LWDMbhr94ptb2MW9varCZP

http://blockexplorer.com/address/176LRX4WRWD5LWDMbhr94ptb2MW9varCZP

AND the payout was reset back to 1.

Is your password for the site the same as the password for your registered worker?

no way, I'm not that stupid...

and the password was stored locally only in an ecrypted file...that's about the only other place that password would be stored other than than slush's server...

[allinvain]

ok this is weird..now my confirmed reward says :6.112e-05 BTC when before it was below 0...

Sucks that I lost 3.90 BTC though

Maybe I shouldn't publish my btc address here on the forum...

Slush please look into this and at least let me know what the heck happened and how the account was broken into.

[kcobra]

Slush really needs to implement the following two features:

1. Login/my account under HTTPS.

2. Twenty-four hour payout lock when wallet address changes.

Not running login over https is pretty dang bad. The 24 hour payout lock would certainly be nice.

[finnthecelt]

Slush really needs to implement the following two features:

1. Login/my account under HTTPS.

2. Twenty-four hour payout lock when wallet address changes.

Not running login over https is pretty dang bad. The 24 hour payout lock would certainly be nice.

True.

There are certainly people preying on his site. My account was broken into but it was my own fault..... Noob mistake but the predators are out there. Kinda sad really. You have high hopes for Bitcoin but the criminal mind is relentless and ever present. May their armpits be infested with the fleas from a thousand camels!!!

[allinvain]

Slush really needs to implement the following two features:

1. Login/my account under HTTPS.

2. Twenty-four hour payout lock when wallet address changes.

Not running login over https is pretty dang bad. The 24 hour payout lock would certainly be nice.

True.

There are certainly people preying on his site. My account was broken into but it was my own fault..... Noob mistake but the predators are out there. Kinda sad really. You have high hopes for Bitcoin but the criminal mind is relentless and ever present. May their armpits be infested with the fleas from a thousand camels!!!

How did it happen to you out of curiosity. The reason I'm asking is I'd like to know whether this is my screwup somehow or if it's slush's fault.

[finnthecelt]

Slush really needs to implement the following two features:

1. Login/my account under HTTPS.

2. Twenty-four hour payout lock when wallet address changes.

Not running login over https is pretty dang bad. The 24 hour payout lock would certainly be nice.

True.

There are certainly people preying on his site. My account was broken into but it was my own fault..... Noob mistake but the predators are out there. Kinda sad really. You have high hopes for Bitcoin but the criminal mind is relentless and ever present. May their armpits be infested with the fleas from a thousand camels!!!

How did it happen to you out of curiosity. The reason I'm asking is I'd like to know whether this is my screwup somehow or if it's slush's fault.

Well as you say you were not stupid enough to use the same password for your worker, I was. I'm man enough to admit it 


I was in  a hurry and excited to get starterd. It had nothing to do with slush. The net has really made the criminal bold. They see it as a "well if your that dumb" mistake you deserve to be stolen from. But blaming stupidity for criminal justification doesn't improve the morality of it. I'd like the dweeb who did it try and come to my house and steal from me.

[allinvain]

Slush really needs to implement the following two features:

1. Login/my account under HTTPS.

2. Twenty-four hour payout lock when wallet address changes.

Not running login over https is pretty dang bad. The 24 hour payout lock would certainly be nice.

True.

There are certainly people preying on his site. My account was broken into but it was my own fault..... Noob mistake but the predators are out there. Kinda sad really. You have high hopes for Bitcoin but the criminal mind is relentless and ever present. May their armpits be infested with the fleas from a thousand camels!!!

How did it happen to you out of curiosity. The reason I'm asking is I'd like to know whether this is my screwup somehow or if it's slush's fault.

Well as you say you were not stupid enough to use the same password for your worker, I was. I'm man enough to admit it 


I was in  a hurry and excited to get starterd. It had nothing to do with slush. The net has really made the criminal bold. They see it as a "well if your that dumb" mistake you deserve to be stolen from. But blaming stupidity for criminal justification doesn't improve the morality of it. I'd like the dweeb who did it try and come to my house and steal from me.

Yeap, unfortunately I see security as being a major future issue for bitcoiners. Just watch the string of newbies who get their bitcoins stolen by from trojan/virus/malware etc. We really really really badly need the wallet.dat to be encrypted by the official client.

Also slush needs to use SSL for all pool website traffic. C'mon slush invest in a damn certificate, they're not that expensive any more.

One can technically load up his site via ssl but it's a self signed certificate and even then ssl is not enabled by default. When someone types in the pool's website it should redirect to https://mining.bitcoin.cz

[kcobra]

Alert: My workers connected to slush started going idle about 60 seconds ago. Went up an down for a bit and now they are 100% idle.

The website is also down.

[allinvain]

Alert: My workers connected to slush started going idle about 60 seconds ago. Went up an down for a bit and now they are 100% idle.

The website is also down.

Yep, noticed that too. I moved all my workers to Eligius though so I'm still hashing away, but the site is offline in both http and https mode. I have a hunch he's getting DDoS'ed like Tycho's pool.