[ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool

[Sigals]

Guys, why are there so many work restart requests? I get 2 minutes worth of restarts in between accepts? This is on scrypt, and it works fine on other pools. Any ideas?

I would like to know this as well.

[toxic0n]

Website down?

Code:

Error 522 Ray ID: 12d2e960476b0436
Connection timed out
You
Browser
Working
Chicago
CloudFlare
Working
www.nicehash.com
Host
Error

[ryen123]

Everything is down

[x8008]

site is down.. is mining affected?

[saykor]

Hi
I download latest version of SGMiner from xxx

And have this error when start it:

Code:

[23:23:09] Started sgminer 4.1.271-nicehash-9

[23:23:09] "C:\Users\miner1\AppData\Local\Temp\OCL8A6C.tmp.cl", line 79: catastr
ophic error:
          cannot open source file "blake.cl"
  #include "blake.cl"
                     ^

1 catastrophic error detected in the compilation of "C:\Users\miner1\AppData\Loc
a
[23:23:09] Failed to init GPU thread 0, disabling device 0
[23:23:09] Restarting the GPU from the menu will not fix this.
[23:23:09] Re-check your configuration and try restarting.
Press enter to continue:

the bat file is:
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u xxxxx -p x -I 13 -w 256 --thread-concurrency 8192 -g 2 --gpu-engine 1075 --gpu-memclock 1500

os: win7

Can someone help pls.

[ryen123]

Hi
I download latest version of SGMiner from xxx

And have this error when start it:

Code:

[23:23:09] Started sgminer 4.1.271-nicehash-9

[23:23:09] "C:\Users\miner1\AppData\Local\Temp\OCL8A6C.tmp.cl", line 79: catastr
ophic error:
          cannot open source file "blake.cl"
  #include "blake.cl"
                     ^

1 catastrophic error detected in the compilation of "C:\Users\miner1\AppData\Loc
a
[23:23:09] Failed to init GPU thread 0, disabling device 0
[23:23:09] Restarting the GPU from the menu will not fix this.
[23:23:09] Re-check your configuration and try restarting.
Press enter to continue:

the bat file is:
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u xxxxx -p x -I 13 -w 256 --thread-concurrency 8192 -g 2 --gpu-engine 1075 --gpu-memclock 1500

os: win7

Can someone help pls.

File sgminer-4.1.271-nicehash-9 is for Scrypt/Scrypt-N only
File sph-sgminer-4.1.0-nicehash-2 is for X11 algorithm

[saykor]

Hi
I download latest version of SGMiner from xxx

And have this error when start it:

Code:

[23:23:09] Started sgminer 4.1.271-nicehash-9

[23:23:09] "C:\Users\miner1\AppData\Local\Temp\OCL8A6C.tmp.cl", line 79: catastr
ophic error:
          cannot open source file "blake.cl"
  #include "blake.cl"
                     ^

1 catastrophic error detected in the compilation of "C:\Users\miner1\AppData\Loc
a
[23:23:09] Failed to init GPU thread 0, disabling device 0
[23:23:09] Restarting the GPU from the menu will not fix this.
[23:23:09] Re-check your configuration and try restarting.
Press enter to continue:

the bat file is:
sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u xxxxx -p x -I 13 -w 256 --thread-concurrency 8192 -g 2 --gpu-engine 1075 --gpu-memclock 1500

os: win7

Can someone help pls.

File sgminer-4.1.271-nicehash-9 is for Scrypt/Scrypt-N only
File sph-sgminer-4.1.0-nicehash-2 is for X11 algorithm

Thank you. It works now.

[suchmoon]

Hey guys, I'm using this setting to sgminer for nicehash

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
. \ sgminer \ sgminer-k-o darkcoin stratum+tcp://stratum.nicehash.com:3336 username.workername-u-p password-I 18-g-w 128 4

I want to know if it's good or i must change something. Thanks

It doesn't look right. Should be something like this:

Code:

sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u btc_address -p x -I 18 -w 128 -g 4

Although -g 4 looks too high to me.

[basilisk]

Hey guys, I'm using this setting to sgminer for nicehash

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
. \ sgminer \ sgminer-k-o darkcoin stratum+tcp://stratum.nicehash.com:3336 username.workername-u-p password-I 18-g-w 128 4

I want to know if it's good or i must change something. Thanks

It doesn't look right. Should be something like this:

Code:

sgminer -k darkcoin -o stratum+tcp://stratum.nicehash.com:3336 -u btc_address -p x -I 18 -w 128 -g 4

Although -g 4 looks too high to me.

Yep, that had changed (about g4). On the command line, it had not changed. I'll try that. Thank you so much

[comeonalready]

There is a *new* and *different* bug that is impacting cgminer v3.4.2a+ and NiceHash ... I'm experiencing it on numerous boxes, and am trying to find a fix.  This is *NOT* the "idle bug" or it is not completely fixed in cgminer.

I'm mining SHA and when running using the "price" option in the password - p=0.07 - and letting it run for long periods of time, suddenly the NiceHash pool will appear in the miner as "Alive" ... but the pool is not passing any work, and the threshold has NOT been hit!  There are NO contracts for 0.07 ...

This is now easily reproducible on more than one box, and they are running the latest cgminer that does contain the "idle bug" fix.

I am trying now to debug the protocol, and determine exactly *WHY* cgminer would believe - when sending the miner.subscribe and miner.authorize requests - believe that the pool is alive.

When this happens my miners are sitting idle - believing they are connected to an active pool, but not being given any work.  Today I have lost hours of mining when I have come back to check the status of my miners and found them in this state.

I have reached out to NiceHash, ckolivas and kano for assistance, but any other assistance in debugging the protocol or cgminer would be appreciated.  Until I can know exactly how NiceHash is handling the protocol requests, it is very difficult to debug cgminer to see what is going on.

This is because nicehash never addressed the true cause of the original "idle bug", but only applied a hacky fix to eliminate one of its symptoms.  I had offered them the real solution to the problem quite some time ago but they declined.  And I would bet this this problem is happening to many more of their miners, but you're just one who noticed it and decided to stay and investigate rather than simply taking your hashpower elsewhere.

Everyone pointing their miners at nicehash should keep a very close watch on them to ensure that they are not unexpectedly going idle.
 

[nicehashdev]

When I offered you a job...:

Job offering posted, if you are interesting. 1 BTC for 1 day of work: https://bitcointalk.org/index.php?topic=580718.new#new

Yeah, I'm not your man on that.  I wouldn't get out of bed for 1 BTC these days.  But if I do find the problem I'll send it to you for free, as I am close.  I like the subscribe.extranonce1 protocol extension.

[xsoft]

Hi, Im getting too much Rejected on X11. Like 10-50%. Is this common?
I tried to decrease diff (to d=0.5 .. d=2) but still its pretty much by my opinion.

Im on sgminer 4.1.271-nicehash-9 (Linux). Yes? I can mine X11 (its not scrypt/100% rejection issue).

[trc]

Hi, Im getting too much Rejected on X11. Like 10-50%. Is this common?
I tried to decrease diff (to d=0.5 .. d=2) but still its pretty much by my opinion.

Im on sgminer 4.1.271-nicehash-9 (Linux). Yes? I can mine X11 (its not scrypt/100% rejection issue).

It's from d=0.01 to d=0.10 and, I'm not sure if you're using the correct miner. Try sph-sgminer for X11. https://www.nicehash.com/software/ 3rd group.

[Sigals]

There is a *new* and *different* bug that is impacting cgminer v3.4.2a+ and NiceHash ... I'm experiencing it on numerous boxes, and am trying to find a fix.  This is *NOT* the "idle bug" or it is not completely fixed in cgminer.

I'm mining SHA and when running using the "price" option in the password - p=0.07 - and letting it run for long periods of time, suddenly the NiceHash pool will appear in the miner as "Alive" ... but the pool is not passing any work, and the threshold has NOT been hit!  There are NO contracts for 0.07 ...

This is now easily reproducible on more than one box, and they are running the latest cgminer that does contain the "idle bug" fix.

I am trying now to debug the protocol, and determine exactly *WHY* cgminer would believe - when sending the miner.subscribe and miner.authorize requests - believe that the pool is alive.

When this happens my miners are sitting idle - believing they are connected to an active pool, but not being given any work.  Today I have lost hours of mining when I have come back to check the status of my miners and found them in this state.

I have reached out to NiceHash, ckolivas and kano for assistance, but any other assistance in debugging the protocol or cgminer would be appreciated.  Until I can know exactly how NiceHash is handling the protocol requests, it is very difficult to debug cgminer to see what is going on.

This is because nicehash never addressed the true cause of the original "idle bug", but only applied a hacky fix to eliminate one of its symptoms.  I had offered them the real solution to the problem quite some time ago but they declined.  And I would bet this this problem is happening to many more of their miners, but you're just one who noticed it and decided to stay and investigate rather than simply taking your hashpower elsewhere.

Everyone pointing their miners at nicehash should keep a very close watch on them to ensure that they are not unexpectedly going idle.
 

This just happened to me - got home and my miner was idle... not happy.

What is the "proper" fix for this?

[nicehashdev]

https://www.nicehash.com/software/

[Sigals]

https://www.nicehash.com/software/

I was already using sgminer nicehash version 8 - is this fixed for sure in version 9?

[punisher1]

i`m getting today :
"JSON KEY 'DATA' NOT FOUND"
"JSON INVAL DATA"

why ?

[comeonalready]

When I offered you a job...:

Job offering posted, if you are interesting. 1 BTC for 1 day of work: https://bitcointalk.org/index.php?topic=580718.new#new

Yeah, I'm not your man on that.  I wouldn't get out of bed for 1 BTC these days.  But if I do find the problem I'll send it to you for free, as I am close.  I like the subscribe.extranonce1 protocol extension.

If you want to live in the past, fine.  When I offered you the proper solution for only 0.25BTC:
 

Does this fork of sgminer address the idle bug, or is that still a work in progress?

Work in progress.

Several days ago I was investigating this idle bug to satisfy my own curiosity and offered to provide the fix to you for free if I found it.  I found and fixed it two days ago, but you had already hired someone else to do the work instead, so obviously I can no longer give it away for nothing.  Today, that person contacted me for some information about the bug, so I assume he has not yet found it.  I have no doubt that he or someone else eventually will, but how long it will take is anyone's guess, as it is nested pretty deeply in the muck.

I offered the fix to you for a token amount -- a quarter of what you were paying him -- and also to send the fix in advance of payment for verification, but you declined.  So how long it remains a work in progress is really up to you...

By the way, it took the person you hired weeks to do the work you said would only take a day, and it's still not done correctly!

All over 0.25BTC.  Nothing.  A pittance.  A poor decision made out of being too stubborn to even consider the potential future effects upon the profitability of nicehash and the satisfaction level of miners providing their hashpower.  For without the miners, nicehash has nothing to sell.  And some of them are not happy!  Most probably just pointed their hashpower elsewhere without bothering to voice their issues here.

I will repeat.  Everyone pointing their miners at nicehash should keep a very close watch over them to ensure that they are not unexpectedly going idle.  If you don't want to take the risk that they will go idle, then you should run your usual profitability calculations and choose for yourself whether you should be mining somewhere else instead.

[trc]

It's none of my business but you guys should settle this already. Comeonalready, name your price (current) for the job and let them consider (again). Do this via PMs or a zillion other ways preferably and be happy with the outcome. Deal or not.
A- Both parties reach an agreement, you get the job done and get your payment.
B- No deal. You'll know you aren't wasting your time with the subject here and move on with your life, where, 1 BTC isn't worth getting out of bed. No pun intended. That's quite the heaven for 99.9% of the world. Make more use of it man.

[comeonalready]

It's none of my business but you guys should settle this already. Comeonalready, name your price (current) for the job and let them consider (again). Do this via PMs or a zillion other ways preferably and be happy with the outcome. Deal or not.
A- Both parties reach an agreement, you get the job done and get your payment.
B- No deal. You'll know you aren't wasting your time with the subject here and move on with your life, where, 1 BTC isn't worth getting out of bed. No pun intended. That's quite the heaven for 99.9% of the world. Make more use of it man.

My price is 0 BTC.  For whatever perverse reason, at this point I prefer to see them spin their wheels addressing these very same issues over and over and over and over again.  I am amused by how people with such a good idea for a service could make a series of incredibly poor decisions.  They voluntarily chose to handicap themselves for nearly nothing!  Does no one else find this as interesting as I do?

I will not chime in on this topic again -- if the rest of you can keep your comments to yourself -- which I greatly doubt you can.  For what it's worth, I do hope you all surprise me though.

PS. Want to know the secret of how 1 BTC is not worth getting out of bed?  Make good decisions when presented with opportunities in life!