Author

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

sr. member
Activity: 350
Merit: 250
Ok guys, i am using the modded x11 sgminer, and got a very decent hash rate increase. however, it is not failing over to my backup pools.

can you please send me info for my config file in order to work better with nicehash? i believe there are some instructions thats needed to be set in the bat/conf files in order to work.

much appreciated.

Same situation.
When nicehash not have work then i need to switch to second pool manually.

Same here bu works fine with this proxy (https://bitcointalksearch.org/topic/new-stratumgetwork-proxy-with-web-based-gui-and-pools-management-611338) between nicehash and sgminer.

Sorry but, I not know java. This not mean anything for me.
legendary
Activity: 1988
Merit: 1007

If average price is 2.8 BTC/GH/Day and you have p=2.7, then your miner will work but if you have p=2.9 then your miner won't work on nicehash.

That was my point exactly. After reading the FAQ I thought I could set a number of prices trying to sell my hashing power for the highest value.

Namely, I have nicehash as my main pool and also as two of my failover pools. The main pool has a higher price, the second one a lower price and the third one an even lower price.

Now I realize I should have only a minimum price because I will always get paid by the average price. Right?


I found that the best way to do this is to just set Nicehash's value to whatever the second highest pool is (and a little above). Ie. if hashco.ws is doing 0.0035 BTC, set Nicehash up to 0.0036. This way you will always get whichever is most profitable.

Note: edit this to whatever pools/type you're using, but the same concept remains.
full member
Activity: 217
Merit: 100
Ok guys, i am using the modded x11 sgminer, and got a very decent hash rate increase. however, it is not failing over to my backup pools.

can you please send me info for my config file in order to work better with nicehash? i believe there are some instructions thats needed to be set in the bat/conf files in order to work.

much appreciated.

Same situation.
When nicehash not have work then i need to switch to second pool manually.

Same here bu works fine with this proxy (https://bitcointalksearch.org/topic/new-stratumgetwork-proxy-with-web-based-gui-and-pools-management-611338) between nicehash and sgminer.
sr. member
Activity: 434
Merit: 250
How did a new order #10152 get ahead of my order #8920 on the sha256 cue at .04btc/th/day. I put my order in days ago and have been waiting for it to come to the top of the cue and to have a new order queued ahead of mine at the same price is unfair.


This just happend for scrypt

#10339 gets priority over #8979

how does this work? why are some new orders placed before the current ones?

Thanks for reporting this. We'll take a look at this issue ASAP!

so how's it going?


I just want to thank you for fucking me over last night so I had to wait another ~7 hours or so before my order went through


Thanks!!


If you're gonna use nicehash you better be ready to place orders with highest bid because everything else is fucked.
full member
Activity: 137
Merit: 100
Ok guys, i am using the modded x11 sgminer, and got a very decent hash rate increase. however, it is not failing over to my backup pools.

can you please send me info for my config file in order to work better with nicehash? i believe there are some instructions thats needed to be set in the bat/conf files in order to work.

much appreciated.

There's another sgminer modded has the same peformance with failover supported
https://bitcointalksearch.org/topic/annx11x13-x11-darkcoinx13-marucoin-miner-based-on-sph-sgminer-623409
sr. member
Activity: 350
Merit: 250
Ok guys, i am using the modded x11 sgminer, and got a very decent hash rate increase. however, it is not failing over to my backup pools.

can you please send me info for my config file in order to work better with nicehash? i believe there are some instructions thats needed to be set in the bat/conf files in order to work.

much appreciated.

Same situation.
When nicehash not have work then i need to switch to second pool manually.
sr. member
Activity: 457
Merit: 273
How did a new order #10152 get ahead of my order #8920 on the sha256 cue at .04btc/th/day. I put my order in days ago and have been waiting for it to come to the top of the cue and to have a new order queued ahead of mine at the same price is unfair.


This just happend for scrypt

#10339 gets priority over #8979

how does this work? why are some new orders placed before the current ones?

Thanks for reporting this. We'll take a look at this issue ASAP!
member
Activity: 85
Merit: 10
How did a new order #10152 get ahead of my order #8920 on the sha256 cue at .04btc/th/day. I put my order in days ago and have been waiting for it to come to the top of the cue and to have a new order queued ahead of mine at the same price is unfair.


This just happend for scrypt

#10339 gets priority over #8979

how does this work? why are some new orders placed before the current ones?
Now two are ahead of me. I trust that you are working to fix this. perhaps you should consider refunding fees to those whose positions were usurped. if I was 8979 I'd be steaming.
sr. member
Activity: 434
Merit: 250
How did a new order #10152 get ahead of my order #8920 on the sha256 cue at .04btc/th/day. I put my order in days ago and have been waiting for it to come to the top of the cue and to have a new order queued ahead of mine at the same price is unfair.


This just happend for scrypt

#10339 gets priority over #8979

how does this work? why are some new orders placed before the current ones?
sr. member
Activity: 457
Merit: 273
Am I right? If the sellers are paid always by the average price and not by the price of the order they are currently working on, it won’t make any sense to input minimum prices in the password field, right? We can just input a random low price and we will always get paid by the average as everybody else.

Maybe the OP should change the FAQ:

"You can limit your miners to work on NiceHash only if the payment is good enough. You can still leave NiceHash as your primary stratum server. NiceHash stratum server will only be activated if there are orders that matches your price threshold. Otherwise miners will work normally on your backup/secondary pool."

This faq has truly been obsolete, we've updated it now to reflect the current status.
member
Activity: 85
Merit: 10
How did a new order #10152 get ahead of my order #8920 on the sha256 cue at .04btc/th/day. I put my order in days ago and have been waiting for it to come to the top of the cue and to have a new order queued ahead of mine at the same price is unfair.
hero member
Activity: 546
Merit: 500

Now I realize I should have only a minimum price because I will always get paid by the average price. Right?


You are right.
legendary
Activity: 1564
Merit: 1027

If average price is 2.8 BTC/GH/Day and you have p=2.7, then your miner will work but if you have p=2.9 then your miner won't work on nicehash.

That was my point exactly. After reading the FAQ I thought I could set a number of prices trying to sell my hashing power for the highest value.

Namely, I have nicehash as my main pool and also as two of my failover pools. The main pool has a higher price, the second one a lower price and the third one an even lower price.

Now I realize I should have only a minimum price because I will always get paid by the average price. Right?
hero member
Activity: 546
Merit: 500
If I understood this statement correctly, then there is no point in setting the minimum price in the password field. We will always get paid by the average price, right?

I mean, why should I bother to set the minimum price for SHA hashing at 0.05? Maybe this will cause some unneeded login failures.

Am I right? If the sellers are paid always by the average price and not by the price of the order they are currently working on, it won’t make any sense to input minimum prices in the password field, right? We can just input a random low price and we will always get paid by the average as everybody else.

Maybe the OP should change the FAQ:

"You can limit your miners to work on NiceHash only if the payment is good enough. You can still leave NiceHash as your primary stratum server. NiceHash stratum server will only be activated if there are orders that matches your price threshold. Otherwise miners will work normally on your backup/secondary pool."

 Grin


If average price is 2.8 BTC/GH/Day and you have p=2.7, then your miner will work but if you have p=2.9 then your miner won't work on nicehash.
legendary
Activity: 1564
Merit: 1027

Orders are pretty much irrelevant for providers. You are paid the average price, not the price of order your miner is working on. We changed this distribution to more fair one quite a while ago. You are paid what main page says and what following API says: https://www.nicehash.com/api?method=stats.global.current

If I understood this statement correctly, then there is no point in setting the minimum price in the password field. We will always get paid by the average price, right?

I mean, why should I bother to set the minimum price for SHA hashing at 0.05? Maybe this will cause some unneeded login failures.

Am I right? If the sellers are paid always by the average price and not by the price of the order they are currently working on, it won’t make any sense to input minimum prices in the password field, right? We can just input a random low price and we will always get paid by the average as everybody else.

Maybe the OP should change the FAQ:

"You can limit your miners to work on NiceHash only if the payment is good enough. You can still leave NiceHash as your primary stratum server. NiceHash stratum server will only be activated if there are orders that matches your price threshold. Otherwise miners will work normally on your backup/secondary pool."

 Grin


full member
Activity: 154
Merit: 100
my miners at gawminers are now having crazy amounts of rejects, high percentage.. what is the cause of this?
member
Activity: 413
Merit: 10
Hey, everyone!
I've made a simple widget for monitoring of my hashrates, balance, etc

You can see your current hashrate, reject rate, unpaid balance and even automatically convert the balance to one of the supported currencies. Just type in your BTC address, choose the currency, refresh interval, whether you would like to receive notification for low hashrate and you're ready to go.

You can also view the hashrate graph by simply tapping on the widget. This widget supports multiple workers (Scrypt, SHA256, X11, etc)  on the same BTC address.

Enjoy!

https://play.google.com/store/apps/details?id=com.inductiveconcepts.nicehashwidget





sr. member
Activity: 280
Merit: 250
Yes, if there is high delay on connection, you would be getting a lot of stale shares (Job not found).
member
Activity: 112
Merit: 10
im having some big troubles here, i bought 0.079BTC x11 hashing power to hash at coinmine.pw .... the pool did not credit any balance or share to my account, i already send several emails to the pool support and also posted my problem at their bitcointalk thread: https://bitcointalk.org/index.php?topic=406178.280

Its not fun or fair to loose my hard earning of over 2 weeks in just 20 minutes and nobody reply or look at the situation (the owners) to help, please kindly help me support from nicehash to see if there was share work done on your side so i can have proof to send to the pool owner

If your BTC balance was reduced, then work was done. We have our own share validators in place. But if the pool you selected mined coin that does not use X11 coin, then all shares from NiceHash to the pool would be rejected.

Are there not enough orders for my 30 MH's?   I am trying to figure out if my fail over to my backup pool is legit as there are not enough orders or is there an issues here with NiceHash or is there an issue with my Fail-over and the way it is working..

We REALLY need more clear easy to read vision on # of orders vs. numbers of miners and when one side or the other is short..

Something simple like..

There are currently Orders for 4.2 TH and there are miners providing 5.2 TH... So there is an overage of 1 TH that will cause some miners here to fail over to their Back up pool.

OP please advise..


Also.. Rejects a lot higher for me than normal. Normal on here has been less then 1%..  Now on here my Reject rate is 13+%   Is this a Miner issue or a pool Issue?




That sounds like you having connection issues with NiceHash. We did no changes that could reflect this behavior, also there is no one else complaining regarding this.

Orders are pretty much irrelevant for providers. You are paid the average price, not the price of order your miner is working on. We changed this distribution to more fair one quite a while ago. You are paid what main page says and what following API says: https://www.nicehash.com/api?method=stats.global.current


Thanks.. Checking with GAW

Would connection issues also cause the TONS of rejects I am now getting on HiceHash?    Never before yesterday have I gotten so may rejects here(Or anywhere)
Jump to: