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

[pallas]

Vertcoin is forking to a new mining algo, a modified lyra2re.
Will you add a new algo or replace the old one (or none of the two)?

Huh, these guys at Vertcoin are really fanatic with those algo forks ... we'll take a look at it and we'll probably add the new algo.

can we still use the same miner ( ccminer-spmod or sgminer-pallas ) to mine? ...

or is this modification to the algo be one where we need a new miner to even get a look at? ...

#crysx

The miner needs to be updated. As soon as they release the official GPU miners (don't wonna do the work twice) I'll take a look and see if I can make a fine mod out of it ;-)

[chrysophylax]

Vertcoin is forking to a new mining algo, a modified lyra2re.
Will you add a new algo or replace the old one (or none of the two)?

Huh, these guys at Vertcoin are really fanatic with those algo forks ... we'll take a look at it and we'll probably add the new algo.

can we still use the same miner ( ccminer-spmod or sgminer-pallas ) to mine? ...

or is this modification to the algo be one where we need a new miner to even get a look at? ...

#crysx

The miner needs to be updated. As soon as they release the official GPU miners (don't wonna do the work twice) I'll take a look and see if I can make a fine mod out of it ;-)

that would be fantastic mate ...

private or opensourced - that is the question i would think ...

donation servers are almost done - with the other two still giving me issues ... may have to destroy those ones and start again ...

hopefully will resolve these issues tonight ...

#crysx

[pallas]

Vertcoin is forking to a new mining algo, a modified lyra2re.
Will you add a new algo or replace the old one (or none of the two)?

Huh, these guys at Vertcoin are really fanatic with those algo forks ... we'll take a look at it and we'll probably add the new algo.

can we still use the same miner ( ccminer-spmod or sgminer-pallas ) to mine? ...

or is this modification to the algo be one where we need a new miner to even get a look at? ...

#crysx

The miner needs to be updated. As soon as they release the official GPU miners (don't wonna do the work twice) I'll take a look and see if I can make a fine mod out of it ;-)

that would be fantastic mate ...

private or opensourced - that is the question i would think ...

donation servers are almost done - with the other two still giving me issues ... may have to destroy those ones and start again ...

hopefully will resolve these issues tonight ...

#crysx

That depends on how much time I'll dedicate to it and how much of a gain I can achieve vs the public miner.
Thanks for your effort on the donation servers!

[thedreamer]

Anyone having issues with NiceHashBot?

It doesn't move up the price , even though the max price is set higher, so it's stuck at the minimum started at.

Also the starting BTC amount is always different than what I set it at initially.

Anyone else ?

[NiceHashSupport]

Anyone having issues with NiceHashBot?

It doesn't move up the price , even though the max price is set higher, so it's stuck at the minimum started at.

Also the starting BTC amount is always different than what I set it at initially.

Anyone else ?

Are you using latest version?

[thedreamer]

Anyone having issues with NiceHashBot?

It doesn't move up the price , even though the max price is set higher, so it's stuck at the minimum started at.

Also the starting BTC amount is always different than what I set it at initially.

Anyone else ?

Are you using latest version?

Yup, just updated.

[NiceHashSupport]

Anyone having issues with NiceHashBot?

It doesn't move up the price , even though the max price is set higher, so it's stuck at the minimum started at.

Also the starting BTC amount is always different than what I set it at initially.

Anyone else ?

Are you using latest version?

Yup, just updated.

Open issue with details here: https://github.com/nicehash/NiceHashBot/issues

We were not able to replicate issues you are claiming.

[thedreamer]

Open issue with details here: https://github.com/nicehash/NiceHashBot/issues

We were not able to replicate issues you are claiming.

No biggie as I can order manually for no, but just playing with the nicehashbot to see how it works..

[PeaMine]

On the miner supplier side, other than setting different pools, is there a way to have a single miner jump between US and EU sections as providers?
Such as an autoswitching URL for a certain algorithm.  Right now I don't want to set a min price, but would like my miner to jump between EU and US depending on which is most profitable.

[nicehash]

On the miner supplier side, other than setting different pools, is there a way to have a single miner jump between US and EU sections as providers?
Such as an autoswitching URL for a certain algorithm.  Right now I don't want to set a min price, but would like my miner to jump between EU and US depending on which is most profitable.

There is no need to jump between USA and EU stratum servers if your are a miner (seller). Please note that you're paid at the current globally weighted average price - in other words - you're paid the same regardless on which location (stratum server/proxy) you're connected. Just make sure to connect your miner to the closest stratum/proxy server to get best efficiency (check also this FAQ: https://www.nicehash.com/index.jsp?p=faq#faqs13) and use closest location as your primary pool and other location as your secondary (backup) pool in your miner's configuration.

Kind regards,
NiceHash

[nicehash]

In case you missed the News about Axiom miner: we have released faster CPU miner for Axiom. How fast does it go? You will be able to hash 80-120% faster than before, depending on what kind of CPU you have. More info here: https://www.nicehash.com/index.jsp?p=news&id=23

edit: Our team is further pushing limits of Axiom CPU mining. This time, we were able to achieve outstanding 241% speed improvement compared to original Axiom miner. Furthermore, we packed miner together with a nice&slim launcher for easy CPU mining and real-time statistics from NiceHash. More info here: https://www.nicehash.com/index.jsp?p=news&id=25

[Jake-R]

In case you missed the News about Axiom miner: we have released faster CPU miner for Axiom. How fast does it go? You will be able to hash 80-120% faster than before, depending on what kind of CPU you have. More info here: https://www.nicehash.com/index.jsp?p=news&id=23

edit: Our team is further pushing limits of Axiom CPU mining. This time, we were able to achieve outstanding 241% speed improvement compared to original Axiom miner. Furthermore, we packed miner together with a nice&slim launcher for easy CPU mining and real-time statistics from NiceHash. More info here: https://www.nicehash.com/index.jsp?p=news&id=25

You guys are doing an awesome job with this new coin. I have been Axiom mining with this new miner all day and just started getting these errors, is anybody else getting them? How do you resolve this? I have restarted my router and PC.

[NiceHashSupport]

In case you missed the News about Axiom miner: we have released faster CPU miner for Axiom. How fast does it go? You will be able to hash 80-120% faster than before, depending on what kind of CPU you have. More info here: https://www.nicehash.com/index.jsp?p=news&id=23

edit: Our team is further pushing limits of Axiom CPU mining. This time, we were able to achieve outstanding 241% speed improvement compared to original Axiom miner. Furthermore, we packed miner together with a nice&slim launcher for easy CPU mining and real-time statistics from NiceHash. More info here: https://www.nicehash.com/index.jsp?p=news&id=25

You guys are doing an awesome job with this new coin. I have been Axiom mining with this new miner all day and just started getting these errors, is anybody else getting them? How do you resolve this? I have restarted my router and PC.

Contact support with your IP, maybe you have been banned.

[Jake-R]

In case you missed the News about Axiom miner: we have released faster CPU miner for Axiom. How fast does it go? You will be able to hash 80-120% faster than before, depending on what kind of CPU you have. More info here: https://www.nicehash.com/index.jsp?p=news&id=23

edit: Our team is further pushing limits of Axiom CPU mining. This time, we were able to achieve outstanding 241% speed improvement compared to original Axiom miner. Furthermore, we packed miner together with a nice&slim launcher for easy CPU mining and real-time statistics from NiceHash. More info here: https://www.nicehash.com/index.jsp?p=news&id=25

You guys are doing an awesome job with this new coin. I have been Axiom mining with this new miner all day and just started getting these errors, is anybody else getting them? How do you resolve this? I have restarted my router and PC.

Contact support with your IP, maybe you have been banned.

The problem resolved itself yesterday. At least one other user was experiencing this issue as well and posted in another thread.

[Blawpaw]

Hi, there
I have used your services over and over to mine several algorithms and always been very pleased.
If you are looking to rent mining rigs this is surely the right place for you

[dhsc19]

In case you missed the News about Axiom miner: we have released faster CPU miner for Axiom. How fast does it go? You will be able to hash 80-120% faster than before, depending on what kind of CPU you have. More info here: https://www.nicehash.com/index.jsp?p=news&id=23

edit: Our team is further pushing limits of Axiom CPU mining. This time, we were able to achieve outstanding 241% speed improvement compared to original Axiom miner. Furthermore, we packed miner together with a nice&slim launcher for easy CPU mining and real-time statistics from NiceHash. More info here: https://www.nicehash.com/index.jsp?p=news&id=25

Can't seem to compile again.  Getting these errors on Ubuntu 14.02 system with all dependencies installed:

crypto/mshabal.c:144:3: note: in expansion of macro âPPâ
   PP(A[0x4], A[0x3], B[0x8], B[0x5], B[0x1], B[0xE], C[0x0], M(0x8));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:145:3: note: in expansion of macro âPPâ
   PP(A[0x5], A[0x4], B[0x9], B[0x6], B[0x2], B[0xF], C[0xF], M(0x9));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:146:3: note: in expansion of macro âPPâ
   PP(A[0x6], A[0x5], B[0xA], B[0x7], B[0x3], B[0x0], C[0xE], M(0xA));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:147:3: note: in expansion of macro âPPâ
   PP(A[0x7], A[0x6], B[0xB], B[0x8], B[0x4], B[0x1], C[0xD], M(0xB));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:148:3: note: in expansion of macro âPPâ
   PP(A[0x8], A[0x7], B[0xC], B[0x9], B[0x5], B[0x2], C[0xC], M(0xC));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:149:3: note: in expansion of macro âPPâ
   PP(A[0x9], A[0x8], B[0xD], B[0xA], B[0x6], B[0x3], C[0xB], M(0xD));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:150:3: note: in expansion of macro âPPâ
   PP(A[0xA], A[0x9], B[0xE], B[0xB], B[0x7], B[0x4], C[0xA], M(0xE));
   ^
crypto/mshabal.c:86:11: error: expected â;â before âttâ
   __m256i tt; \
           ^
crypto/mshabal.c:151:3: note: in expansion of macro âPPâ
   PP(A[0xB], A[0xA], B[0xF], B[0xC], B[0x8], B[0x5], C[0x9], M(0xF));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:197:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x0], C[0x0], M(0x0));
   ^
crypto/mshabal.c:192:3: error: âtmpâ undeclared (first use in this function)
   tmp = xb; \
   ^
crypto/mshabal.c:197:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x0], C[0x0], M(0x0));
   ^
crypto/mshabal.c:191:11: warning: implicit declaration of function â_mm256_supi32â [-Wimplicit-function-declaration]
   __m256i tmp; \
           ^
crypto/mshabal.c:197:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x0], C[0x0], M(0x0));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:198:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x1], C[0x1], M(0x1));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:199:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x2], C[0x2], M(0x2));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:200:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x3], C[0x3], M(0x3));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:201:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x4], C[0x4], M(0x4));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:202:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x5], C[0x5], M(0x5));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:203:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x6], C[0x6], M(0x6));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:204:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x7], C[0x7], M(0x7));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:205:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x8], C[0x8], M(0x8));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:206:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0x9], C[0x9], M(0x9));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:207:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0xA], C[0xA], M(0xA));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:208:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0xB], C[0xB], M(0xB));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:209:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0xC], C[0xC], M(0xC));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:210:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0xD], C[0xD], M(0xD));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:211:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0xE], C[0xE], M(0xE));
   ^
crypto/mshabal.c:191:11: error: expected â;â before âtmpâ
   __m256i tmp; \
           ^
crypto/mshabal.c:212:3: note: in expansion of macro âSWAP_AND_SUBâ
   SWAP_AND_SUB(B[0xF], C[0xF], M(0xF));
   ^
crypto/mshabal.c:228:3: warning: implicit declaration of function â_mm256_sto_si256â [-Wimplicit-function-declaration]
   _mm256_storeu_si256((__m256i *)sc->state + j, A[j]);
   ^
crypto/mshabal.c:228:33: error: expected expression before â)â token
   _mm256_storeu_si256((__m256i *)sc->state + j, A[j]);
                                 ^
crypto/mshabal.c:230:33: error: expected expression before â)â token
   _mm256_storeu_si256((__m256i *)sc->state + j + 12, B[j]);
                                 ^
crypto/mshabal.c:231:33: error: expected expression before â)â token
   _mm256_storeu_si256((__m256i *)sc->state + j + 28, C[j]);
                                 ^
make[2]: *** [crypto/cpuminer-mshabal.o] Error 1
make[2]: Leaving directory `/home/dhsc19/Downloads/mining/cpuminer-multi'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/dhsc19/Downloads/mining/cpuminer-multi'
make: *** [all] Error 2

Comment from cpuminer-multi thread says for developer to use git pull.

[NiceHashSupport]

No official support for linux Axiom miner from our side. Sorry, you will have to wait for linux gurus to port our changes to linux environment.

[pallas]

No official support for linux Axiom miner from our side. Sorry, you will have to wait for linux gurus to port our changes to linux environment.

It compiles fine on linux for me.

[chrysophylax]

No official support for linux Axiom miner from our side. Sorry, you will have to wait for linux gurus to port our changes to linux environment.

It compiles fine on linux for me.

not for me pallas ...

i get very similar errors ...

is it a straight compile for you? ... intel cpu? ... amd? ...

my compile system is amd ...

#crysx

[TYPEcoin]

I just got intro this,let's see what is going to happan