I have 2 rigs which are behind firewall, so I use tunneling
Nicehash m iner can't get "SMA information" on start, so can't be used for auto switching
Which ports/address I have to make available to the GUI in order to get the info?
http (80) and https (443) and additionally all stratum ports (see https://www.nicehash.com/index.jsp?p=gstarted#seller) |
|
|
|
Will anything happen to the increments for order.set.price.decrease and order.set.price? Presently these are in steps of 0.0001 -- will that now be 0.1 or something else?
This will stay the same, that is 0.0001. This is one of the major driver for the change, since it will allow more refined and competitive bidding. |
|
|
|
|
Hi,
Congratulations to 1H87bQ7gpzut4CKNdqAnYrBXQcGyRcSMMP for the recently found block with approx 30 TH/s!
Best regards,
NiceHash team.
|
|
|
|
How I locked the diff per worker.
I put d=8192
But these does not locked diff per worker what I must put ??
Diff can not be absolutely locked, it can only be suggested (as you already did), more info in this FAQ: https://www.nicehash.com/index.jsp?p=faq#faqs10 |
|
|
|
I rented some X11 hashing power yesterday and pointed it to your Solo Dash mining pool. It was constantly being disconnected. I used your pool verificator to see if there was a problem. This was the result.... Resolving pool host stratum.solo.nicehash.com... OK Establishing connection with proxy... OK Establishing connection with pool 158.85.244.248:3336... 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... Pool difficulty too low (provided=0.00064087, minimum=0.002) Waiting for pool to send higher difficulty. Received authorization result... OK Error: Read timed out Your pool is shown as incompatible therefore we encourage you to contact pool operator to make sure that the pool is using minimal/starting pool share difficulty which is compatible with our service (and thus compatible with today's miners), please send them link to our FAQ on this topic: https://www.nicehash.com/index.jsp?p=faq#faqb3. Thank you! Is there a way to resolve this? Yes, just use fixed difficulty. See here: https://solo.nicehash.com/faq.htm ... just put "diff_3072" for the password field and orders will be 100% stable. Best regards, NiceHash team. |
|
|
|
|
Hmm, unfortunately there seems to be a small but annoying bug - if you start with clean NHM (without config) then the entered Bitcoin address is not stored in config.json and therefore not used in the benchmark. We'll release a bugfix soon, meanwhile just "Start" miner for a few moments (will start mining on first algo - X11), then Stop miner, close NHM. Then start NHM again and you should be able to run benchmark.
|
|
|
|
i just upgraded to the new version and all the benchmarks are saying terminated..
1.3 worked. i dunno why 1.4 isnt.
Which cards are you using? |
|
|
|
Quick question, what are my earnings likely to be with two S3+ running 480-490ghs each if I sell the hashrate on your website?
If you mine on SOLO pool, you only get all or nothing  - if you're lucky you find Bitcoin block and get 25 Bitcoins. If you sell on PPS nicehash.com service, you'll get in average approximately 5% more than direct Bitcoin mining (see https://www.nicehash.com/index.jsp?p=stats). |
|
|
|
Dear users, Version 1.4.0.0 of NiceHash Miner has just been released. It brings: - Added the ability to submit per-device benchmark results to NiceHash's profitability calculator
- Fixed bug regarding infinite amount of error messages when an invalid Bitcoin address is used
- Removed default Bitcoin address, users are encouraged to use it's own Bitcoin address upon starting NiceHash Miner
- Automatically removes old Ethereum DAG files
- Ethereum benchmark speed is more accurate now by using up-to-date DAG file
- Fixed benchmark DAG file location for Ethereum
- Added trim to remove extra spaces in some of the CPU names
- Added the ability to mine Ethereum on NVIDIA_3.X GPUs
- Removed NeoScrypt from the algo list for NVIDIA_3.X as it is not supported anymore
- Added the ability to mine only with certain device(s) for AMD Ethereum mining
It is recommended that all existing users upgrade to this release. If your are a new user, download the full package and follow How to get&run it? instructions.  AMD GPU USERS - PLEASE READ! In some particular combinations of Windows version + AMD Driver version benchmarks on some algorithms keep getting terminated. If the particular algorithm that is being terminated is shown on pause on the front page of NiceHash.com (No orders - mining unavailable), then this is normal expected behavior. However, if benchmark is also terminated for active algorithms, then you have to apply workaround solution. The solution is to copy all .cl files from the [..\bin\sgminer-5-3-0-general\kernel] folder into [c:\Users\[your_username_here]\appdata\local\temp\] folder and then re-run the benchmark for the algorithms that are terminated during benchmark. Go ahead and get the new version: download here! Keep on mining! Best regards, NiceHash team |
|
|
|
Dear users, Version 1.4.0.0 of NiceHash Miner has just been released. It brings: - Added the ability to submit per-device benchmark results to NiceHash's profitability calculator
- Fixed bug regarding infinite amount of error messages when an invalid Bitcoin address is used
- Removed default Bitcoin address, users are encouraged to use it's own Bitcoin address upon starting NiceHash Miner
- Automatically removes old Ethereum DAG files
- Ethereum benchmark speed is more accurate now by using up-to-date DAG file
- Fixed benchmark DAG file location for Ethereum
- Added trim to remove extra spaces in some of the CPU names
- Added the ability to mine Ethereum on NVIDIA_3.X GPUs
- Removed NeoScrypt from the algo list for NVIDIA_3.X as it is not supported anymore
- Added the ability to mine only with certain device(s) for AMD Ethereum mining
It is recommended that all existing users upgrade to this release. If your are a new user, download the full package and follow How to get&run it? instructions. AMD GPU USERS - PLEASE READ! In some particular combinations of Windows version + AMD Driver version benchmarks on some algorithms keep getting terminated. If the particular algorithm that is being terminated is shown on pause on the front page of NiceHash.com (No orders - mining unavailable), then this is normal expected behavior. However, if benchmark is also terminated for active algorithms, then you have to apply workaround solution. The solution is to copy all .cl files from the [..\bin\sgminer-5-3-0-general\kernel] folder into [c:\Users\[your_username_here]\appdata\local\temp\] folder and then re-run the benchmark for the algorithms that are terminated during benchmark. Go ahead and get the new version: download here! Keep on mining! Best regards, NiceHash team |
|
|
|
what happened don't understand? [2016-04-15 22:23:51] stratum_recv_line failed
[2016-04-15 22:23:51] ...retry after 10 seconds Ping passes, why I have no connection with the pools, I was banned?  On which algorithm are you seeing this? Please send us screenshot and your public ip to support@nicehash.com so that we can check the details. |
|
|
|
- did we have an outage on stratum+tcp://stratum.nicehash.com:3334 today ?
- is your maintance till 4:00 UTC still in progress ?
Your Informations have been better and more accurate over the past 2 years.
Last few days experience do not make me feel well, on renting a few 100 THs the next days ^^
Indeed we had a few unexpected downtime and maintenance periods in the last few days. The most up-to date information about our service status is officially posted on our Twitter ( https://twitter.com/NiceHashMining). Currently is our service running normally and we don't expect any additional longer maintenance in the next few days. Thanks! Best regards, NiceHash team. |
|
|
|
|
Show Posts
