Search the Community
Showing results for tags 'mining'.
Found 2 results
################################################# # dstm's ZCash Cuda miner ################################################# I've written it initially for my own purpose. It performs pretty well - so here it is. Compatible with devices having Compute Capability 5.0 and greater i.e. it should run fine on Maxwell/Pascal GPUs. Supports every server using the stratum protocol. If you have issues with certain pools pls. report them here. Contains 2% devfee. Suggestions are welcome. Download: Zcash Nvidia_Miner v0.6.2 Version 0.6.2 update: - fix ssl handshake failures - fix device selection bug introduced in 0.6.1 - make linux performance improvements introduced in 0.6.1 optional via 'mq-solver' parameter (due to issues on some systems) - improve device initialization on large systems Linux x64: Download Zcash_Nvidia for Linux Win x64 v0.6.2: Download Zcash_Nvidia for Windows Performance: 1080Ti 725-740 Sol/s 1070 440-450 Sol/s stock settings UI: Sample output mining on a rig with 8 GPUs. GPU0-7: 1070Ti Code: > GPU0 65C 75% | 507.9 Sol/s 504.9 Avg 269.8 I/s | 4.52 S/W 112 W | 3.74 100 39 ++++++++ > GPU1 64C 70% | 508.4 Sol/s 509.1 Avg 273.0 I/s | 4.57 S/W 111 W | 4.11 100 38 +++++++++ > GPU2 62C 70% | 512.9 Sol/s 514.0 Avg 274.0 I/s | 4.60 S/W 110 W | 2.62 100 37 +++++ > GPU3 61C 70% | 502.4 Sol/s 500.8 Avg 266.9 I/s | 4.48 S/W 113 W | 2.24 100 38 ++++++++* > GPU4 64C 70% | 508.6 Sol/s 508.2 Avg 272.9 I/s | 4.53 S/W 111 W | 1.49 100 38 ++++++++++++ > GPU5 57C 70% | 506.7 Sol/s 504.7 Avg 270.0 I/s | 4.53 S/W 110 W | 1.94 100 38 ++++++++++ > GPU6 59C 70% | 514.5 Sol/s 506.3 Avg 270.4 I/s | 4.55 S/W 112 W | 2.36 100 38 ++++++ > GPU7 64C 75% | 511.1 Sol/s 515.1 Avg 275.2 I/s | 4.62 S/W 109 W | 1.12 100 37 ++++++++ > ============== | 4072.6 Sol/s 4063.3 Avg 2172.1 I/s | 4.55 S/W 891 W | 19.63 100 37 ++++++++++ Sol/s: solutions per second Avg: average solutions per second I/s: iterations per second done by the GPU S/W: efficiency - average Sol/s per Watt W: power consuption in Watt last 3 colums: <shares per minute> <accepted shares ratio> <network latency in ms> > : indicates that a new job was received + : indicates one submitted share * : indicates one submitted dev fee share = : sum/average if mining on multiple GPUs Features: To get help just start zm without any arguments Code: ZM 0.6.2, dstm's ZCASH/Equihash Cuda Miner Usage: zm --server hostname --port port_nr --user user_name [--pass password] [options]... zm --cfg-file[=path] Stratum: --server Stratum server hostname prefix hostname with 'ssl://' for encrypted connections - e.g. ssl://mypool.com --port Stratum server port number --user Username --pass Worker password Options: --help Print this help --list-devices List available cuda devices --dev Space separated list of cuda devices to use. If this option is not given all available devices are used. --time Enable output of timestamps --color colorize the output --logfile [=path] Append logs to the file named by 'path' If 'path' is not given append to 'zm.log' in current working directory. --noreconnect Disable automatic reconnection on network errors. --temp-target =dev_id:temp-target[,dev_id:temp-target] ... In C - If set, enables temperature controller. The workload of each GPU will be continuously adjusted such that the temperature stays around this value. It is recommended to set your fan speed to a constant value when using this setting. Example: --temp-target=0:65,2:70 --intensity =dev_id:intensity[,dev_id:intensity] ... Reduce the load which is put on the GPU - valid intensity range ]1.0-0.0[. Example: --intensity=0:0.893,2:0.8 --telemetry [=iport]. Starts telemetry server. Telemetry data can be accessed using a web browser(http) or by json-rpc. If no arguments are given the server listens on 127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222 Valid port range [1025-65535] --cfg-file [=path] Use configuration file. All additional command line options are ignored - configuration is done only through configuration file. If 'path' is not given use 'zm.cfg' in current working directory. --pool =hostname,port_nr,user_name[,pass] Setup additional failover pools. Example: zm --server servername.com --port 1234 --user username BIG THANKS TO SWISSTRADER for providing access to hardware. Dependencies Linux: openssl 1.0 (for versions <= 0.5.7) Windows: .Net 2.0+ Version 0.6.2 - fix ssl handshake failures - fix device selection bug introduced in 0.6.1 - make linux performance improvements introduced in 0.6.1 optional via 'mq-solver' parameter (due to issues on some systems) - improve device initialization on large systems Version 0.6.1 - fix failover-pool not switching back on ssl errors - fix failover-pool not switching back on some servers - add support for stratum's client.reconnect rpc - support configuration of 'temp-target', 'intensity', 'pool' via cmd-line parameters - report current difficulty and target on term-ui - sort output by gpu_id on term-ui - colorize temperature above 70°C on term-ui - report intended fan speed on term-ui, web-ui, json-rpc - report power consumption on term-ui - improve performance on linux systems by ~2% Version 0.6 - failover pool support - introduce configuration file - introduce intensity option - support per gpu temp-target via cfg-file - support per gpu intensity via cfg-file - json-rpc report gpu_name, pci_bus_id, pci_device_id gpu_uuid - improve error reporting - improve handling of invalid server resposes - improve reconnection in cases where servers become reachable but respond with malformed data - ui: add colorized output - web-ui: use dark colors Version 0.5.8 con: add support for protocol v.01000020 link openssl statically Version 0.5.7 reduce cpu load minor performance improvements con: use single pool connection con: ssl: clear session data before reconnect nvml: handle invalid values Version 0.5.6 reduce cpu load minor performance improvements Version 0.5.5 con: handle failure of dev share pool con: disable reconnect limit logfile: disable buffering Version 0.5.4 fix: device selection fix: latency reporting add logfile support add option to disable auto reconnect handle disconnect periods in web/json stats add basic GPU responsiveness infrastructure ui: change timestamps to ISO 8601 format webui: report: uptime contime server user port json: report: uptime contime server user port version Version 0.5.3 cpu: reduce cpu load con: fix recon loop con: network latency measurement ui: add accepted/rejected shares ratio ui: add network latency ui: add information about selected devices Version 0.5.2 fix a race that might have corrupted shares net: tcp: disable the Nagle algorithm which reduces network latency in some circumstances net: lower keepalive for nat-networks Version 0.5.1 con: fix reconnection might have give up too early con: enable TCP Keepalive to prevent nat-routers from dropping the connection. ui: output rejected shares ui: optional output of timestamps telemetry: make web ui mobile friendly + add share stats telemetry: json: add more GPU stats Version 0.5 con: support set_extranonce rpc con: improve handling of temporary slow network conditions con: add monitoring support using web browser con: add monitoring support using json-rpc mp: rebalance queue sizes - this improves the solution rate as seen by the pools, especially on pools that submit new jobs often Version 0.4.5 fix: bad miner performance when using --temp-target on systems with many GPUs reduce temperature controller cpu usage Version 0.4.4 fix: Sol/W might have produced wrong values fix: Sum not shown if --dev was used fix: memory leak on reconnection improve stability Version 0.4.3 stratum: support more pools ui: flush stdout stream con: improve reconnections performance improvements 0.3-0.5 % Version 0.4.2 mp: more accurate time measurements ui: calculate efficiency Version 0.4.1 improve performance Version 0.4.0 temperature controller added cpu: reduce CPU usage con: improve pool support minor performance improvement Version 0.3.2 mp: improve stability con: support more pools con: more robust reconnection support for unreliable servers which often drop the connection ui: report GPU temperature Version 0.3.1 cpu: reduce CPU usage Version 0.3 con: support encrypted connections Version 0.2.2 con: Miner reconnects automatically on connection loss now, e.g. on DSL-disconnects / public IP-changes UI: report submitted devfee-shares Version 0.2.1 Performance improvements: - about 4% on Maxwell - about 1% on Pascal Version 0.2 - Improved pascal perfromance. - Added support for concurrent mining on multiple GPUs. - Be asynchronous where possible. - Security work
Claymore's Dual Ethereum + Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak AMD+NVIDIA GPU Miner. ========================= Latest version is v14.6 - Supercharged Edition: - now "-rxboost" option also supports old AMD cards (Hawaii, Tonga, Tahiti, Pitcairn), use "-rxboost 1" to improve hashrate up to 5% by applying some additional memory timings. - now "-rxboost" option supports all AMD drivers. - now "-strap" for AMD cards also supports AMD blockchain drivers. - some changes to further reduce stale shares a bit. - added "-minspeedtime" option. - added statistics for shares accepting time (min/max/average), press "s" to see it. - updated Remote Manager to show shares accepting time. - a few minor bug fixes and improvements. DOWNLOAD LINK: MEGA - Download Claymore's v14.6 FEATURES: - Supports applying optimized memory timings (straps) on-the-fly in Windows, without flashing VBIOS (currently Polaris, Vega, Nvidia 10xx cards only), up to 20% speedup. Best straps for Ethereum are included. - Supports new "dual mining" mode: mining both Ethereum and Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak at the same time, with no impact on Ethereum mining speed. Ethereum-only mining mode is supported as well. - Effective Ethereum mining speed is higher by 3-5% because of a completely different miner code - much less invalid and outdated shares, higher GPU load, optimized OpenCL code, optimized assembler kernels. - Supports both AMD and nVidia cards, even mixed. - No DAG files. - Supports all Stratum versions for Ethereum: can be used directly without any proxies with all pools that support eth-proxy, qtminer or miner-proxy. - Supports Ethereum and Siacoin solo mining. - Supports both HTTP and Stratum for Decred. - Supports both HTTP and Stratum for Siacoin. - Supports Stratum for Lbry, Pascal, Blake2s, Keccak. - Supports failover. - Displays detailed mining information and hashrate for every card. - Supports remote monitoring and management. - Supports GPU selection, built-in GPU overclocking features and temperature management. - Supports Ethereum forks (Expanse, etc). - Windows and Linux versions. This version is POOL/SOLO for Ethereum, POOL for Decred, POOL/SOLO for Siacoin, POOL for Lbry, POOL for Pascal, POOL for Blake2s, POOL for Keccak. For old AMD cards, Catalyst (Crimson) 15.12 is required for best performance and compatibility. For AMD 4xx/5xx cards (Polaris) you can use any recent drivers. For AMD cards, set the following environment variables, especially if you have 2...4GB cards: GPU_FORCE_64BIT_PTR 0 GPU_MAX_HEAP_SIZE 100 GPU_USE_SYNC_OBJECTS 1 GPU_MAX_ALLOC_PERCENT 100 GPU_SINGLE_ALLOC_PERCENT 100 This miner is free-to-use, however, current developer fee is 1%, every hour the miner mines for 36 seconds for developer. For all 2GB cards and 3GB cards devfee is 0%, so on these cards you can mine all ETH forks without devfee, this miner is completely free in this case. If some cards are 2...3GB and some >3GB, 2...3GB cards still mine for you during devfee time, only cards that have more than 3GB memory will be used for devfee mining. Miner displays appropriate messages during startup. Second coin (Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak) is mined without developer fee. So the developer fee is 0...1%, 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 and 3xx, 2GB or more. Recent nVidia videocards are supported as well. CONFIGURATION FILE 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. If for Ethereum-only mining: ethpool: EthDcrMiner64.exe -epool us1.ethpool.org:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x sparkpool: EthDcrMiner64.exe -epool eu.sparkpool.com:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x f2pool: EthDcrMiner64.exe -epool eth.f2pool.com:8008 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -eworker rig1 nanopool: EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -eworker rig1 nicehash: EthDcrMiner64.exe -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal 1LmMNkiEvjapn5PRY8A9wypcWJveRrRGWr -epsw x -esm 3 -allpools 1 -estale 0 Ethereum forks mining: EthDcrMiner64.exe -epool exp-us.dwarfpool.com:8018 -ewal 0xd69af2a796a737a103f12d2f0bcc563a13900e6f -epsw x -allcoins -1 Ethereum SOLO mining (assume geth is on 192.168.0.1:8545): FAILOVER Use "epools.txt" and "dpools.txt" files to specify additional pools (you can use "-epoolsfile" and "-dpoolsfile" options to use different filenames). These files have text format, one pool per line. Every pool has 3 connection attempts. Miner disconnects automatically if pool does not send new jobs for a long time or if pool rejects too many shares. If the first character of a line is ";" or "#", this line will be ignored. Do not change spacing, spaces between parameters and values are required for parsing. If you need to specify "," character in parameter value, use two commas - ,, will be treated as one comma. You can reload "epools.txt" and "dpools.txt" files in runtime by pressing "r" key. Pool specified in the command line is "main" pool, miner will try to return to it every 30 minutes if it has to use some different pool from the list. If no pool was specified in the command line then first pool in the failover pools list is main pool. You can change 30 minutes time period to some different value with "-ftime" option, or use "-ftime 0" to disable switching to main pool. You can also use environment variables in "epools.txt", "dpools.txt" and "config.txt" files. For example, define "WORKER" environment variable and use it as "%WORKER%" in config.txt or in epools.txt. You can also select current pool in runtime by pressing "e" or "d" key. REMOTE MONITORING/MANAGEMENT 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. KNOWN ISSUES - AMD cards: on some cards you can notice non-constant mining speed in dual mode, sometimes speed becomes a bit slower. This issue was mostly fixed in recent versions, but not completely. - AMD cards: in Linux with gpu-pro drivers, the list of GPUs may differ from the list of temperatures. You can use -di to change order of GPUs to match both lists. - nVidia cards: dual mode is not so effective as for AMD cards. - 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. TROUBLESHOOTING 1. Install Catalyst v15.12 for old AMD cards; for Fury, Polaris and Vega cards use latest blockchain drivers. 2. Disable overclocking. 3. Set environment variables as described above. 4. Set Virtual Memory 16 GB or more. 5. Reboot computer. 6. Check hardware, risers. 7. Set some timeout in .bat file before starting miner at system startup (30sec or even a minute), and try "-ethi 4" to check if it is more stable. It can help if miner is not stable on some system. FAQ - Miner works too slowly when I mine ETH/ETC but works fine when I mine some ETH fork. Check if you enabled "Compute Mode" in AMD drivers, also you can press "y" key to turn on "Compute Mode" in AMD drivers for all cards (Windows only). - I cannot mine ETH/ETC with Nvidia 3GB card in Windows 10. Windows 10 internally allocates about 20% of GPU memory so applications can use only 80% of GPU memory. Use Windows 7 or Linux. FAQ #2: 1. Please read Readme.txt or original post of this thread for command line samples, options description and FAQ.