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

[BinoX]

I'm working on a little something that might make it a bit easier, although not as easy as a normal unfortunately...

Probably looking at an "end of february"(ish) release

[1679992612]

1679992612

[1679992612]

1679992612

[1679992612]

1679992612

[portron]

Namecoin needs a big name integration to make it relevant... Firefox, Tor, something of that nature...

but yeah those 8 hour blocks are 

[Portnoy]

Namecoin needs a big name integration to make it relevant... Firefox, Tor, something of that nature...

If some of these things like SOPA get pushed through then NMC might become a lot more popular, causing more effort to be put into developing the tech involved with using it easily and effectively. 

[freshzive]

Can anyone comment as to what sort of payout/GH/s they're getting from this pool? Right now I'm running at around 2GH/s or higher, but only made about 1 BTC today which seems low. On ABC pool in December, I made around 1.25BTC/day from ~1.5GH/s.

Granted, difficulty has increased since then. We have also had some fairly terrible luck recently, so that may explain it as well. Obviously payout is going to have some inherit variation here due to luck as this isn't a PPS pool either.

I guess I'm just looking for someone to estimate the average BTC payout for running 1GH/s for 1 day here. Thanks!

[slider1978]

I run right around 2.2GH and I was getting between 2-2.5 BTC per day back in December. I sort of bounce between here and Deepbit and I can say that I haven't really noticed much difference in payout between the 2 with the exception of the NMC that you get here at Slush which I feel makes up for the slightly higher variance that I "feel" between deepbit and slush.

[digital]

I average around 1.5ghash and have been averaging about 1.25 btc a day since the ddos attacks...

*edit*

Obviously there has been some fluctuation though, I'm just talking averages.  And if you look at the previous couple posts, luck has been way down for the last day or two.

[tinman951]

Can anyone comment as to what sort of payout/GH/s they're getting from this pool? Right now I'm running at around 2GH/s or higher, but only made about 1 BTC today which seems low. On ABC pool in December, I made around 1.25BTC/day from ~1.5GH/s.

Granted, difficulty has increased since then. We have also had some fairly terrible luck recently, so that may explain it as well. Obviously payout is going to have some inherit variation here due to luck as this isn't a PPS pool either.

I guess I'm just looking for someone to estimate the average BTC payout for running 1GH/s for 1 day here. Thanks!

I run at 200mhash and in the past 715 hours (~30days) I have gotten 0.006223766 per hour.
1Gh/s would be 5 times that so 0.03111883 per hour or 0.74685192 per 24 hours.
Yes I keep detailed records...

I don't earn much: donations are welcome to get me started.
18b94MMTWd7bWaUWcq7VHmizgswP2dK6fM

[BinoX]

I run about 900 MHash (current rate in avatar... fluctuates between 870 and 940) and I get around 0.7BTC/day (average over the last 4 weeks)

[slush]

Granted, difficulty has increased since then. We have also had some fairly terrible luck recently, so that may explain it as well. Obviously payout is going to have some inherit variation here due to luck as this isn't a PPS pool either.

You joined the pool in very unlucky day; From the Statistics page, the luck was around 39%, which is very low. However, as you can see, monthly luck is very close to 100% (it usually fluctuates from 99% to 101%, which is expected).

[naypalm]

Gratz on 10k blocks!

[freshzive]

Thanks for all the info, going to stick with slush's pool 

[allinvain]

I few days ago my reject ratio was 0.3% and now its 2-3%, and I'm getting a lot of miner idle warnings in phoenix, is this causes by my own settings/system/upgraded phoenix + kernel or is slush getting ddosed again?

What version of phoenix are you running? I used to have the same problem as you until I upgraded to 1.7.3. Also do you have a manually set "ask rate" (in the phoenix command line argument) ?

[allinvain]

I few days ago my reject ratio was 0.3% and now its 2-3%, and I'm getting a lot of miner idle warnings in phoenix, is this causes by my own settings/system/upgraded phoenix + kernel or is slush getting ddosed again?

What version of phoenix are you running? I used to have the same problem as you until I upgraded to 1.7.3. Also do you have a manually set "ask rate" (in the phoenix command line argument) ?

I don't have a manual set ask rate, I'm using 1.7.3 and this kernel: https://bitcointalk.org/index.php?topic=25135.0

Ah that explains it. There is some bug in the latest phoenix version when running with that kernel (checkout the phoenix thread for details). I would suggest going back to phatk2 to see if it makes a difference.

[allinvain]

I few days ago my reject ratio was 0.3% and now its 2-3%, and I'm getting a lot of miner idle warnings in phoenix, is this causes by my own settings/system/upgraded phoenix + kernel or is slush getting ddosed again?

What version of phoenix are you running? I used to have the same problem as you until I upgraded to 1.7.3. Also do you have a manually set "ask rate" (in the phoenix command line argument) ?

I don't have a manual set ask rate, I'm using 1.7.3 and this kernel: https://bitcointalk.org/index.php?topic=25135.0

Ah that explains it. There is some bug in the latest phoenix version when running with that kernel (checkout the phoenix thread for details). I would suggest going back to phatk2 to see if it makes a difference.

Nope, I tried 1.7.2 again with that kernel and its still having issues.

Hmm, ok, next thing to try would be a different mining program. If you get the same issue then it must be the pool or somehow your internet connection. Does this happen on all your miners (if you have more than 1)?

Oh I forgot to mention did you also try 1.7.0?

From what I can gather in this thread: https://bitcointalk.org/index.php?topic=6458.new;topicseen#new

It seems this has something to do with PyOpenCL.

[Epoch]

Thanks for all the info, going to stick with slush's pool 

In the long run, Slush's pool (like any other) will converge to the same expected payout. Daily variances can be large, weekly as well, so don't base your decisions on that.

For your earlier question about expected per-day payout for a 1Ghash rate: at today's difficulty you can expect to get 0.784BTC (0.8BTC minus the 2% fee that Slush charges). Here's a handy calculator: http://www.alloscomp.com/bitcoin/calculator.php

[slush]

Gratz on 10k blocks!

Heh, I didn't noticed that, thanks! :-)

[slush]

damn we've been having some bad luck here the last day or so... a couple 7-8 hour blocks.
edit: 1 day pool luck is currently at 39% 

Yep, it was insane day. But we're now at 130% in one day and 99% in seven day average, which is pretty good.

[BinoX]

Hoping that the luck continues

[shad]

feature request: payout time intervall

my problem is that i want a daily payout, i am doing this right now by setting payout_limit to 7day average, but i am a little unhappy that the intervall in which my payments get send is so variable

i would like somethink like

if last_payment_time + payment_timeintervall < actual_time && payout_limit > btc_balance then
PAYOUTTIME

i think that is the easiest way to explane about what i think, no language problems in code
i think payment_timeintervall should be in days and the payout_limit which already can't be set under 0.01 afaik will secure that there aren't to tiny payouts

what do you think?

[sadpandatech]

Hmm I'm having issues again, using phoenix and phatk modified kernel: https://bitcointalk.org/index.php?topic=25135.0
 -k phatk DEVICE=0 VECTORS2 AGGRESSION=16 WORKSIZE=64 FASTLOOP=false
On a unlocked 6950, running at 930 mhz core and 1430 mhz memory.

It was working perfectly but yesterday my isp did some maintenance and now the program will only mine 9 shares and after that it "hangs"
I tried disabling long polling, went back to phoenix 1.7.2 and tried 2 different modified kernels.

If you are running the latest phatk, try removing the 'FASTLOOP=FALSE' from your arguments.
If that does not change anything try with the normal vectors, aggr, etc. i.e, 'VECTORS AGGRESSION=8 WORKSIZE=256'
That memory sounds awfully high for running vectors2 as well. Though if it worked for you in the past then it may not be the issue. I would try lowering it to about 800 if using vectors2