Author

Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 162. (Read 794394 times)

hero member
Activity: 588
Merit: 501
Thank You,

sorry for trouble, this was a bit confusing.



Yes, the website you linked has confusing title. What it explains there is Scrypt Jane and not Scrypt-Adaptive-nFactor.
sr. member
Activity: 328
Merit: 250
Thank You,

sorry for trouble, this was a bit confusing.

hero member
Activity: 588
Merit: 501
No, factors are different - what Vertcoin originally used before it was forked to Lyra.
sr. member
Activity: 328
Merit: 250
I have put order on scrtypnf and getting only recets by pool.
pool verificator says pool is ok.
All details are correct, username, password etc...

Spending money getting nothing??
Pool says 0 shares 0 kh/s

Order no :S
Standard
 #550099

According to order details, you tried to mine leocoin, but it does not use scryptnf algo thus all your shares were rejected with reason share above target.

Leocoin IS scryptnfactor, scryptjane or scryptchacha.

Scrypt jane is not equal as scryptnf. Our scryptnf has full name: Scrypt-Adaptive-nFactor.

Like this?
http://leocoin.org/nfactor.aspx
hero member
Activity: 588
Merit: 501
I have put order on scrtypnf and getting only recets by pool.
pool verificator says pool is ok.
All details are correct, username, password etc...

Spending money getting nothing??
Pool says 0 shares 0 kh/s

Order no :S
Standard
 #550099

According to order details, you tried to mine leocoin, but it does not use scryptnf algo thus all your shares were rejected with reason share above target.

Leocoin IS scryptnfactor, scryptjane or scryptchacha.

Scrypt jane is not equal as scryptnf. Our scryptnf has full name: Scrypt-Adaptive-nFactor.
sr. member
Activity: 328
Merit: 250
I have put order on scrtypnf and getting only recets by pool.
pool verificator says pool is ok.
All details are correct, username, password etc...

Spending money getting nothing??
Pool says 0 shares 0 kh/s

Order no :S
Standard
 #550099

According to order details, you tried to mine leocoin, but it does not use scryptnf algo thus all your shares were rejected with reason share above target.

Leocoin IS scryptnfactor, scryptjane or scryptchacha.
hero member
Activity: 588
Merit: 501
I have put order on scrtypnf and getting only recets by pool.
pool verificator says pool is ok.
All details are correct, username, password etc...

Spending money getting nothing??
Pool says 0 shares 0 kh/s

Order no :S
Standard
 #550099

According to order details, you tried to mine leocoin, but it does not use scryptnf algo thus all your shares were rejected with reason share above target.
sr. member
Activity: 328
Merit: 250
I have put order on scrtypnf and getting only recets by pool.
pool verificator says pool is ok.
All details are correct, username, password etc...

Spending money getting nothing??
Pool says 0 shares 0 kh/s

Order no :S
Standard
 #550099
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
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

I just did:

git clone ....
cd
./autogen.sh
./configure
edited the Makefile to add -lcurl and -lcrypto (for some reason they do not get added automatically, maybe it's missing some m4 part, it happens on many cpuminer versions)
make
full member
Activity: 364
Merit: 101
I just got intro this,let's see what is going to happan
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
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
legendary
Activity: 2716
Merit: 1094
Black Belt Developer
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.
hero member
Activity: 588
Merit: 501
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.
member
Activity: 96
Merit: 10
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.
legendary
Activity: 1596
Merit: 1027
Hi, there Smiley
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 Wink
full member
Activity: 142
Merit: 100
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.
hero member
Activity: 588
Merit: 501
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.
full member
Activity: 142
Merit: 100
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.

legendary
Activity: 885
Merit: 1006
NiceHash.com
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
legendary
Activity: 885
Merit: 1006
NiceHash.com
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
Jump to: