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

I've been many hours over my threshold (which is below the 0.05 value in the FAQ), it is now almost 3 times my threshold but still no payout... Slush has been 'consistently inconsistent' with the payout regime, although it always happens eventually, but the delays are frustrating and unjustified 

I'm going to have to switch to another pool until this gets sorted out.  In the last 4 blocks 2 of my rewards have been 1/100th or 1/10th of my expected returns .  I'm loyal to slush but I gotta make that money.

Yeah I grok that. But being on a pissy wireless broadband plan that's sometimes painfully slow (especially mid morning) along with capped downloads so low I don't even want to go there, it surprised me 1's were still accepted at those hashing speeds. I did end up going back to 3 which put's me at diff 2 again but oh well it was just a suggestion.

Maybe slush has been busy with his trezor project and that's why he hasn't checked in lately? I understand that he can't respond to every question, especially questions that have been asked many times before, but checking in every now and then or having some other way for miners in this pool to contact him would be much appreciated. Anyone checked the IRC channel recently?

I personally haven't had any issues with payouts or calculations over the last few months, or maybe I simply didn't notice, but for those oddball cases a short explanation would come a long way. Just my 2 mBTC!

Exactly right. But at 2-2.5Ghash it's possible to exceed 100 shares a minute (or I guess I should say 'when it's passing off the lowest difficulty results one can be credited with more than 100 shares a minute' ) Here is a a snippet from about half an hours worth;

Reject ratio: 0.1%
 Items worked on: 2513
 Discarded work due to new blocks: 133
 Stale submissions discarded due to new blocks: 0
 Unable to get work from server occasions: 0
 Submitting work remotely delay occasions: 0
 
I still reckon it would be a nice touch and would help mitigate the problems you listed above. Some people aren't in a position to decide they'll just point 3 at it to save bandwidth and latency issues.

As an aside it was good to read your concise write up.

Yea, I'm seeing my hashrate reported through the API as very unstable.  Sometimes it shows 200MH/s and then gets better during the round, when I'm consistently pushing near 10 GH/s.

Do you take Slush's share rate setting as a disadvantage? The lower the accepted difficulty setting, the lower your variance.

And in case of the Slush's scoring algorithm, one has to have a bit higher shares per minute, as only the latest shares submitted have some significant value. Thus one gets effectively less shares for the accounting (only a part of the shares submitted in the round, which makes the round effectively shorter), and for maintaining the same level of precision and keeping the variance reasonably low, one has to increase the share rate by some amount.

Been like 18 hours since I passed my payment threshold.  Now way over. 

Your miner is not sent shares of any difficulty - in fact, it is not sent shares at all.  It is allocated new work every so often, and told by the pool what difficulty of result is acceptable.  When it calculates a result whose difficulty matches or exceeds that threshold, then the result is sent, and you are credited with a number of shares equal to the threshold difficulty.

Let's say you are mining with a GPU producing on average four results per minute.  Some of those will probably be rated diff 1.  Slush has set your threshold to 1 (as it's so slow) so each of those results is accepted and earns one share.  If you were able to set your own threshold, as used to be the case, any results below the threshold you set would not be sent and thus ignored.  You might then go a minute or more and earn nothing, even missing out completely on some very short rounds where you might otherwise have had at least one or two shares.

You now upgrade to a faster miner, producing around 150 results per minute.  Slush will quickly adjust your difficulty threshold higher, aiming to receive around 20 results per minute.  Let's say it's raised to 4 - then your miner will only send results with a diff of 4 or more, and you will be credited with 4 shares per result.  Higher, but fewer of them.

In all cases the work allocated is the same: it's just the difficulty of the accepted results that varies.

The whole point of this being done automatically is that it optimises the rate at which your results are sent, preventing the server being stressed by excessive traffic, and using less of your internet connection bandwidth, while maintaining your share generation rate.  This latter can be important, for at busy times your connection speed may vary widely, and you might find that your hash rate slows down noticeably; reducing the traffic sent may limit the damage.

Ugh, ok... thanks.

I'd love to see manual setting of diff as an option again.

Anything below 2.3Ghash pointed to slush and you'll keep getting sent diff 1 shares. Of the other pools I've looked at 2 is set as the bare minimum.

The FAQ currently says it's now every 15 minutes.  That hasn't been my experience, though.  I am waiting for a payout and it has been past threshold for at least a couple of hours. 

It used to be at the top of the hour, but at the moment is seems random.  Maybe they are being triggered manually at the moment.  All I know is that it isn't consistent right now.

How often does Slush's pool pay after reaching your payout amount?  Just curious.

My numbers look ok now too. Looks to me like since the database server upgrade on 26 Nov things have been quite unstable.

Morris

Looks like latest confirm problem is fixed. I sure would like an official "hey we are still here" post from slush though. I don't like that there doesn't seem to be any communication channel to the pool operators when there is a problem.

Who's to say that reporting is correct?


ETA: It looks like the numbers are now going the right way.

Good points. I guess I take the view that because in the past (that is until the things you pointed out) they always did, and that the massive miners with the most to lose are yet to jump ship.
The whole uncomfirmed reward thing is crazy though. Could always delete our accounts to get the remaining payouts that are owed even if below threshhold and then create a new one. Shit that wouldn't work for me anyway since my confirmed is 0. My non confirmed/total will be zero soon too at the rate I'm going backwards.

The problem is I haven't seen any sign recently of things sorting themselves out. Round 21027 never got fixed and there has been no reply on the issue from slush. Sorry, but I need a pool operator that is at least responsive to problems.

As things are being confirmed the are being SUBTRACTED from the confirmed total. This is not good.

When was your last payout? ie I got a payout a little while back, so my confirmed reward is zero but my unconfirmed total is correct.

Though having said that I've no idea what block my payout actually came through on.  Ok my apologies I misunderstood what you were saying - you're correct - nothing is moving from unconfirmed even though they are well and truly past 100 confirmations. I wouldn't stress to much about it though I'm sure it will sort itself out.

Edit to add: Right this minute my total reward went down a huge chunk right in front of my eyes. Almost laughable. This is actually a bit disconcerting if for nothing else it makes the backend look flaky as fuck lol. Then again none of the big boys (those with hundreds or thousands of Mhashes) have moved on we're still around the 410-415Thash