nicehash payout is so low this days on SHA-256
not worth renting here anymore
back in the days payout was constantly 10-20 % more
now payouts are in the red zone
Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 211. (Read 794394 times)
December 25, 2014, 10:34:02 AM
December 25, 2014, 10:01:38 AM
X11 Pool up again...
Scrypt not so good yet.
Scrypt not so good yet.
December 25, 2014, 08:59:26 AM
Pool down?
Yep, another multipool down, as seen with wafflepool.
I will stop mining, doesn't worth it anymore, low profit, bad pools, BTC price crash, game over for us.
December 25, 2014, 08:43:10 AM
Pool down?
December 25, 2014, 06:42:40 AM
I did a short test with the original cgminer on the s1, but currently I think it also shows the same problems.
my S3 behave a little bit better with the payout threshold, but not 100%
my S3 behave a little bit better with the payout threshold, but not 100%
Which binary for AntMiner S1 are you using? You should use the latest version from our download page (https://www.nicehash.com/index.jsp?p=software#cgminer) because the first version that was provided by 7queue indeed had the idlebug ... but this should be fixed in the latest version from our download page. If you still having issues you could maybe ask 7queue to look into it at this thread: https://bitcointalksearch.org/topic/cgminer-extranoncesubscribe-extension-binaries-available-for-download-850620
Yes, I was using that version from your site, assuming it has not changed in the last 1-2 Weeks.
thanks for your advices
December 25, 2014, 01:50:24 AM
I did a short test with the original cgminer on the s1, but currently I think it also shows the same problems.
my S3 behave a little bit better with the payout threshold, but not 100%
my S3 behave a little bit better with the payout threshold, but not 100%
Which binary for AntMiner S1 are you using? You should use the latest version from our download page (https://www.nicehash.com/index.jsp?p=software#cgminer) because the first version that was provided by 7queue indeed had the idlebug ... but this should be fixed in the latest version from our download page. If you still having issues you could maybe ask 7queue to look into it at this thread: https://bitcointalksearch.org/topic/cgminer-extranoncesubscribe-extension-binaries-available-for-download-850620
We don't have AntMiners S1 in our lab, but we do have AntMiners S3 as well as Spondoolies SP20s and we can confirm that the binaries for S3 and SP20 are working 100% correct with extranonce.subscribe and price-limitation switching.
I got the S3 cgminer from your site and it works great. Idlebug is gone. Thanks!
December 24, 2014, 07:12:43 PM
I did a short test with the original cgminer on the s1, but currently I think it also shows the same problems.
my S3 behave a little bit better with the payout threshold, but not 100%
my S3 behave a little bit better with the payout threshold, but not 100%
Which binary for AntMiner S1 are you using? You should use the latest version from our download page (https://www.nicehash.com/index.jsp?p=software#cgminer) because the first version that was provided by 7queue indeed had the idlebug ... but this should be fixed in the latest version from our download page. If you still having issues you could maybe ask 7queue to look into it at this thread: https://bitcointalksearch.org/topic/cgminer-extranoncesubscribe-extension-binaries-available-for-download-850620
We don't have AntMiners S1 in our lab, but we do have AntMiners S3 as well as Spondoolies SP20s and we can confirm that the binaries for S3 and SP20 are working 100% correct with extranonce.subscribe and price-limitation switching.
This explains my issue exactly, but I am using your cgminer for S1's downloaded from your site. Your cgminer for S3's and SP20's seem to work great on my miners. Whats strange it also does it in bfgminer proxy.
December 24, 2014, 11:38:25 AM
Fresh sgminer binaries with optimized Lyra2RE algorithm (by djm34) and support for multi-algo are available: https://www.nicehash.com/index.jsp?p=software#sgminer (thanks badman74 for windows build). Do not forget to include ";f9=1.5" to the password parameter of your NiceHash multi-algo configuration if you want to enable Lyra2RE for multi-algo.
I have problems with my eyes.
I see only sgminer-5.1-dev-2014-11-13-win32.zip that does not work with l2re
Sorry, our software page was accidentally reverted to an older revision ... we fixed that now and you can download the sgminer-5.1-2014-12-20 binaries.
December 24, 2014, 10:33:43 AM
Fresh sgminer binaries with optimized Lyra2RE algorithm (by djm34) and support for multi-algo are available: https://www.nicehash.com/index.jsp?p=software#sgminer (thanks badman74 for windows build). Do not forget to include ";f9=1.5" to the password parameter of your NiceHash multi-algo configuration if you want to enable Lyra2RE for multi-algo.
I have problems with my eyes.
I see only sgminer-5.1-dev-2014-11-13-win32.zip that does not work with l2re
December 23, 2014, 11:14:20 AM
I did a short test with the original cgminer on the s1, but currently I think it also shows the same problems.
my S3 behave a little bit better with the payout threshold, but not 100%
my S3 behave a little bit better with the payout threshold, but not 100%
Which binary for AntMiner S1 are you using? You should use the latest version from our download page (https://www.nicehash.com/index.jsp?p=software#cgminer) because the first version that was provided by 7queue indeed had the idlebug ... but this should be fixed in the latest version from our download page. If you still having issues you could maybe ask 7queue to look into it at this thread: https://bitcointalksearch.org/topic/cgminer-extranoncesubscribe-extension-binaries-available-for-download-850620
We don't have AntMiners S1 in our lab, but we do have AntMiners S3 as well as Spondoolies SP20s and we can confirm that the binaries for S3 and SP20 are working 100% correct with extranonce.subscribe and price-limitation switching.
December 23, 2014, 03:26:11 AM
I did a short test with the original cgminer on the s1, but currently I think it also shows the same problems.
my S3 behave a little bit better with the payout threshold, but not 100%
my S3 behave a little bit better with the payout threshold, but not 100%
December 22, 2014, 11:00:20 PM
dear nicehash,
is it possible that the cgminer binary you supply for antminer s1 enabling #xnsub option is not able to correctly failover to another pool with the "p=0.0120" minimum payment theshold option in the password? pool is not shown or recognized as "dead" when current payment falls below the value. instead it is alive but delivers zero shares to the s1 miner.
using latest firmware cgminer from s1 does not show that effect.
any ideas?
is it possible that the cgminer binary you supply for antminer s1 enabling #xnsub option is not able to correctly failover to another pool with the "p=0.0120" minimum payment theshold option in the password? pool is not shown or recognized as "dead" when current payment falls below the value. instead it is alive but delivers zero shares to the s1 miner.
using latest firmware cgminer from s1 does not show that effect.
any ideas?
I am plagued with the exact same problem. What exactly happens is Nicehash releases the miners, they go over to the Guild for a minute or two, then Nicehash calls them back but holds them there and gives them no work.
I don't think it's the extranonce subscription that causes it because the miners do the same thing without that. I'm using S3's so I don't think it's something that's happening in our equipment, but at Nicehash. I'd greatly appreciate an answer to this too.
I too am having the same problem. I have also tried through bfgminer using a proxy. Same issue. Cgminer on the S1's reports both pools being alive. Then they sit there waiting for work not hashing.
December 22, 2014, 09:09:19 PM
dear nicehash,
is it possible that the cgminer binary you supply for antminer s1 enabling #xnsub option is not able to correctly failover to another pool with the "p=0.0120" minimum payment theshold option in the password? pool is not shown or recognized as "dead" when current payment falls below the value. instead it is alive but delivers zero shares to the s1 miner.
using latest firmware cgminer from s1 does not show that effect.
any ideas?
is it possible that the cgminer binary you supply for antminer s1 enabling #xnsub option is not able to correctly failover to another pool with the "p=0.0120" minimum payment theshold option in the password? pool is not shown or recognized as "dead" when current payment falls below the value. instead it is alive but delivers zero shares to the s1 miner.
using latest firmware cgminer from s1 does not show that effect.
any ideas?
I am plagued with the exact same problem. What exactly happens is Nicehash releases the miners, they go over to the Guild for a minute or two, then Nicehash calls them back but holds them there and gives them no work.
I don't think it's the extranonce subscription that causes it because the miners do the same thing without that. I'm using S3's so I don't think it's something that's happening in our equipment, but at Nicehash. I'd greatly appreciate an answer to this too.
December 22, 2014, 07:15:25 PM
dear nicehash,
is it possible that the cgminer binary you supply for antminer s1 enabling #xnsub option is not able to correctly failover to another pool with the "p=0.0120" minimum payment theshold option in the password? pool is not shown or recognized as "dead" when current payment falls below the value. instead it is alive but delivers zero shares to the s1 miner.
using latest firmware cgminer from s1 does not show that effect.
any ideas?
is it possible that the cgminer binary you supply for antminer s1 enabling #xnsub option is not able to correctly failover to another pool with the "p=0.0120" minimum payment theshold option in the password? pool is not shown or recognized as "dead" when current payment falls below the value. instead it is alive but delivers zero shares to the s1 miner.
using latest firmware cgminer from s1 does not show that effect.
any ideas?
December 22, 2014, 11:01:36 AM
Fresh sgminer binaries with optimized Lyra2RE algorithm (by djm34) and support for multi-algo are available: https://www.nicehash.com/index.jsp?p=software#sgminer (thanks badman74 for windows build). Do not forget to include ";f9=1.5" to the password parameter of your NiceHash multi-algo configuration if you want to enable Lyra2RE for multi-algo.
Very nice. Is the keccak unroll problem fixed? In the latest dailies keccak unroll was ignored, the bins that were produced did not contain ....ku0.bin, for example.
December 22, 2014, 05:13:28 AM
question I did the wonderful paycoin rush.
I earned 2.8 or maybe 3.0 btc coins vs .8 btc coins
I was doing so well in did not try to do the Extranonce subscription with the 6 sp20's as I was afraid to brick an sp20 with payoffs so high.
Now that payoffs are close to normal how do I load or activate Extranonce subscription
Thanks in advance , Phil
I earned 2.8 or maybe 3.0 btc coins vs .8 btc coins
I was doing so well in did not try to do the Extranonce subscription with the 6 sp20's as I was afraid to brick an sp20 with payoffs so high.
Now that payoffs are close to normal how do I load or activate Extranonce subscription
Thanks in advance , Phil
use this: https://github.com/Stratehm/stratum-proxy/releases
December 22, 2014, 02:56:17 AM
Fresh sgminer binaries with optimized Lyra2RE algorithm (by djm34) and support for multi-algo are available: https://www.nicehash.com/index.jsp?p=software#sgminer (thanks badman74 for windows build). Do not forget to include ";f9=1.5" to the password parameter of your NiceHash multi-algo configuration if you want to enable Lyra2RE for multi-algo.
December 21, 2014, 10:22:32 PM
Seems like there was a change in the last couple days that effected the difficulty. The difficulty for my miners has been much higher than normal. Anyone else seeing this? My S4's in the past typically had a difficulty of 4096 (even though I have d=2048). But now they are at 8192. And my 1TH/s miners went from 2048 to 4096. Pretty much doubled, for all miners. I know that overall the payout is the same, but it made the graphs very "jumpy" and at first I thought there was a problem. Actually, as I look again while typing this, the reject rate has increased, starting 1.5-2 days ago. I'm just wondering if there is an issue on my end.
I've got a few S1's and several S3's on westhash and have seen the same increase in difficulty you have, but at lower numbers. I used to see sub-1000 difficulty but all of them are now 1024 or 2048, which is not normal.
So I'd guess that no, it's not an issue on your end of the connection.
1Neptune, thanks for confirming. Looking at Westhash's stats for the last 7 days, I'm guessing they increased the difficulty to handle the huge increase in hashrate, to nearly 5.5 PH/s. Since higher difficulty decreases network traffic and server utilization.
December 21, 2014, 06:12:52 PM
Seems like there was a change in the last couple days that effected the difficulty. The difficulty for my miners has been much higher than normal. Anyone else seeing this? My S4's in the past typically had a difficulty of 4096 (even though I have d=2048). But now they are at 8192. And my 1TH/s miners went from 2048 to 4096. Pretty much doubled, for all miners. I know that overall the payout is the same, but it made the graphs very "jumpy" and at first I thought there was a problem. Actually, as I look again while typing this, the reject rate has increased, starting 1.5-2 days ago. I'm just wondering if there is an issue on my end.
I've got a few S1's and several S3's on westhash and have seen the same increase in difficulty you have, but at lower numbers. I used to see sub-1000 difficulty but all of them are now 1024 or 2048, which is not normal.
So I'd guess that no, it's not an issue on your end of the connection.
December 21, 2014, 01:49:04 PM
Seems like there was a change in the last couple days that effected the difficulty. The difficulty for my miners has been much higher than normal. Anyone else seeing this? My S4's in the past typically had a difficulty of 4096 (even though I have d=2048). But now they are at 8192. And my 1TH/s miners went from 2048 to 4096. Pretty much doubled, for all miners. I know that overall the payout is the same, but it made the graphs very "jumpy" and at first I thought there was a problem. Actually, as I look again while typing this, the reject rate has increased, starting 1.5-2 days ago. I'm just wondering if there is an issue on my end.
Jump to: