Great service offering by Nicehash.
Really amazing services. Any one can start instant cryptocurrency mining with nicehash. As well as if user have own hardware , then it can also be put on lease with time frame and rate.
Nicehash provide both way service useful for user and investors.
Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 95. (Read 794394 times)
September 06, 2016, 09:54:49 AM
September 06, 2016, 09:11:58 AM
NiceHash Bot 1.0.3.3 has been released: https://github.com/nicehash/NiceHashBot/releases/tag/1.0.3.3
Best regards,
NiceHash team.
- fixed daggerhashimoto order placing bug
- API version compatibility bump
Best regards,
NiceHash team.
September 06, 2016, 02:01:21 AM
Hi To All!
Its my first post here. Sorry for my English.
I have a small rig 2x380, 2x 280x, just complete. I install Win7 x64 Home Premium, drivers 14.12 on AMD, Frame 3.5. Then download Nicehash from site but when I click to start they dont do that. Could You help?
Regards!
Its my first post here. Sorry for my English.
I have a small rig 2x380, 2x 280x, just complete. I install Win7 x64 Home Premium, drivers 14.12 on AMD, Frame 3.5. Then download Nicehash from site but when I click to start they dont do that. Could You help?
Regards!
September 06, 2016, 12:10:49 AM
What are the types of rejects?
September 05, 2016, 07:46:22 PM
Can I get a little feedback about your change to the open-ethereum-pool. I have a private pool that I use that pool on and I added your "update" to the handlers.go and got it working with nicehash without a problem. The only problem I have now is frequent disconnects with the nicehash order.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
Did you implement this patch: https://github.com/sammy007/open-ethereum-pool/pull/48/commits/8141c95966e3ceca16974433a857df1ca81da745 ?
Yes I applied that patch.
What is exactly the reason for the disconnect (you should get this info in the stratum conversation)?
Well it is not showing on my side but it is on your side. I place an order for a few GH and it makes it to about 1.1-4 and then drops out and starts back again a few minutes later.
I set up on a new server with plenty of RAM and cores to run a pool and do not have any problems running mine or my friends rigs on the pool.
I really do not even know what is the problem with the Nicehash order stopping and restarting.
thanks
I do understand that I can get duplicate shares but the stats on the nicehash order say 34-50% rejected
September 04, 2016, 03:26:00 PM
Can I get a little feedback about your change to the open-ethereum-pool. I have a private pool that I use that pool on and I added your "update" to the handlers.go and got it working with nicehash without a problem. The only problem I have now is frequent disconnects with the nicehash order.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
Did you implement this patch: https://github.com/sammy007/open-ethereum-pool/pull/48/commits/8141c95966e3ceca16974433a857df1ca81da745 ?
Yes I applied that patch.
What is exactly the reason for the disconnect (you should get this info in the stratum conversation)?
September 04, 2016, 03:13:39 PM
There is no bin directory in the beta zip.
As soon as you run the 1.7-BETA version it will auto-download the needed miner binaries. If this does not happen, please report the issue here: https://github.com/nicehash/NiceHashMiner/issues
Thanks!
The error message is made (Missing path ... bin/...) and I press 'Continue'. It then says that it is loading, but after 15 minutes of waiting nothing is happening.
September 04, 2016, 02:43:30 PM
Can I get a little feedback about your change to the open-ethereum-pool. I have a private pool that I use that pool on and I added your "update" to the handlers.go and got it working with nicehash without a problem. The only problem I have now is frequent disconnects with the nicehash order.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
Did you implement this patch: https://github.com/sammy007/open-ethereum-pool/pull/48/commits/8141c95966e3ceca16974433a857df1ca81da745 ?
Yes I applied that patch.
September 04, 2016, 08:27:56 AM
Can I get a little feedback about your change to the open-ethereum-pool. I have a private pool that I use that pool on and I added your "update" to the handlers.go and got it working with nicehash without a problem. The only problem I have now is frequent disconnects with the nicehash order.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
Did you implement this patch: https://github.com/sammy007/open-ethereum-pool/pull/48/commits/8141c95966e3ceca16974433a857df1ca81da745 ?
September 04, 2016, 08:26:11 AM
There is no bin directory in the beta zip.
As soon as you run the 1.7-BETA version it will auto-download the needed miner binaries. If this does not happen, please report the issue here: https://github.com/nicehash/NiceHashMiner/issues
Thanks!
September 04, 2016, 02:53:00 AM
Can I get a little feedback about your change to the open-ethereum-pool. I have a private pool that I use that pool on and I added your "update" to the handlers.go and got it working with nicehash without a problem. The only problem I have now is frequent disconnects with the nicehash order.
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
thanks
If I run my miners on it using claymore's miner (Eth only mode) then I do not see any disconnects of my miners. I have run nicehash orders with and without my miners and it doesn't change the Nicehash disconnects.
Any help would be appreciated.
thanks
September 03, 2016, 03:25:20 PM
There is no bin directory in the beta zip.
September 03, 2016, 09:19:01 AM
CPU and NVIDIA miners: try out the new 1.7-BETA NH Miner with the support of very profitable CryptoNight algorithm:
https://github.com/nicehash/NiceHashMiner/releases/tag/v1.7.0.1-BETA
Best regards,
NiceHash team.
https://github.com/nicehash/NiceHashMiner/releases/tag/v1.7.0.1-BETA
Best regards,
NiceHash team.
September 03, 2016, 09:05:40 AM
ok thank you for the clarification
1- How to setup no Hash limitation and is there any interest to do that
2- I've DL the last order bot but it's not working. Message error say api version have changed (I can't remember the exact message) and don't start.
1- How to setup no Hash limitation and is there any interest to do that
2- I've DL the last order bot but it's not working. Message error say api version have changed (I can't remember the exact message) and don't start.
September 03, 2016, 08:53:21 AM
I would really appreciate an explanation
This order stayed here about 15mn at this price and with 100 miners. Strange thing
This order stayed here about 15mn at this price and with 100 miners. Strange thing
Obviously there was a situation, where existing orders were low-priced, and then many new orders were submitted with much higher price. Our system is designed in such a way, that miners are redirected to better paying orders gradually, not instantly. This is to improve system efficiency. See this FAQ for more details: https://www.nicehash.com/index.jsp?p=faq#faqb1
Best regards,
NiceHash team.
September 03, 2016, 07:14:06 AM
I would really appreciate an explanation
https://www.evernote.com/l/AA_vI3axaZVNupik7OUzlxBPrqPx1MjyhNw
This order stayed here about 15mn at this price and with 100 miners. Strange thing
https://www.evernote.com/l/AA_vI3axaZVNupik7OUzlxBPrqPx1MjyhNw
This order stayed here about 15mn at this price and with 100 miners. Strange thing
September 02, 2016, 08:14:38 AM
when i connect my antminer s7 & s9 directly to nh it mines properly with very few rejects/stales or dupes but when i connect them via proxy lots of rejects especially dupes & invalid extranonce shares.
INFO:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 4096.0) from on Nice/West Hash. Booo !!!!. Error: JsonRpcError code=20, message=Invalid extranonce2 size., traceback=null
other miners via proxy are ok, normal with occasional rejects such as stales or dupes just the antminers.
any solutions ?
thx.
INFO:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 4096.0) from on Nice/West Hash. Booo !!!!. Error: JsonRpcError code=20, message=Invalid extranonce2 size., traceback=null
other miners via proxy are ok, normal with occasional rejects such as stales or dupes just the antminers.
any solutions ?
thx.
Sure is.. Mine at a better pool.
September 01, 2016, 03:25:37 PM
when i connect my antminer s7 & s9 directly to nh it mines properly with very few rejects/stales or dupes but when i connect them via proxy lots of rejects especially dupes & invalid extranonce shares.
INFO:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 4096.0) from on Nice/West Hash. Booo !!!!. Error: JsonRpcError code=20, message=Invalid extranonce2 size., traceback=null
other miners via proxy are ok, normal with occasional rejects such as stales or dupes just the antminers.
any solutions ?
thx.
INFO:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 4096.0) from on Nice/West Hash. Booo !!!!. Error: JsonRpcError code=20, message=Invalid extranonce2 size., traceback=null
other miners via proxy are ok, normal with occasional rejects such as stales or dupes just the antminers.
any solutions ?
thx.
September 01, 2016, 02:50:32 PM
Yes that is exactly what I want! To put manually the power that draws every algorithm ( I have watt metter) and put the price of electricity like 0.1$ and then nicehash miner could actually count what is the real profit! Whit the ne 1.7.0.1 beta you almost did it , it is check profitability (now working without error) on your site. There was a minercontrol by KBomba that had this option! You can have a look at it! It calculate the net profit by profit-powercost=actual profit!
September 01, 2016, 02:22:10 PM
Is there a way to put how much power draws the system in nicehash miner , so that the profit calculation to be real? I don`t see such an option!
It is impossible to get an exact power draw of the full system, and the real information is only the one that is shown at the power socket, which includes power supply efficiency, etc. But you can estimate your power costs if you measure it wilt some power meter at the wall ... but please note that power draw also depends on particular algorithm. We might add the option to manually enter your power draw and power costs, which can then be evaluated when calculating full costs.
Jump to: