Hi,
I´m new over the place, and also over mining. I´m having trouble trying to run Nicehash with a Rx 480, both in win7 or win10, no matter driver version. I got this message "Failed to create OpenGL context for format QSurfaceFormat", and when I run the benchmarks I get a blue screen. Anyone can help?
Sorry if I´m asking something already answered, as I said I´m noob.
Thanx a lot.
Please make sure to update your AMD drivers. Also, if you're new in mining and using Windows, we suggest you to use simple-to-use NiceHash Miner. |
|
|
|
If you're getting `GLIBCXX_x.x.x' not found on Ubuntu 14.04, try this: sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install libstdc++6 |
|
|
|
Linux as well (gtx 1070 on stock clocks, alpha version, will be tuned before release):  |
|
|
|
Any tips or resources please for integrating Cryptonight mining at Nicehash (stratum+tcp://cryptonight.eu.nicehash.com:3355) into cpuminer-multi_1.3-dev_ubuntu_x64 ?? Thanks in advance. Steve.
Just use cpuminer-opt: sudo apt-get install build-essential libcurl4-openssl-dev git automake libtool libjansson* libncurses5-dev libssl-dev libgmp-dev
git clone https://github.com/JayDDee/cpuminer-opt.git
cd cpuminer-opt
./build -j$(nproc)
./cpuminer -t NUM-OF-CPU-THREADS -a cryptonight -o stratum+tcp://cryptonight.eu.nicehash.com:3355 -u YOUR-BITCOIN-ADDRESS.WORKER-NAME -p x |
|
|
|
Can we hope a new miner more powerful soon for Nvidia ?
We are planning to release an improved version of EQM, targeting 100+ Sol/s on GTX 970 and 180+ Sol/s on 1070 (not yet fully tested, though). |
|
|
|
Is the download link down? I got file not found.  Sorry for the broken link, fixed now in the original post and here: OFFICIAL DOWNLOAD HERE |
|
|
|
|
A few benchmarks:
GTX 1070: ~125 Sol/s @ 110 W
GTX 1060 6GB: ~85 Sol/s @ 80 W
GTX 1050 Ti: ~53 Sol/s @ 45 W
GTX 1050: ~48 Sol/s @ 40 W
GTX 980 Ti: ~125 Sol/s
GTX 980 OC: ~115 Sol/s
GTX 980: ~100 Sol/s
GTX 970: ~85 Sol/s
GTX 950: ~50 Sol/s
GTX 750 Ti: ~36 Sol/s
GTX 750 1GB OC: ~34 Sol/s
Best regards,
NiceHash team.
|
|
|
|
Why does it say "unable to alloc locked pages - performance will be degraded" when it starts?
This is a warning when you enable CPU mining but your CPU or OS is missing some features. It is just a warning, nevermind. |
|
|
|
When will You embed this miner to NiceHashMiner?
Yes, it will be included in our next version, released soon (give us a few days for testing). |
|
|
|
|
Hello,
@olcaytu2005
First of all we would like to say that security and user satisfaction is of course very important to us. We are working very hard to provide an excellent service for hundreds thousands of users and we are doing this job for several years.
In this particular case the accusations and complaints from user olcaytu2005 are over reacted and also false. You all know that 2FA protection is standard and essential when dealing with funds. Also protecting your account with proper passwords and making sure your password is changed over a particular period of time adds additional level of security to your account. olcaytu2005 hasn't followed these standard practices and this is why his account got hacked and funds were lost.
If 2FA would be enabled from the begging, this would not happen and no funds would be lost.
Regarding the particular issue with changing passwords and still active open concurrent sessions. There was indeed a particular specific issue in this case and we've already added additional layer of protection to make sure this kind of scenarios would not happen again. Nevertheless, once again we have to say that even with this exceptions nobody could do any harm to your account if you would enable 2FA right after you registered your account or before you started dealing with funds on your account.
It is also very important to note that our system was not compromised or hacked. It was just the user's account by someone stealing/guessing his login credentials from his personal computer or other sources.
As far as refunds are concerned - any business or institution that has to do anything with financial transactions clearly states no refunds on any kind of financial loss. No matter who's fault is it in the end - this is also clear from our Terms of use, available on our website. Since we care a lot for our users satisfaction we have still done some refunds and compensations in the past for various kind of issues that were an actual result of service issues - for example, order was charged but not placed properly due to system overload, etc.. But we will never do any refunds due to user's faults. If we would do this then anybody could say that he needs some kind of refunds for thousands of possible issues you can make up.
Therefore - once again - olcaytu2005, we are very sorry for the funds you've lost and understand your situation, but unfortunately a refund in this case is not possible since you didn't follow standard security practices such as enabling 2FA before doing any kind of operations with funds. Thank you for understanding.
Best regards,
NiceHash team.
|
|
|
|
|
Hello,
First of all we would like to say that security and user satisfaction is of course very important to us. We are working very hard to provide an excellent service for hundreds thousands of users and we are doing this job for several years.
In this particular case the accusations and complaints from user olcaytu2005 are over reacted and also false. You all know that 2FA protection is standard and essential when dealing with funds. Also protecting your account with proper passwords and making sure your password is changed over a particular period of time adds additional level of security to your account. olcaytu2005 hasn't followed these standard practices and this is why his account got hacked and funds were lost.
If 2FA would be enabled from the begging, this would not happen and no funds would be lost.
Regarding the particular issue with changing passwords and still active open concurrent sessions. There was indeed a particular specific issue in this case and we've already added additional layer of protection to make sure this kind of scenarios would not happen again. Nevertheless, once again we have to say that even with this exceptions nobody could do any harm to your account if you would enable 2FA right after you registered your account or before you started dealing with funds on your account.
It is also very important to note that our system was not compromised or hacked. It was just the user's account by someone stealing/guessing his login credentials from his personal computer or other sources.
As far as refunds are concerned - any business or institution that has to do anything with financial transactions clearly states no refunds on any kind of financial loss. No matter who's fault is it in the end - this is also clear from our Terms of use, available on our website. Since we care a lot for our users satisfaction we have still done some refunds and compensations in the past for various kind of issues that were an actual result of service issues - for example, order was charged but not placed properly due to system overload, etc.. But we will never do any refunds due to user's faults. If we would do this then anybody could say that he needs some kind of refunds for thousands of possible issues you can make up.
Therefore - once again - olcaytu2005, we are very sorry for the funds you've lost and understand your situation, but unfortunately a refund in this case is not possible since you didn't follow standard security practices such as enabling 2FA before doing any kind of operations with funds. Thank you for understanding.
Best regards,
NiceHash team.
|
|
|
|
Hey folks, This is a heavily optimized Zcash (Equihash) miner for CUDA, brought to you by NiceHash.Up to 400 Sol/s @ stock GTX 1070WINDOWS and LINUXWorks on all GPUs with SM5.0 or more. Do not even try to run on older cards, won't work. Also, there are some improvements regarding CPU mining; ability to use locked pages, works good on multi-cpu servers/rigs with no additional settings needed. There are no additional settings needed for GPUs, the default should be the best for most, but just in case, several options are provided and you may choose among them (use -h to learn more). This miner has 0% fees but is currently compatible only with NiceHash.DOWNLOAD WINDOWS version (Windows 7+)DOWNLOAD Linux Ubuntu 14.04 versionDOWNLOAD Linux Ubuntu 16.04 version(Linux versions might work on other Linux distributions as well, but haven't been tested) Known issue on Linux: Ctrl+C does not stop the miner, you have to use stop.sh script (included in zip archive) or simply do "pkill -9 -f eqm". If you're getting `GLIBCXX_x.x.x' not found on Ubuntu 14.04, try this: sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install libstdc++6 See eqm -h for help. GPU mining only: eqm -l [LOCATION] -t 0 -u [YOUR-BTC-ADDRESS] -w [WORKER-NAME] CPU + GPU mining with 4 cores: eqm -l [LOCATION] -t 4 -u [YOUR-BTC-ADDRESS] -w [WORKER-NAME] -cd [GPUs] [LOCATION] = "eu", "usa", "hk", "jp" [GPUs] = 0 1 2 3 ... IMPORTANT: to achieve maximum speed you should enable two threads per GPU: -cd [GPU0] [GPU0] [GPU1] [GPU1]... for example, when using two threads per GPU while having three GPUs in the system: or you can simply use -ca parameter to run on all cuda devices: Notes on CPU mining: this miner has support for LOCKED PAGES; it can give few extra % of performance. How to enable: https://msdn.microsoft.com/en-us/library/ms190730.aspx (you may have to restart OS after changing). CPU mining supports "big servers" with more than 64 cores and there is no need to manually fiddle with affinities and NUMA nodes. Just set -p (number of CPUs) and -t (number of CORES per CPU) and miner automatically deals with it. Keep on mining! Best regards, NiceHash team. |
|
|
|
Today I discovered there was an order that wasn't mine. Someone hacked my account and put 2FA so I wasnt able to stop him. I immidietly changed my password from a fresh computer incase I had keylogger.
We are very sorry for the funds that you've lost. You should always enable 2FA before doing any kind of operations with the funds on your account to prevent such scenarios. You should also keep your account secure all the time ( https://www.nicehash.com/index.jsp?p=news&id=108) Once again, please make sure to keep 2FA enabled all the time when doing any kind of operations with any kind of funds in your account. Best regards, NiceHash team. |
|
|
|
While being known for its hashing power marketplace, NiceHash also runs a pure Zcash pool. First, you need to know that this pool is not the same pool as NiceHash's selling hashing power pool. It is an independent pool for mining ZEC - Zcash. All that you need to start mining is your Zcash wallet address. If you need help along the way, read our Getting started. Host: stratum.zcash.nicehash.com
Port: 3357
Username: Your Zcash wallet address
Password: x
: If you are planning to mine ZEC by buying hashing power on NiceHash, you should first view this special promo of ours before you decide which pool to use. For every order you make on NiceHash, we'll deduct 3% order fee (meaning 0% order fee) if you choose our Zcash pool for mining. |
|
|
|
Hi Nicehash support - can I use the windows miner on an APU A8-7600 APU gaming rig? According to specs it has AMD Integrated Graphics (Radeon R7 7600). Thanks
You can use it as CPU mining device, however APU's as GPU mining devices are not yet supported. |
|
|
|
I have a question for you: why does 1 of your 2 servers behind equihash.eu.nicehash.com returns a 17 bytes nonce (37.58.117.214) and the other a 5 bytes nonce (5.153.50.217)? Only the latter is supported by silentarmy.
Please revise the official stratum documentation at https://slushpool.com/help/#!/manual/stratum-protocol. There are no such limitations, a nonce can be even larger. The fact that you're receiving different nonce sizes is not related to a particular NiceHash stratum endpoint. It is simply a fact that NiceHash is forwarding work from different hashing power orders, which are working on different target pools. Anyway, 17 bytes nonce is the largest (max) that you'll receive from NiceHash stratum and even at this size you still have 3 bytes for iteration. So there is no reason why not to accept this kind of work. Please fix this as soon as possible, since our users would really love to use your miner and are now not able to do so due to these limitations of your miner. Thank you and keep up the good work! |
|
|
|
@mrb, could you please work on some small patches to improve compatibility with our NiceHash.com stratum servers? First of all, you should properly implement client.reconnect ( https://slushpool.com/help/#!/manual/stratum-protocol) Stratum: SILENTARMY is not compatible with servers fixing the first 17 bytes of the nonce
Connecting to equihash.eu.nicehash.com:3357
Stratum server sent us the first job
Mining on 6 devices
Stratum: invalid msg from server: Unimplemented method: client.reconnect: {'method': 'client.reconnect', 'params': [], 'id': None}
And secondly, it would be excellent if you could add a small stratum extension, called extranonce.subscribe. Please see here for the instructions (really easy): https://www.nicehash.com/?p=software#devsThank you, and keep up the excellent work! Best regards, NiceHash team. |
|
|
|
|
Show Posts
