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

[chrysophylax]

Hello.

I am a new user of Nicehash and i am mining Quark.
Is it normal that the stats dont update ?
I mean the page i get to when clicking on my btc adress in the user list.

I see my total unpaid amount of BTC get updated but i see no hashrate or any other stats.

Have you selected appropriate algorithm and location where you mine?

Yeah i have.

https://www.nicehash.com/index.jsp?p=miners&a=12&addr=17sYY7v4MHky1xfvA4XFsNU2Ap6GzvXEvx&l=0

you are on the wrong stratum ...

try changing the 'service location' located in the upper left of the graph to 'usa ...' ...

you are actually mining on the 'westhash' stratum ...

and you are doing pretty good ...

edit - thought id add the link for you to make it easy - https://www.nicehash.com/index.jsp?p=miners&addr=17sYY7v4MHky1xfvA4XFsNU2Ap6GzvXEvx&a=12&l=1 ...

#crysx

Damn lol
I am located in Europe, i guess i should switch it ?

possibly ...

do what nicehash suggest in their docs ...

ping ALL the servers a few times and get point your miners to the one that has the LOWEST ping ...

though logically - if you are in europe - then you would generally choose the eu stratum ... but you never know what tunnel your isp is using - so the ping test is the best to find out ... i found that out ( from australia ) by doing three ping tests on each stratum to get an average - then chose the lowest ping ...

then just change your mining address accordingly ...

#crysx

Sweet, thanks for the help

no problem - hope it gets you a higher hashrate too ...

#crysx

Yeah. I will do some tests tomorrow when i have some free time. For now i let it run where it is at

edit. I switched to EU stratum now before leaving for work and it seem like i got a bit higher hashrate there.

im glad it does ...

are you using the nvidia miners and ccminer-spmod? ... i see you on his thread ...

if so - there are some commits that seem to break the hash ( and he reverts it and fixes it ) ...

so sometimes if you use the latest ccminer commit AND it doesnt seem to give the right hashrate on nicehash - just revert back to the previous build ...

sp always manages to find the issue - or some of the other devs that are contributing ...

our donation links are running fine now - and will be publishing them some time today if i get time ... they ALL go through nicehash currently and initially ALL through the eu stratum ...

ill setup the other startums ( hk - jk - us ( westhash ) ) as failover stratums when these donation links go up AND they are working well on just the eu stratum ...

for gpu mining - they work flawlessly - as long as the miners are setup properly ...

for asic miners - there has been no testing to date as i dont have any to test with ... but im guessing we will find out how it goes soon enough ... as far as i know - asics use getwork protocol and that can be activated on the stratum proxies being used ... so will see ...

#crysx

[chrysophylax]

I'm having problems connecting to the US scrypt URL. I'm using the latest (as of a week or two ago) bfgminer under Minera with a Zeus Thunder X3.

I can connect fine to the EU server.

This problem resolved itself. I don't know if it's related, but one change that I made was to shorten my worker name once I realized that it was too long.

Seems like an extra long worker name would not affect my ability to connect, but that's the only change on my end.

that sounds a little strange ...

my miners have long names too but dont have issues mining - unless nicehash themselves have maintenance downtime or issues they are fixing or upgrades to the system ...

#crysx

[tbearhere]

@ nicehash  you need to change you minimum pay that says .01btc  to .05btc ...if .05btc is the minimum.
thx

[NiceHashSupport]

@ nicehash  you need to change you minimum pay that says .01btc  to .05btc ...if .05btc is the minimum.
thx

Minimum is still 0.01.

[tbearhere]

@ nicehash  you need to change you minimum pay that says .01btc  to .05btc ...if .05btc is the minimum.
thx

Minimum is still 0.01.

Last order it didn't take it at .01btc.    ok thz

[tbearhere]

@NiceHash...can I change pools with my rented hash..or do I need to place a new order?  thx

[NiceHashSupport]

@NiceHash...can I change pools with my rented hash..or do I need to place a new order?  thx

New order.

[tokarev1972]

Anyone having problems with #xnsub flag on cgminer? I cant use #xnsub flag  with price settings, if i setup price  with extranonce enabled, pool never goes "dead" but no work issued to miner. Cgminer 4.9.0 for bitmain miners from bitmaintech repo. If i disable #xnsub, price setting work as expected, nicehash pool goes "dead" and switches to backup pool

[nicehash]

Anyone having problems with #xnsub flag on cgminer? I cant use #xnsub flag  with price settings, if i setup price  with extranonce enabled, pool never goes "dead" but no work issued to miner. Cgminer 4.9.0 for bitmain miners from bitmaintech repo. If i disable #xnsub, price setting work as expected, nicehash pool goes "dead" and switches to backup pool

This is due to incomplete implementation of xnsub patch in the bitmaintech repo (details here: https://github.com/bitmaintech/cgminer/pull/7).

If you're using AntMiner S5 we welcome you to install our patched firmware with corrected xnsub patch and also with added performance graphs. You can download if here: https://www.nicehash.com/sw/SD-S5-20150415_nicehash_perf_graphs.tar.gz

Here is an example of performance graphs:
https://www.nicehash.com/sw/SD-S5-20150415_nicehash_perf_graphs_screenshot.png

We'll soon provide updated firmwares for other AntMiners as well (S4, C1, etc.).

p.s.: based on our testing the 4.9.0 version does not work well with antminers ... use 4.8.0 instead.

[herjahto]

i cannot mining i have 2 miner Pool host: stratum.solo.nicehash.com
Pool port: 3334
Pool user: 3MvxQFxQ1kk71kC1aY9MmaQvhhptvSpJk7
Pool pass: diff_655xx
Algorithm: SHA256

Resolving pool host stratum.solo.nicehash.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 158.85.244.248:3334... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received unknown stratum message.
Received mining.notify work... OK
Received mining.set_difficulty... OK: 65536
Received authorization result... OK
i want mining Your guide custumer service,,icannot find block ini solo nice hash

[nicehash]

i cannot mining i have 2 miner Pool host: stratum.solo.nicehash.com
Pool port: 3334
Pool user: 3MvxQFxQ1kk71kC1aY9MmaQvhhptvSpJk7
Pool pass: diff_655xx
Algorithm: SHA256

Resolving pool host stratum.solo.nicehash.com... OK
Establishing connection with proxy... OK
Establishing connection with pool 158.85.244.248:3334... OK
Sending mining.subscribe... OK
Sending mining.authorize... OK
Received mining.notify subscription... OK
Received unknown stratum message.
Received mining.notify work... OK
Received mining.set_difficulty... OK: 65536
Received authorization result... OK
i want mining Your guide custumer service,,icannot find block ini solo nice hash

First of all, please change "Pool pass: diff_655xx" ... 655xx is invalid number, you should try diff_65536 instead.

Second, what exactly is your issue? Are you saying that the order is not not hashing, it's Inactive (Dead)? Please keep in mind that you have to mine long enough or with hashing power big enough to be able to quickly find a Bitcoin block due to very high Bitcoin network difficulty.

Kind regards,
NiceHash

[tbearhere]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

[NiceHashSupport]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

[elbandi]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

That's bad

There is old coin with low (<= 100M) global hashrate, coin fans cannot use you service, because a +100M hashrate will raise the difficulty more, the miner will be own enemy...

I looked the miner stats, and i can see low hashrate addresses, there is some gridseeds miners

[NiceHashSupport]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

That's bad

There is old coin with low (<= 100M) global hashrate, coin fans cannot use you service, because a +100M hashrate will raise the difficulty more, the miner will be own enemy...

I looked the miner stats, and i can see low hashrate addresses, there is some gridseeds miners

We are aware of that and solution is possible once all miners use xnsub compatible software. But as long as there are reconnects involved, we cannot never know what will be the speed of incoming miner (considering that miners may change IP or there may be multiple miners using same IP).

[tbearhere]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

I'm talking about a non ASIC algorithm.

[NiceHashSupport]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

I'm talking about a non ASIC algorithm.

Which one do you have in mind?

[tbearhere]

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

I'm talking about a non ASIC algorithm.

Which one do you have in mind?

Quark

[elbandi]

We are aware of that and solution is possible once all miners use xnsub compatible software. But as long as there are reconnects involved, we cannot never know what will be the speed of incoming miner (considering that miners may change IP or there may be multiple miners using same IP).

You can identify "old" miner by the sessionid

[NiceHashSupport]

We are aware of that and solution is possible once all miners use xnsub compatible software. But as long as there are reconnects involved, we cannot never know what will be the speed of incoming miner (considering that miners may change IP or there may be multiple miners using same IP).

You can identify "old" miner by the sessionid

Subscription id? Not used, miner never sends this data to server.

@NICEHASH  please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this  >" Limit hashing speed (0 for no limit, min. 0.1) "   to this    Limit hashing speed (0 for no limit, min. 0.05)  <    plz  thx 

We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations.

I'm talking about a non ASIC algorithm.

Which one do you have in mind?

Quark

We will consider this request.