Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1017. (Read 4382653 times)

Iam using slush's Pool again because I dont get so much at deepbit with my 200 Mhash/s

Yea, thus I want to find out what's wrong. It didn't seem to me everyone else was having this problem as well. As the graph updates I only had 3.1 BTC yesterday. My expected is 7.33, and I've even done the calculation myself. This is really odd, I checked the miners even when I'm out (which is hardly) and I administer them myself. I'm on holidays right now and are home most of the time doing this and writing my thesis (Thus I don't sleep much). I don't see a reason why I'm getting such low rewards. I was busy trying to get my mining stable before and didn't really spend time to understand pools, shares and scores. However, I thought the rewards should not be so much different from solo except for fees in exchange for variance.

ok, that was stupid, I missed the output of the terminal, I just had to give it an address without http

If you're giving only 50% performance all the time, then something is probably wrong. There are too many factors which can hurt your earnings: mining hardware itself (are you really mining at expected hashrate?), connection quality (any connection downtime?), network lags (what's your ping/packetloss?).

Then of course luck (but should not be *so* important), pool downtime (yesterday it was around 15 minutes in total caused by attack) and weird thinks like using all gpus on same worker etc.

Daily rewards fluctuate a bit on my miners, too. It's pretty natural to mining process. But I'm not observing such huge drops, so I'm expecting something wrong on your side.

Having problems with DiabloMiner. I start i with "./DiabloMiner-Linux.sh -u ***** -p ***** -o http://mining.bitcoin.cz -r 8332 -v 2 -w 256"
Every 5 secodns i get "ERROR: Can't connect to Bitcoin: http", on the bottom left corner it shows my hashrate, which seams reasonable...

I dont know if i should just ignore the error (because of the hash rate) or if I am using my power for no profit.

How do i integrate my CPU with the pool as well? Using bitcoiner 0.3.21

This right here was priceless information that I've been looking for. Thank you good sir.

Yea precisely my point. It's suppose to go closer (more or less) to the expected figure. 2.3 is A LOT of difference in my opinion (I'm not sure if it's this much of a difference), so I'm asking around unless everyone is getting a 2+ tolerence or I'm missing something...

And 2+ is a modest estimate because I only hit the maximum of 5 BTC only 2 times. I'd like to know if this is a common thing or do everyone get so much a difference from the calculator then I don't understand how people are getting into mining so blindly putting faith into the calculator.

Just started today and getting 230~ mhash on my 6870.

How long before I start to see results in my account?
Do I need constant internet connection?
Is there any way to tell what block i am working on?

Thanks

edit: Just seen ive gotten a 0.00560481 reward on block 129965, what does this equate to in reality?
edit: nvm its BTC, thought it may have been %age of work or something

Seems both pool was attacked. I am running PR1.41 , my main server is slush & back up is deepbit.
For around 15 minutes, miners cant able to mine & keep on switching from slush to deepbit & vice verse.
After that mining is going normally.

For those of you worried about losing out on mining if the pool gets DoS'd/DDoS'd there's a simple workaround.  Just setup a second worker for the same GPU with a lower aggression setting and point it to another pool/your local bitcoin solo server and leave both running.  I'm using GUIMiner/poclbm and for every GPU I have one miner/worker set up and pointing to slush's pool and then another for the same GPU pointing to my local Bitcoin client for solo mining.

For example, one of my cards is a 6950 and I have it running with the flags "-v -w 128 -f 1" for the Slush pool miner and "-v -w 128 -f 15" for the solo miner.  Assuming the pool is up, I get ~ 369 MH/s going towards slush's pool and ~ 1 MH/s going towards the local solo bitcoin server.  If I ever get any connection problems to the pool, the solo miner ramps up to ~ 366 MH/sec and chugs away.  Once the pool comes back up it reverses back to just about everything to Slush and the trickle to the solo.

Yeah, it's double the work, especially if you want to use multiple pools and have to manage all the workers on the pool websites as well, but for a bit of extra time during setup, at least you don't have to worry about these DDoS attacks or any hardware failures on Slush's side putting your mining out of commission.

Seems I've been performing a little better than the calc with some down time even.... I may be underestimating my hash rates.

so 2.3 is fees, rejected shares and I have no down time. Wow I didn't know they cost so much.

I think the calculator is assuming solo mining with no fees to be payed.  So you need to subtract 2% from that.  It also assumes that there is no pool or miner down time and that you don't have your result rejected by the network.

The last share time is all jacked up.....

Whats up?

DKN

Slush, I know you're really busy. But recently I've been doing some calculation.

http://www.alloscomp.com/bitcoin/calculator.php
says I should be getting 7.3/day. My max before was around 5 and that was once or twice. I don't know what to look for, I have some time now since my rigs have been stable and I've gotten used to the rest of the maintainence work to keep them that way. So could you please tell me how do I get closer to my 7.3/day or are we just having a really bad day?

Slush hows that long polling coming i know you have been working on it for a while. Just curious

Yes, invalid is that one with 53 shares. Too bad for being invalid, afaik it is all time record, previous one (but valid) was 83-shares round. But it was in times of 30k difficulty .

Lets hope the 1 second one is invalid then. Would suck to crunch for 3 hours and then have it divided between 52 shares in the end (of which I had none of course ).

I have no reason to think that this 3hour round was caused by some p2p network attack (except that pool hashrate was lower for some time because of that DoS).

Also keep in mind that 'other' are just estimation. There is no way to measure 'other' hashrate exactly.