Claymore’s ZCash/BTG AMD GPU Miner.
Latest version v12.6:
- added Vega cards support (ASM mode).
- added ASM mode for RX460/560 cards (+20% speed).
- new GPU sorting method for AMD cards. Now GPUs are sorted by physical bus index (it matches AfterBurner list of GPUs). Also the list of temperatures/fans matches the list of GPUs automatically.
Therefore “-di detect” and “-gmap” options are not necessary and not supported anymore.
WARNING: be careful if you use use separate overclock/temperature settings for every card, due to new sorting method GPUs can get different indexes!
- added fan/OC support for 17.7.2 (and higher) drivers.
- improved support for systems with more than 10 GPUs, check readme for “-di” option description for details.
- added pool selection in runtime (“e” key).
- a few minor improvements.
- Reduce intensity ("-i" option) if miner is unstable or if you see bad speed.
- It seems there is no way to get full speed on latest drivers for Fiji cards, at least in Windows. So don’t use latest drivers for Fury, use 15.12 or 16.3.2, or use “-asm 0” for them if you use newer drivers.
MEGA: Download v12.6
This version is for pools.
Catalyst (Crimson) 15.12 is required for best performance and compatibility.
15.12 does not support some Fiji cards, use 16.3.2 for them.
For 4xx cards (Polaris) Crimson 16.12.2 is recommended.
NOTE: For best performance on Fiji cards you must use 15.12 or 16.3.2 drivers. For newest drivers speed will be slower!
You can get bad results for non-recommended drivers, or miner can fail on startup.
Set the following environment variables, especially if you have 1-2GB cards:
For multi-GPU systems, set Virtual Memory size in Windows at least 16 GB:
“Computer Properties / Advanced System Settings / Performance / Advanced / Virtual Memory”.
This miner is free-to-use, however, current developer fee is 2% if you use secure SSL/TLS connection to mining pool, every hour the miner mines for 72 seconds for developer.
If you use unsecure connection to mining pool, current developer fee is 2.5%, every hour the miner mines for 90 seconds for developer.
If you don’t agree with the dev fee - don’t use this miner, or use “-nofee” option.
Attempts to cheat and remove dev fee will cause a bit slower mining speed (same as “-nofee 1”) though miner will show same hashrate.
Miner cannot just stop if cheat is detected because creators of cheats would know that the cheat does not work and they would find new tricks. If miner does not show any errors or slowdowns, they are happy.
This version is for recent AMD videocards only: 7xxx, 2xx, 3xx and 4xx, 1GB or more.
There are builds for Windows x64 and Linux x64. No 32-bit support. No NVidia support.
COMMAND LINE OPTIONS:
-zpool ZCash pool address. Only Stratum protocol is supported.
Miner also supports SSL/TLS encryption for all data between miner and pool (if pool supports encryption), it significantly improves security.
To enable encryption, use “ssl://” or “stratum+ssl://” prefix (or “tls” instead of “ssl”), for example: “-zpool ssl://asia1-zcash.flypool.org:3443”
-zwal Your ZCash wallet address. Also worker name and other options if pool supports it.
Pools that require “Login.Worker” instead of wallet address are not supported directly currently, but you can use “-allpools 1” option to mine there.
-zpsw Password for ZCash pool, use “x” as password.
You can use “config.txt” file instead of specifying options in command line.
If there are not any command line options, miner will check “config.txt” file for options.
If there is only one option in the command line, it must be configuration file name.
If there are two or more options in the command line, miner will take all options from the command line, not from configuration file.
Place one option per line, if first character of a line is “;” or “#”, this line will be ignored.
You can also use environment variables in “epools.txt” and “config.txt” files. For example, define “WORKER” environment variable and use it as “%WORKER%” in config.txt or in epools.txt.
flypool SSL/TLS connection:
ZecMiner64.exe -zpool ssl://eu1-zcash.flypool.org:3443 -zwal t1U7fJqYzmQyVNB2AyGthJJTrFgtVDhbXmB.YourWorkerName -zpsw x
suprnova SSL/TLS connection:
ZecMiner64.exe -zpool ssl://zec.suprnova.cc:2242 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword
miningpoolhub SSL/TLS connection (this pool detects encryption automatically so it uses same port as for unencrypted connection):
ZecMiner64.exe -zpool ssl://us-east.equihash-hub.miningpoolhub.com:20570 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword
coinmine SSL/TLS connection:
ZecMiner64.exe -zpool ssl://zec.coinmine.pl:7017 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword
flypool (unencrypted connection):
ZecMiner64.exe -zpool eu1-zcash.flypool.org:3333 -zwal t1U7fJqYzmQyVNB2AyGthJJTrFgtVDhbXmB.YourWorkerName -zpsw x
nanopool (unencrypted connection):
ZecMiner64.exe -zpool zec-eu1.nanopool.org:6666 -zwal t1U7fJqYzmQyVNB2AyGthJJTrFgtVDhbXmB.YourWorkerName -zpsw x
miningpoolhub (unencrypted connection)
ZecMiner64.exe -zpool us-east.equihash-hub.miningpoolhub.com:20570 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword
nicehash (unencrypted connection):
ZecMiner64.exe -zpool equihash.usa.nicehash.com:3357 -zwal 13PHHqne7e7W9G6aUqNVcFfkMoPADWkySZ -zpsw x
suprnova (unencrypted connection):
ZecMiner64.exe -zpool zec.suprnova.cc:2142 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword
coinmine (unencrypted connection):
ZecMiner64.exe -zpool zec.coinmine.pl:7007 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword
Miner supports remote monitoring/management via JSON protocol over raw TCP/IP sockets. You can also get recent console text lines via HTTP.
Start “EthMan.exe” from “Remote management” subfolder (Windows version only).
Check built-in help for more information. “API.txt” file contains more details about protocol.
- Windows 10 Defender recognizes miner as a virus, some antiviruses do the same. Miner is not a virus, add it to Defender exceptions.
I write miners since 2014. Most of them are recognized as viruses by some paranoid antiviruses, perhaps because I pack my miners to protect them from disassembling, perhaps because some people include them into their botnets, or perhaps these antiviruses are not good, I don’t know. For these years, a lot of people used my miners and nobody confirmed that my miner stole anything or did something bad.
Note that I can guarantee clean binaries only for official links in my posts on this forum (bitcointalk). If you downloaded miner from some other link - it really can be a virus.
However, my miners are closed-source so I cannot prove that they are not viruses. If you think that I write viruses instead of good miners - do not use this miner, or at least use it on systems without any valuable data.
- Install Catalyst v15.12.
- Disable overclocking.
- Reduce intensity ("-i" option).
- Set environment variables as described above.
- Set Virtual Memory 16 GB or more.
- Try “-old 1” option.
- Reboot computer.
- Check hardware, risers.
Q: Why do I see more shares for devfee than in my mining for the same time?
A: Most pools support variable diff, they change “target share” after some time after connection. For example, you have very powerful rig, after connection you will send shares very often. It takes some CPU time to check your shares so after some time pool will send higher share target and miner will send less shares (but they will have more value). When pool updates share target you will see “Pool sets new share target” line in the miner. This way pool can adjust the number of shares that miner sends and balance its load.
So check the log or console text to see current target for main mining thread and for devfee thread. For example:
DevFee: Pool sets new share target: 0x0083126e (diff: 500H) - this is for devfee mining connection
Pool sets new share target: 0x0024fa4f (diff: 1772H) - this is for main mining connection
As you can see, target share for main mining is higher in about 3.5 times, so for main mining miner sends in 3 times less shares (but they have 3x more value) than for devfee mining.
Q: Can I mix Polaris cards (RX 4xx/5xx) and Fury cards in same rig?
A: You will not get best speed for Polaris and Fury cards mixed in one rig in Windows. Possible solutions:
- Split Polaris and Fury GPUs to different rigs.
- Use Linux.
- Use “-asm 0” option for Fury cards (leave “asm 1” for Polaris cards) though they will have less speed in this mode.