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

[VirosaGITS]

I decided to try Lightning Asics firmware, and it works well at every other pool I've tried.  However, I get 100% rejects here.  It is CPUminer based.  Log says:
DEBUG: reject reason: Invalid extranonce2 size.

Yes you need a miner that fix the extranonce issue, as per FAQ : supported miner listed on the website. (Tho some others work, most of the times anyways. EG Cuda miner)

[evolvia31]

Can i use my simple old CGminer with this service?

No you can't.

You need only a mining software which is patched to the extranonce2 bug.

The last sgminer github version is ready, or the modded cgminer 3.7.2 release by nicehashdev is ready too.

Or if you have a specific version of cgminer, you can patch it, with this patch :
https://github.com/bitbandi/sgminer/commit/7521451cae3ffadecd007b12d1a3fe0f44e80a9a

[snooker75]

I'm new to the site, less than 24 hours.  I'm using sgminer and mining on the scrypt pool.

One thing that I've noticed is that the accepted MH/s that NiceHash is reporting on my account is about 20% lower than what my miners are reporting. 

I love the higher rates that NiceHash pays out, but if I'm being credited 20% less hash than other places, then really I need to consider that I'm only making 80% of the advertised rate.

I've played with my difficulty settings, I've tried both zuikkis kernel and the ckolivas kernel.

Are others experiencing this mysterious loss in hash?  Is there something I am doing wrong at my end?

Thanks for any help, suggestions or insight.

Snooker

[suchmoon]

I'm new to the site, less than 24 hours.  I'm using sgminer and mining on the scrypt pool.

One thing that I've noticed is that the accepted MH/s that NiceHash is reporting on my account is about 20% lower than what my miners are reporting. 

I love the higher rates that NiceHash pays out, but if I'm being credited 20% less hash than other places, then really I need to consider that I'm only making 80% of the advertised rate.

I've played with my difficulty settings, I've tried both zuikkis kernel and the ckolivas kernel.

Are others experiencing this mysterious loss in hash?  Is there something I am doing wrong at my end?

Thanks for any help, suggestions or insight.

Snooker

Check you reject percentage. Also make sure you are not just looking at the 5 min hashrate because that may have a huge variance. Look at the "Round accepted speed MH/s" and also look at the chart.

[nish2011]

Another improvement/ feature request would be the ability to increase the amount of btc on order after creating the order.

[pzero15]

I'm new to the site, less than 24 hours.  I'm using sgminer and mining on the scrypt pool.

One thing that I've noticed is that the accepted MH/s that NiceHash is reporting on my account is about 20% lower than what my miners are reporting. 

I love the higher rates that NiceHash pays out, but if I'm being credited 20% less hash than other places, then really I need to consider that I'm only making 80% of the advertised rate.

I've played with my difficulty settings, I've tried both zuikkis kernel and the ckolivas kernel.

Are others experiencing this mysterious loss in hash?  Is there something I am doing wrong at my end?

Thanks for any help, suggestions or insight.

Snooker

Check you reject percentage. Also make sure you are not just looking at the 5 min hashrate because that may have a huge variance. Look at the "Round accepted speed MH/s" and also look at the chart.

Snooker is right, same thing for me...and I'm looking at the right thing not the 5min avg.
I haven't change my config and I'm getting 600kh/s instead of usual 730kh/s with another pool.
I was able to do 730kh/s before with nicehash, so I'm pretty sure it's not our miners.

[ATCkit]

Ya this new version stops working on start up. I have returned to the Apr 15th version of sgminer-4.1.271. It gives my GPUs the best hashrate (740 khs per gpu)  i ever had.

My "5 minute accepted speed MH/s" always varies wildly compared to what my miner shows or the list shows.

My concern is this:

The "round accepted speed MH/s" is always way lower than my miner's mhs or what or the list shows for my mining rig. Should it be the same?

Also, what is Round accepted GH?  Mine seems good at 18-19 for a 2.2 MHS miner. Is that better than having a "round accepted speed MH/s" of say 0.8? Which variable is the important one?


EDIT: I don't get any rejects using the Apr 15th version of sgminer-4.1.271.

[ATCkit]

BTW, if you are wondering what config i use to get 740 khs on my 280Xs, here it is:

setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
sgminer -k zuikkis -o stratum+tcp://stratum.nicehash.com:3333 -u xxxxxxxxx -p p=4.1 x --lookup-gap 2 --thread-concurrency 8193 -g 2 -I 13 --auto-fan --gpu-fan 30-85 --temp-cutoff 90 --temp-overheat 85 --temp-target 70 --gpu-memclock 1500 --gpu-engine 1052 --gpu-powertune +1 --expiry 1 --scan-time 1 --queue 0 --no-submit-stale

[nicehashdev]

Unfortunately, we are constantly being attack with various forms of attacks. Today, someone decided to spam the service with many orders - even though, he had to pay fee for that. Someone is really investing large quantities of resources to try to harm NiceHash.

Which miners are you using that you are getting lower hashrate?

[pzero15]

Unfortunately, we are constantly being attack with various forms of attacks. Today, someone decided to spam the service with many orders - even though, he had to pay fee for that. Someone is really investing large quantities of resources to try to harm NiceHash.

Which miners are you using that you are getting lower hashrate?

Last binaries of cgminer 3.7.2 (from here) and sgminer 4.0.0

[nicehashdev]

Do you get any rejects? Where are you from? Do you submit stale shares? What about if you use other miner - as ATCkit suggested?

[ATCkit]

nicehashdev,


Two part question.

1. As i am mining with GPU's, which factor should be the most important to me?:

 a). Round accepted speed MH/s?

or

 b.) Round accepted GH ?

2. If the answer is a, should the MHS be equal to what my miner shows in the list?  Currently, it is a .200 MHS lower.

[nish2011]

I think nicehash has frozen, the orders are not changing.

[lrgbit]

same here. It stopped working about an half an hour ago.

[Taburnak]

There are some decent paying Scrypt-A-Nfactor orders ... if you have Scrypt-A-Nfactor you can get some good payouts, check here: https://www.nicehash.com/index.jsp?a=2 and point your miner to stratum+tcp://stratum.nicehash.com:3335

We advice you to use multi-algorithm configuration (if you're using latest sgminer)

"pools" : [
        {
                "name" : "NiceHash Scrypt-A.-Nfactor",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "myBTCaddress",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash Scrypt",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "myBTCaddress",
        },
        {
      "name" : "mybackuppool",
                "url" : "stratum+tcp://mybackuppool",
                "user" : "myBTCaddress",
                "pass" : "x"
        }
]
,
"kernel" : "zuikkis",
... etc ...

I have added my info to the conf file but i get errors when loading

partial JSON error in conf file
conf file could not be used
need to specify at least one pool server

[dhsc19]

There are some decent paying Scrypt-A-Nfactor orders ... if you have Scrypt-A-Nfactor you can get some good payouts, check here: https://www.nicehash.com/index.jsp?a=2 and point your miner to stratum+tcp://stratum.nicehash.com:3335

We advice you to use multi-algorithm configuration (if you're using latest sgminer)

"pools" : [
        {
                "name" : "NiceHash Scrypt-A.-Nfactor",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "myBTCaddress",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash Scrypt",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "myBTCaddress",
        },
        {
      "name" : "mybackuppool",
                "url" : "stratum+tcp://mybackuppool",
                "user" : "myBTCaddress",
                "pass" : "x"
        }
]
,
"kernel" : "zuikkis",
... etc ...

I have added my info to the conf file but i get errors when loading

partial JSON error in conf file
conf file could not be used
need to specify at least one pool server

Make sure you have commas where there needs to be and no commas where there doesn't need to be.  Also, same with the brackets.  I get that message when I've messed up those.

[BombaUcigasa]

Unfortunately, we are constantly being attack with various forms of attacks. Today, someone decided to spam the service with many orders - even though, he had to pay fee for that. Someone is really investing large quantities of resources to try to harm NiceHash.

Not only that but I did a little math and you only gain something like 260$ a month, this might cover the technological costs but what about the development time and support? What are your future expectations and plans?

[Ajeto]

Nicehash is back working, but now getting mostly
"Stratum from stratum.nicehash.com requested work restart"

at least before we got switched to failover pool

[Taburnak]

There are some decent paying Scrypt-A-Nfactor orders ... if you have Scrypt-A-Nfactor you can get some good payouts, check here: https://www.nicehash.com/index.jsp?a=2 and point your miner to stratum+tcp://stratum.nicehash.com:3335

We advice you to use multi-algorithm configuration (if you're using latest sgminer)

"pools" : [
        {
                "name" : "NiceHash Scrypt-A.-Nfactor",
                "url" : "stratum+tcp://stratum.nicehash.com:3335",
                "user" : "myBTCaddress",
                "algorithm" : "nscrypt",
                "nfactor" : "11"
        },
        {
                "name" : "NiceHash Scrypt",
                "url" : "stratum+tcp://stratum.nicehash.com:3333",
                "user" : "myBTCaddress",
        },
        {
      "name" : "mybackuppool",
                "url" : "stratum+tcp://mybackuppool",
                "user" : "myBTCaddress",
                "pass" : "x"
        }
]
,
"kernel" : "zuikkis",
... etc ...

I have added my info to the conf file but i get errors when loading

partial JSON error in conf file
conf file could not be used
need to specify at least one pool server

Make sure you have commas where there needs to be and no commas where there doesn't need to be.  Also, same with the brackets.  I get that message when I've messed up those.

thanks but i dont know how to do that. i want to setup for Nscrypt but if i change my port to 3335 i get share is above target. i followed the faq on the nicehash website. it works fine in scrypt mode with this bat with no conf file.

setx GPU_MAX_ALLOC_PERCENT 100  

sgminer -o stratum+tcp://stratum.nicehash.com:3333 -u 1CrpGPyvWdGuirFTN7ky62bLvYEW1gZUuZ -p d=64 -o stratum+tcp://useast.wafflepool.com:3333 -u 1CrpGPyvWdGuirFTN7ky62bLvYEW1gZUuZ -p password --thread-concurrency 8192 --intensity 13 --worksize 256 -g 2 --temp-target 70 --gpu-memclock 1500 --gpu-engine 1080 --gpu-fan 80

[nicehashdev]

Nicehash is back working, but now getting mostly
"Stratum from stratum.nicehash.com requested work restart"

at least before we got switched to failover pool

Work restart is nothing abnormal - looks like one of customers pool is switching work fast. It may influence your shares being stale, but NiceHash will treat your stale share accepted even when it is too late (for up to 800 msec).

nicehashdev,


Two part question.

1. As i am mining with GPU's, which factor should be the most important to me?:

 a). Round accepted speed MH/s?

or

 b.) Round accepted GH ?

2. If the answer is a, should the MHS be equal to what my miner shows in the list?  Currently, it is a .200 MHS lower.

Each round lasts 6 hours. From one mass payment to another. If you have your miner hooked to NiceHash from one payment to another, then looking at round speed might be better - it is less jumpy. But if you come in in the middle, then round speed will not be correct until at least one payment is made.