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

Slush pool in attack, so i changed to deepbit & found 0 rejection due to LP.
Seems until all members of slush push him , he won't add LP support.
I always get 1-3% of stale shares due to no LP, which i am not getting now on deepbit due to LP support.
When will you add LP support slush?

That was just small mistake in confirming payouts, it were fixed manually by me; those blocks are fine now.

Server is currently under attack, I'm solving that. Thanks for your patience.

There isn't one.

What is the fee for sending earned bitcoins from slush's pool to your bitcoin wallet?

Oh, well, guess we will be ignored.

Looks like Slush is relegated to backup pool from now on.

Block 135263 (record # 6431 from stats) still says no reward, though I know for a fact that I had two workers each with 300+ shares!

I think so too. Stats saying "your reward" : "none" for this block.

Wish you had instant payout, really annoys me having to hit threshold.
Good pool tho! =)

So, just out of curiosity, was there going to be ANY response at all to the issue I brought up?

Hi Slush,

After watching my worker stats for the past few days with my Cacti template that uses the JSON API, I noticed the last share times seemed to jump around for the running workers.



The following graph shows another worker that was shut down late Thursday night and stopped submitting shares. The initial jump to ~9600 seconds at ~22:40 (the time I shut the worker down) is odd given the previous values, but the growth rate from then to the end of the graph on the right looks normal.


Since the JSON API provides the last_share time in UNIX time format, my script simply subtracts the last_time value for the worker from the current time to get the elapsed time in seconds. It seems to work most of the time, save the weird spikes shown in the first graph.

Is it possible one or more of the servers providing the last share data aren't synced time-wise resulting in these jumps as load balancing shifts the JSON API query to one of the affected servers?

Thank you for this, at least I'm not alone in thinking this block was calculated wrong.

Slush,

Could you please re-run payout calculations for block 135263 (record # 6431 from stats)

Something isn't right with it...

Thanks!

I do not show 6414,13,12 as invalid...  they are all confirmed for me.

I do see 6420 as being invalid though...

Hmm, any particular reason I have no reward listed for block #135263 when I had two workers with 300+ shares each? That's the block that was ending as you "restarted balancer".

*see my earlier post*

3 invalid blocks?

And I am getting no reward also for block 6431 with 1GH/s.

What is going on?

Unfortunately, I am going to have to switch to another pool once again. I originally started mining with this pool but about 1 month ago switched to another because of the amount of invalidated block compared to any other pool. 

6414    2011-07-07 18:24:00    0:11:13    483355    0.00800290    -    invalid
6413    2011-07-07 18:12:47    0:11:39    497313    0.00734895    -    invalid
6412    2011-07-07 18:01:08    0:53:54    2333879    0.00803047    -    invalid

Three Invalid block in a row is just unacceptable.  I'm thinking there is something fundamentally wrong if so many of the pools' blocks are invalid, the chances of having bad "luck" by another pool just barely finding the block faster on 3 blocks in a row is miniscule.

6432    2011-07-08 06:19:12    0:38:17    914357    0.00431025    135266    74 confirmations left
6431    2011-07-08 05:40:55    1:41:08    4001166    none    135263    71 confirmations left
6430    2011-07-08 03:59:47    0:15:26    634924    0.00773850    135254    62 confirmations left

One other problem is block #6431.  I don't believe my miners stopped working for exactly 1:41:08 during the search for this block.

I can say that I do enjoy the occasional exceptional "luck" with short rounds with slush's pool, but the amount of invalidated blocks on average in 24 hrs, are worse than any fee any other pool charges.

So does total rewards decrease if you move to a different pool or don't submit shares in consequent rounds?

I had .301 total rewards last night. I set my minimum payout to .3 thinking that at some point today it would get payed out. I then realized that block 135220 still shows as no block found so I assumed it would get invalidated at some point and was going to adjust minimum payout accordingly. Now though my total reward is shown as .25xxxx. So basically my unconfirmed reward went down, but I don't see any invalid blocks shown in the last 6-8 hours when I last saw the original reward amount?

I realize this is a pitiful amount of btc, but why would it decrease by 1/6th simply because I stopped mining here?

Those blocks are not there because they were found by another pool.

Why do some of the blocks that my miner works on not show in statistics? What happens to the accepted results eg. for 135274 I found about a 100 but there is no 135272 listed in statistics.

Hello guys, I was out for few days on holiday. Now I'm back and will respond to all your posts and PM soon .

About today issue - I had to restart balancer (so pool was down for ~two minutes now), but should be running fine now.