Changes in version 4.9c (since 4.8c):
Added support for AMD RX5500 cards
Added support for the latest AMD Windows drivers 19.12.3
Adding support for AMD Linux drivers 19.50-967956
Adding option -rate 2 to use the command name "eth_submitHashRate" instead of "eth_submitHashrate" when solo mining
Fixed the problem with loading NVML with the latest Nvidia drivers
Fixed a problem that was introduced in 4.8c causing mismatching of the cards when using more than one value in -cclock or any other command-line argument with more than one value (i.e. when using different values for each card)
Added an HTML version of the documentation for better navigation and readability
Other small improvements and fixes.
PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supportsboth AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64and has a developer fee of 0.65% (the lowest in the industry). This means that every 90minutes the miner will mine for us, its developers, for 35 seconds.PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual miningEthash/Ubqhash with Blake2s.The speed is generally faster than Claymore's Ethereum miner in eth only mode(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower orhigher depending on the GPUs). To achieve highest possible speed on AMD cards it may be neededto manually adjust the GPU tune factor (a number from 8 to about 400, which can be changedinteractively with the + and - keys while the miner is running).If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner withminimal hassle as we support most of Claymore's command-line options and confirgurationfiles.Easy Plug&Play OS Linux with our miner: https://SimpleMining.netPlease note that PhoenixMiner is extensively tested on many mining rigs but there still may be some bugs.Additionally, we are actively working on bringing many new features in the future releases.If you encounter any problems or have feature requests, please post them here (in this thread).We will do our best to answer in timely fashion.Screenshot:
1. Quick startYou can download PhoenixMiner 4.9c from here:
https://mega.nz/#F!ybAX2QJb!TsBuMe2FhsRLh44yfGuzbw (MEGA)
If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):
If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):
Code:
File: PhoenixMiner_4.9c_Windows.zip
===================================
SHA-1: 63b7a990c0f4eb0bc26b1dd3d9e32f61b5e43864
SHA-256: cbed2c8395426c49a557c76e9e666aac81145c75aeeaa1624b4421cf81ca47d3
SHA-512: 628a7eb6424797b99b9beb4403a740cb969d8bcd7504b3f61eefced6f3f8e9adae438474d4f02a9eeb15e98c64ababe7720a411963e9232d5a82a21345090c69
File: PhoenixMiner_4.9c_Linux.tar.gz
====================================
SHA-1: f375c4b1b49f5acad6370358cdbb60eb41b0b453
SHA-256: 556f396549217f6142c12c6f43d935df91c648da0b60ff0dd012e6ed5b4ca8d1
SHA-512: e4f214b0767880249194e4cc22cc439b9f56c2f71cf254db436a043dcc3a2e424a547f98ba114a6e15d71053579ea7816e2a86bfe71e822073ebe95f659cfd0a
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
Here are the command line parameters for some of the more popular pools and coins:ethermine.org (ETH): PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3ethermine.org (ETH, secure connection): PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3ethpool.org (ETH): PhoenixMiner.exe -pool eu1.ethpool.org:3333 -pool2 us1.ethpool.org:3333 -wal YourEthWalletAddress.WorkerName -proto 3 dwarfpool.com (ETH): PhoenixMiner.exe -pool eth-eu.dwarfpool.com:8008 -wal YourEthWalletAddress/WorkerName -pass xnanopool.org (ETH): PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -wal YourEthWalletAddress/WorkerName -pass xnicehash (ethash): PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0f2pool (ETH): PhoenixMiner.exe -epool eth.f2pool.com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName miningpoolhub (ETH): PhoenixMiner.exe -pool us-east.ethash-hub.miningpoolhub.com:20535 -wal YourLoginName.WorkerName -pass x -proto 1coinotron.com (ETH): PhoenixMiner.exe -pool coinotron.com:3344 -wal YourLoginName.WorkerName -pass x -proto 1ethermine.org (ETC): PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal YourEtcWalletAddress.WorkerNameepool.io (ETC): PhoenixMiner.exe -pool eu.etc.epool.io:8008 -pool2 us.etc.epool.io:8008 -worker WorkerName -wal YourEtcWalletAddress -pass x -retrydelay 2whalesburg.com (ethash auto-switching): PhoenixMiner.exe -pool proxy.pool.whalesburg.com:8082 -wal YourEthWalletAddress -worker WorkerName -proto 2dwarfpool.com (EXP): PhoenixMiner.exe -pool exp-eu.dwarfpool.com:8018 -wal YourExpWalletAddress/WorkerNameminingpoolhub (MUSIC): PhoenixMiner.exe -pool europe.ethash-hub.miningpoolhub.com:20585 -wal YourLoginName.WorkerName -pass x -proto 1maxhash.org (UBIQ): PhoenixMiner.exe -pool ubiq-us.maxhash.org:10008 -wal YourUbqWalletAddress -worker WorkerName -coin ubqubiq.minerpool.net (UBIQ): PhoenixMiner.exe -pool lb.geo.ubiqpool.org:8001 -wal YourUbqWalletAddress -pass x -worker WorkerName -coin ubqubiqpool.io (UBIQ): PhoenixMiner.exe -pool eu2.ubiqpool.io:8008 -wal YourUbqWalletAddress.WorkerName -pass x -proto 4 -coin ubqminerpool.net (PIRL): PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerNamedodopool.com (Metaverse ETP): PhoenixMiner.exe -pool etp.dodopool.com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass xminerpool.net (Ellaism): PhoenixMiner.exe -pool ella.minerpool.net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass xetherdig.net (ETH PPS): PhoenixMiner.exe -pool etherdig.net:4444 -wal YourEthWalletAddress.WorkerName -proto 4 -pass xetherdig.net (ETH HVPPS): PhoenixMiner.exe -pool etherdig.net:3333 -wal YourEthWalletAddress.WorkerName -proto 4 -pass xepool.io (CLO): PhoenixMiner.exe -pool eu.clo.epool.io:8008 -pool2 us.clo.epool.io:8008 -worker WorkerName -wal YourEthWalletAddress -pass x -coin clo -retrydelay 2baikalmine.com (CLO): PhoenixMiner.exe -pool clo.baikalmine.com:3333 -wal YourEthWalletAddress -pass x -coin clo -worker rigName Dual-mining command-line examples:ETH on ethermine.org ETH, Blake2s on Nicehash: PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 -dpool blake2s.eu.nicehash.com:3361 -dwal YourBtcWalletAddress -dcoin blake2sNicehash (Ethash + Blake2s): PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0 -dpool blake2s.eu.nicehash.com:3361 -dwal YourBtcWalletAddress -dcoin blake2sProgPOW command-line examples:BCI on BCI-Server: PhoenixMiner.exe -pool eu-1.pool.bci-server.com:3869 -wal YourBciWalletAddress.Rig1 -coin bci -proto 12. Features, requirements, and limitations* Supports AMD RX5700, Radeon VII, Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM* Supports Nvidia 20x0, 16x0, 10x0 and 9x0 series as well as older cards with enough VRAM* Highly optimized OpenCL and CUDA cores for maximum ethash mining speed* Optional "green" kernels for RX580/570/560/480/470/460 to lower the power consumption by 2-3% with small, or no drop in hashrate* Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)* Dual mining ethash/Blake2s with lowest devfee of 0.9% (35 seconds defvee mining per each 65 minutes)* Advanced statistics: actual difficulty of each share, effective hashrate at the pool, and optional showing of estimated income in USD* DAG file generation in the GPU for faster start-up and DAG epoch switches* Supports all ethash mining pools and stratum protocols* Supports secure pool connections (e.g. ssl://eu1.ethermine.org:5555) to prevent IP hijacking attacks* Detailed statistics, including the individual cards hashrate, shares, temperature, fan speed, clocks, voltages, etc.* Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line)* Automatic GPU tuning for the AMD GPUs to achieve maximum performance with your rig* Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, Metaverse ETP, PGC, Akroma, WhaleCoin, Victorium, Nekonium, Mix, EtherGem, Aura, HBC, Genom, EtherZero, Callisto, DubaiCoin, MOAC, Ether-1, and EtherCC. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970).* Full compatibility with the industry standard Claymore's Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management.* Supports the new Ubqhash algorithm for the UBQ coin. Please note that you must add -coin ubq to your command line (or COIN: ubq to your epools.txt file) in order to mine UBQ* Supports the ProgPOW algorithm for the Bitcoin Interest (BCI) coin mining. Please note that you must add -coin bci to your command line (or COIN: bci to your epools.txt file) in order to mine BCI* Supports the ProgPOW algorithm for mining BCI.* More features coming soon!PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.), or Linux x64 (tested on Ubuntu LTSand Debian stable).PhoenixMiner also supports dual mining (simultaneous mining of ethash/ubqhash and other cryptocoin algorithm).Currently we support only Blake2s as secondary algorithm for dual mining. Note that when using dual mining,there is no devfee on the secondary coin but the devfee on the main coin is increased to 0.9%. In other words,if you are using the dual mining feature PhoenixMiner will mine for us for 35 seconds every 65 minutes.Solo mining is supported since version 2.7c.While the miner is running, you can use some interactive commands. Press the key 'h' while theminer's console window has the keyboard focus to see the list of the available commands. Theinteractive commands are also listed at the end of the following section.3. Command-line argumentsNote that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum minerso you can use the same command line options as the ones you would have used with Claymore's miner.Pool options: -pool <host:port> Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining) -wal <wallet> Ethash wallet (some pools require appending of user name and/or worker) -pass <password> Ethash password (most pools don't require it, use 'x' as password if unsure) -worker <name> Ethash worker name (most pools accept it as part of wallet) -proto <n> Selects the kind of stratum protocol for the ethash pool: 1: miner-proxy stratum spec (e.g. coinotron) 2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools 3: qtminer (e.g. ethpool) 4: EthereumStratum/1.0.0 (e.g. nicehash) 5: EthereumStratum/2.0.0 -coin <coin> Ethash coin to use for devfee to avoid switching DAGs: auto: Try to determine from the pool address (default) eth: Ethereum etc: Ethereum Classic exp: Expanse music: Musicoin ubq: UBIQ pirl: Pirl ella: Ellaism etp: Metaverse ETP pgc: Pegascoin akroma: Akroma whale: WhaleCoin vic: Victorium nuko: Nekonium mix: Mix egem: EtherGem aura: Aura hbc: Hotelbyte Coin gen: Genom etz: EtherZero clo: Callisto dbix: DubaiCoin moac: MOAC etho: Ether-1 etcc: EtherCC yoc: Yocoin b2g: Bitcoiin2Gen esn: Ethersocial ath: Atheios reosc: REOSC qkc: QuarkChain bci: Bitcoin Interest -stales <n> Submit stales to ethash pool: 1 - yes (default), 0 - no -pool2 <host:port> Failover ethash pool address. Same as -pool but for the failover pool -wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too) -pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too) -worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too) -proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too) -coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too) -stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no -dpool <host:port> Dual mining pool address -dwal <wallet> Dual mining wallet -dpass <password> Dual mining pool password (most pools don't require it, use 'x' as password if unsure) -dworker <name> Dual mining worker name -dcoin blake2s Currently only the Blake2s algorithm is supported for dual mining. If you want to put all dual mining pools in dpools.txt, you need to set -dcoin blake2s in the command-line or in config.txt to force the miner to load the dual mining pools from dpools.txt -dstales <n> Submit stales to the dual mining pool: 1 - yes (default), 0 - noGeneral pool options: -fret <n> Switch to next pool afer N failed connection attempts (default: 3) -ftimeout <n> Reconnect if no new ethash job is receved for n seconds (default: 600) -ptimeout <n> Switch back to primary pool after n minutes. This setting is 30 minutes by default; set to 0 to disable automatic switch back to primary pool. -retrydelay <n> Seconds to wait before reconnecting (default: 20) -gwtime <n> Recheck period for Solo/GetWork mining (default: 200 ms) -rate <n> Report hashrate to the pool: 1 - yes, 0 - no (1 is the default), 2 - (for solo mining only) use alternative name of the report method "eth_submitHashRate" instead of "eth_submitHashrate"Benchmark mode: -bench [<n>],-benchmark [<n>] Benchmark mode, optionally specify DAG epoch. Use this to test your rig. If you specify only the -bench option, you will benchmark the ethash algorithm. If you want to bench the dual mining, use the options -bench <n> -dcoin blake2s. If you want to benchmark the ProgPOW BCI algorithm, use the options -bench <n> -coin bciRemote control options: -cdm <n> Selects the level of support of the CDM remote monitoring: 0: disabled 1: read-only - this is the default 2: full (only use on secure connections) -cdmport <port> Set the CDM remote monitoring port (default is 3333). You can also specify <ip_addr:port> if you have a secure VPN connection and want to bind the CDM port to it -cdmpass <pass> Set the CDM remote monitoring password -cdmrs Reload the settings if config.txt is edited/uploaded remotely. Note that most options require restart in order to change. Currently the follwing options can be changed without restarting: -mi, -gt, -sci, -clf, -nvf, and all hardware control parameters (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).Mining options: -amd Use only AMD cards -acm Turn on AMD compute mode on the supported GPUs. This is equivalent of pressing 'y' in the miner console. -nvidia Use only Nvidia cards -gpus <123 ..n> Use only the specified GPUs (if more than 10, separate the indexes with comma) -mi <n> Set the mining intensity (0 to 14; 12 is the default for the new kernels). You may specify this option per-GPU. -gt <n> Set the GPU tuning parameter (6 to 400). The default is 15. You can change the tuning parameter interactively with the '+' and '-' keys in the miner's console window. If you don't specify -gt or you specify value 0, the miner will start auto-tuning to determine the best GT value for each GPU Note that when the GPU is dual-mining, it ignores the -gt values, and uses -sci instead. -sci <n> Set the dual mining intensity (1 to 1000). The default is 30. As you increase the value of -sci, the secondary coin hashrate will increase but the price will be higher power consumption and/or lower ethash hashrate. You can change the this parameter interactively with the '+' and '-' keys in the miner console window. You may specify this option per-GPU. If you set -sci to 0, the miner will use auto-tuning to determine the best value, while trying to maximize the ethash hashrate regardless of the secondary coin hashrate. -clKernel <n> Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative, 3 - turbo (1 is the default) -clGreen <n> Use the power-efficient ("green") kernels (0: no, 1: yes; default: 0). You may specify this option per-GPU. Note that you have to run auto-tune again as the optimal GT values are completely different for the green kernels -clNew <n> Use the new AMD kernels (0: no, 1: yes; default: 1) -clf <n> AMD kernel sync (0: never, 1: periodic; 2: always; default: 1) -nvKernel <n> Type of Nvidia kernel: 0 auto (default), 1 old (v1), 2 newer (v2), 3 latest (v3). Note that v3 kernels are only supported on GTX10x0 GPUs. Also note that dual mining is supported only by v2 kernels. You may specify this option per-GPU. -nvdo <n> Enable Nvidia driver-specific optimizations (0 - no, the default; 1 - yes). Try -nvdo 1 if your are unstable. You may specify this option per-GPU. -nvNew <n> Use new Nvidia kernels if supported (0: no, 1: yes; default: 1) -nvf <n> Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU. -mode <n> Mining mode (0: dual mining if dual pool(s) are specified; 1: ethash only even if dual pools are specified). You may specify this option per-GPU. -list List the detected GPUs devices and exit -gbase <n> Set the index of the first GPU (0 or 1, default: 1) -minRigSpeed <n> Restart the miner if avg 5 min speed is below <n> MH/s -eres <n> Allocate DAG buffers big enough for n epochs ahead (default: 2) to avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability -lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs (0-3, default: 0 - fastest, 3 - slowest). -gser <n> Serializing DAG creation on multiple GPUs (0 - no serializing, all GPUs generate the DAG simultaneously, this is the default; 1 - partial overlap of DAG generation on each GPU; 2 - no overalp (each GPU waits until the previous one has finished generating the DAG); 3-10 - from 1 to 8 seconds delay after each GPU DAG generation before the next one) -gpureset <n> Fully reset GPU when paused (0 - no, 1 - yes; default: no, except on 1080Ti). You may specify this option per-GPU. -altinit Use alternative way to initialize AMD cards to prevent startup crashes -rvram <n> Minimum free VRAM in MB (-1: don't check; default: 384 for Windows, and 128 for Linux) -wdog <n> Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The watchdog timer checks periodically if any of the GPUs freezes and if it does, restarts the miner (see the -rmode command-line parameter for the restart modes) -wdtimeout <n> Watchdog timeout (30 - 300; default 45 seconds). You can use this parameter to increase the default watchdog timeout in case it restarts the miner needlessly -rmode <n> Selects the restart mode when a GPU crashes or freezes: 0: disabled - miner will shut down instead of restarting 1: restart with the same command line options - this is the default 2: reboot (shut down miner and execute reboot.bat) -log <n> Selects the log file mode: 0: disabled - no log file will be written 1: write log file but don't show debug messages on screen (default) 2: write log file and show debug messages on screen -logfile <name> Set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there is no asterisk in the logfile name, the new log entries will be added to end of the same file. If you want to use the same logfile but the contents to be overwritten every time when you start the miner, put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$). -logdir <path> Set a path where the logfile(s) will be created -logsmaxsize <n> Maximum size of the logfiles in MB. The default is 200 MB (use 0 to turn off the limitation). On startup, if the logfiles are larger than the specified limit, the oldest are deleted. If you use a single logfile (by using -logfile), then it is truncated if it is bigger than the limit and a new one is created. -config <name> Load a file with configuration options that will be added to the command-line options. Note that the order is important. For example, if we have a config.txt file that contains -cclock 1000 and we specify command line -cclock 1100 -config config.txt, the options from the config.txt file will take precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100) then the second option takes precedence and the resulting -cclock will be 1100. Note that only one -config option is allowed. Also note that if you reload the config file with 'c' key or with the remote interface, its options will take precedence over whatever you have specified in the command-line. -timeout <n> Restart miner according to -rmode after n minutes -pauseat <hh:mm> Pause the miner at hh::mm (24 hours time). You can specify multiple times: -pauseat 6:00,12:00 -resumeat <hh:mm> Resume the miner at hh::mm (24 hours time). You can specify multiple times: -resumeat 8:00,22:00 -gswin <n> GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats) -gsi <n> Speed stats interval (5-30 sec; default: 5; use 0 to disable). The detailed stats are still shown every 45 seconds and aren't affected by the -gsi value -astats <n> Show advanced stats from Web sources (0: no; 1: yes). By default the coin exchange rates are updated every 4 hours, and the coin difficulty is updated every 8 hours. You can increase these periods by specifying for example -astats 12, which will increase update periods to 12 and 24 hours respectively -gpow <n> Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead -li <n> Another way to lower the GPU usage. Bigger n values mean less GPU utilization; the default is 0. -resetoc Reset the hardware overclocking settings on startup -leaveoc Do not reset overclocking settings when closing the minerHardware control options, use comma to specify different values for each GPU: -tt <n> Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards, 1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %) -hstats <n> Level of hardware monitoring: 0 - temperature and fan speed only; 1 - temperature, fan speed, and power; 2 - full (include core/memory clocks, voltages, P-states). The default is 1. -pidle <n> Idle power consumption of the rig in W. Will be added to the GPU power consumption when calculating the total power consumption of the rig. -ppf <n> The power usage of each GPU will be multiplied by this value to get the actual usage. This value is in percent, so for example if the GPU reports 100 W power usage and you have specified -ppf 106 the GPU power usage will be calculated to be 100 * (106 / 100) = 106 W. This allows you to correct for the efficiency of the PSUs and the individual GPUs. You can also specify this value for each GPU separately. -prate <n> Price of the electricity in USD per kWh (e.g. -prate 0.1). If specified the miner will calculate the rig daily electricity cost -fanmin <n> Set fan control min speed in % (-1 for default) -fanmax <n> Set fan control max speed in % (-1 for default) -fcm <n> Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 - forced fan control; default: 0) -tmax <n> Set fan control max temperature (0 for default) -powlim <n> Set GPU power limit in % (from -75 to 75, 0 for default) -cclock <n> Set GPU core clock in MHz (0 for default). For Nvidia cards use relative values (e.g. -300 or +400) -cvddc <n> Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400) -mclock <n> Set GPU memory clock in MHz (0 for default) -mvddc <n> Set GPU memory voltage in mV (0 for default) -tstop <n> Pause a GPU when temp is >= n deg C (0 for default; i.e. off) -tstart <n> Resume a GPU when temp is <= n deg C (0 for default; i.e. off) -mt <n> VRAM timings (AMD under Windows only): 0 - default VBIOS values; 1 - faster timings; 2 - fastest timings. The default is 0. This is useful for mining with AMD cards without modding the VBIOS. If you have modded BIOS, it is probably faster than even -mt 2General Options: -v,--version Show the version and exit -vs Show short version string (e.g. "4.1c") and exit -h,--help Show information about the command-line options and exitPer-GPU optionsSome of the PhoenixMiner options can provide either the same setting for all GPUs, or a differentsetting for each of the GPUs. For example, to specify the -gt value for all cards you would write-gt 90 but if you want to specify a different GT value for each of the cards, use something like this:-gt 20,15,40,90,90 for a five-GPU mining rig. This would set GT to 20 for the first GPU, 15 for the secondGPU, and so on. If you specify less values than you have GPUs, the rest of the GPUs will use the defaultvalue for the parameter.You can also use another, more flexible way of specifying different values for the different cards.This is best explained by example: -cclock *:1100,1-3:1090,4:1300 - here we are setting core clockto 1100 MHz for all cards, except the cards 1 to 3, on which it is set to 1090 MHz, and card 4 to 1300 MHz.The part before the colon (:) is the selector, which selects the GPUs for which the value after the colon is applied. The selector can be: - single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU - range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5 - asterisk, which sets the value for all GPUs - label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards - arbitrary string that starts with letter and can contain letters, numbers and asterisks, which is matched with the GPU name as listed by PhoenixMiner. Example: gtx*1070:+500 will set value +500 for all cards which contain 'gtx' and '1070' in their names with anything between them. This will match 'Nvidia GeForce GTX 1070' but not 'Nvidia GeForce 1070'. Note that if more than one selector matches given card, than only the last one counts.Example: -cclock *:1100,1-4:1090,2:1300 will set card 2 to 1300; cards 1,2, and 4 to 1090;and the rest of the cards to 1100 MHz core clock. Additionally, while the miner is running, you can use the following interactive commandsin the console window by pressing one of these keys: s Print detailed statistics 1-9 Pause/resume GPU1 ... GPU9 (if you have more than 9 GPUs, type 010 for card 10, 011 for card 11, etc.) p Pause/resume the whole miner +,- Increase/decrease GPU tuning parameter g Reset the GPU tuning parameter (and stop auto-tuning if active) x Select the GPU(s) for manual or automatic GT tuning z Start AMD auto-tune process r Reload epools.txt and switch to primary ethash pool e Select the current ethash pool (if you have more than 9 pools in the list, type 010 for pool 10, 011 for pool 11, etc.) d Select the current dual-mining pool y Turn on AMD Compute mode if it is off on some of the GPUs c Reload the config.txt file (some settings require restart, see -cdmrs option above for details) h Print this short help 4. Configuration filesNote that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum minerso you can use your existing configuration files without any changes.Instead of using command-line options, you can also control PhoenixMiner with configurationfiles. If you run PhoenixMiner.exe without any options, it will search for the file config.txtin the current directory and will read its command-line options from it. If you want, you canuse file with another name by specifying its name as the only command-line optionwhen running PhoenixMiner.exe.You will find an example config.txt file in the PhoenixMiner's directory.Instead of specifying the pool(s) directly on the command line, you can use another configurationfile for this, named epools.txt. There you can specify one pool per line (you will find an exampleepools.txt file in the PhoenixMiner's directory).For the dual mining pools, you can use the dpools.txt file, which has the same format as epools.txtbut for the secondary coin. You will find an example epools.txt file in the PhoenixMiner's directory.Note that unlike the epools.txt, which is loaded each time when the miner starts, the dpools.txt fileis only read if you specify a dual mining pool on the command line with -dpool, or at least addthe -dcoin blake2s command-line option.The advantages of using config.txt and epools.txt/dpools.txt files are:- If you have multiple rigs, you can copy and paste all settings with these files- If you control your rigs via remote control, you can change pools and even the miner options byuploading new epools.txt files to the miner, or by uploading new config.txt file and restartingthe miner.5. Remote monitoring and managementPhoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring andmanagement. This means that you can use any tools that are build to support Claymore's dual miner,including the "Remote manager" application that is part of Claymore's dual miner package.We are working on much more powerful and secure remote monitoring and control functionality andcontrol center application, which will allow better control over your remote or local rigs and someunique features to increase your mining profits.6. Hardware control options Here are some important notes about the hardware control options:
Hardware control options are supported for both AMD and Nvidia cards under Windows. Under Linux most options are supported only for AMD cards.
If you specify a single value (e.g. -cvddc 1150), it will be used on all cards. Specify different values for each card like this (separate with comma): -cvddc 1100,1100,1150,1120,1090 If the specified values are less than the number of GPUs, the rest of GPUs will use the default values.
We have tested only on relatively recent AMD GPUs (RX460/470/480/560/570/580, Vega, Radeon VII, RX5700). Your results may vary with older GPUs.
The blockchain beta drivers from AMD show quite unstable results - often the voltages don't stick at all or revert back to the default after some time. For best results use the newer drivers from AMD: 18.5.1 or later, where most of the bugs are fixed.
-tmax specifies the temperature at which the GPU should start to throttle (because the fans can't keep up).
If you use other programs for hardware control, conflicts are possible and quite likely. Use something like GPU-Z to monitor the voltages, etc. MSI Afterburner also seems to behave OK (so you can use it to control the Nvidia cards while AMD cards are controller by PhoenixMiner).
This should be obvious but still: if given clocks/voltages are causing crashes/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options.
If you have problems with hardware control options of PhoenixMiner and you were using something else to control clocks, fans, and voltages (MSI Aftrerburner, OverdriveNTool, etc.), which you were happy with, it is probably best to keep using it and ignore the hardware control options of PhoenixMiner (or use only some of them and continue tweaking the rest with your third-party tools).
Changes in version 4.9c (since 4.8c): Added support for AMD RX5500 cards Added support for the latest AMD Windows drivers 19.12.3 Adding support for AMD Linux drivers 19.50-967956 Adding option -rate 2 to use the command name "eth_submitHashRate" instead of "eth_submitHashrate" when solo mining Fixed the problem with loading NVML with the latest Nvidia drivers Fixed a problem that was introduced in 4.8c causing mismatching of the cards when using more than one value in -cclock or any other command-line argument with more than one value (i.e. when using different values for each card) Added an HTML version of the documentation for better navigation and readability Other small improvements and fixes. PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supportsboth AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64and has a developer fee of 0.65% (the lowest in the industry). This means that every 90minutes the miner will mine for us, its developers, for 35 seconds.PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI, and dual miningEthash/Ubqhash with Blake2s.The speed is generally faster than Claymore's Ethereum miner in eth only mode(we have measured about 0.4-1.3% speed improvement but your results may be slightly lower orhigher depending on the GPUs). To achieve highest possible speed on AMD cards it may be neededto manually adjust the GPU tune factor (a number from 8 to about 400, which can be changedinteractively with the + and - keys while the miner is running).If you have used Claymore's Dual Ethereum miner, you can switch to PhoenixMiner withminimal hassle as we support most of Claymore's command-line options and confirgurationfiles.Easy Plug&Play OS Linux with our miner: https://SimpleMining.netPlease note that PhoenixMiner is extensively tested on many mining rigs but there still may be some bugs.Additionally, we are actively working on bringing many new features in the future releases.If you encounter any problems or have feature requests, please post them here (in this thread).We will do our best to answer in timely fashion.Screenshot: 1. Quick startYou can download PhoenixMiner 4.9c from here: https://mega.nz/#F!ybAX2QJb!TsBuMe2FhsRLh44yfGuzbw (MEGA) If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows): If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows): Code: File: PhoenixMiner_4.9c_Windows.zip =================================== SHA-1: 63b7a990c0f4eb0bc26b1dd3d9e32f61b5e43864 SHA-256: cbed2c8395426c49a557c76e9e666aac81145c75aeeaa1624b4421cf81ca47d3 SHA-512: 628a7eb6424797b99b9beb4403a740cb969d8bcd7504b3f61eefced6f3f8e9adae438474d4f02a9eeb15e98c64ababe7720a411963e9232d5a82a21345090c69 File: PhoenixMiner_4.9c_Linux.tar.gz ==================================== SHA-1: f375c4b1b49f5acad6370358cdbb60eb41b0b453 SHA-256: 556f396549217f6142c12c6f43d935df91c648da0b60ff0dd012e6ed5b4ca8d1 SHA-512: e4f214b0767880249194e4cc22cc439b9f56c2f71cf254db436a043dcc3a2e424a547f98ba114a6e15d71053579ea7816e2a86bfe71e822073ebe95f659cfd0a File: PhoenixMiner_NVRTC_Windows.zip ==================================== SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4 Here are the command line parameters for some of the more popular pools and coins:ethermine.org (ETH): PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName -proto 3ethermine.org (ETH, secure connection): PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3ethpool.org (ETH): PhoenixMiner.exe -pool eu1.ethpool.org:3333 -pool2 us1.ethpool.org:3333 -wal YourEthWalletAddress.WorkerName -proto 3 dwarfpool.com (ETH): PhoenixMiner.exe -pool eth-eu.dwarfpool.com:8008 -wal YourEthWalletAddress/WorkerName -pass xnanopool.org (ETH): PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -wal YourEthWalletAddress/WorkerName -pass xnicehash (ethash): PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0f2pool (ETH): PhoenixMiner.exe -epool eth.f2pool.com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName miningpoolhub (ETH): PhoenixMiner.exe -pool us-east.ethash-hub.miningpoolhub.com:20535 -wal YourLoginName.WorkerName -pass x -proto 1coinotron.com (ETH): PhoenixMiner.exe -pool coinotron.com:3344 -wal YourLoginName.WorkerName -pass x -proto 1ethermine.org (ETC): PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal YourEtcWalletAddress.WorkerNameepool.io (ETC): PhoenixMiner.exe -pool eu.etc.epool.io:8008 -pool2 us.etc.epool.io:8008 -worker WorkerName -wal YourEtcWalletAddress -pass x -retrydelay 2whalesburg.com (ethash auto-switching): PhoenixMiner.exe -pool proxy.pool.whalesburg.com:8082 -wal YourEthWalletAddress -worker WorkerName -proto 2dwarfpool.com (EXP): PhoenixMiner.exe -pool exp-eu.dwarfpool.com:8018 -wal YourExpWalletAddress/WorkerNameminingpoolhub (MUSIC): PhoenixMiner.exe -pool europe.ethash-hub.miningpoolhub.com:20585 -wal YourLoginName.WorkerName -pass x -proto 1maxhash.org (UBIQ): PhoenixMiner.exe -pool ubiq-us.maxhash.org:10008 -wal YourUbqWalletAddress -worker WorkerName -coin ubqubiq.minerpool.net (UBIQ): PhoenixMiner.exe -pool lb.geo.ubiqpool.org:8001 -wal YourUbqWalletAddress -pass x -worker WorkerName -coin ubqubiqpool.io (UBIQ): PhoenixMiner.exe -pool eu2.ubiqpool.io:8008 -wal YourUbqWalletAddress.WorkerName -pass x -proto 4 -coin ubqminerpool.net (PIRL): PhoenixMiner.exe -pool pirl.minerpool.net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerNamedodopool.com (Metaverse ETP): PhoenixMiner.exe -pool etp.dodopool.com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass xminerpool.net (Ellaism): PhoenixMiner.exe -pool ella.minerpool.net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass xetherdig.net (ETH PPS): PhoenixMiner.exe -pool etherdig.net:4444 -wal YourEthWalletAddress.WorkerName -proto 4 -pass xetherdig.net (ETH HVPPS): PhoenixMiner.exe -pool etherdig.net:3333 -wal YourEthWalletAddress.WorkerName -proto 4 -pass xepool.io (CLO): PhoenixMiner.exe -pool eu.clo.epool.io:8008 -pool2 us.clo.epool.io:8008 -worker WorkerName -wal YourEthWalletAddress -pass x -coin clo -retrydelay 2baikalmine.com (CLO): PhoenixMiner.exe -pool clo.baikalmine.com:3333 -wal YourEthWalletAddress -pass x -coin clo -worker rigName Dual-mining command-line examples:ETH on ethermine.org ETH, Blake2s on Nicehash: PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal YourEthWalletAddress.WorkerName -proto 3 -dpool blake2s.eu.nicehash.com:3361 -dwal YourBtcWalletAddress -dcoin blake2sNicehash (Ethash + Blake2s): PhoenixMiner.exe -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0 -dpool blake2s.eu.nicehash.com:3361 -dwal YourBtcWalletAddress -dcoin blake2sProgPOW command-line examples:BCI on BCI-Server: PhoenixMiner.exe -pool eu-1.pool.bci-server.com:3869 -wal YourBciWalletAddress.Rig1 -coin bci -proto 12. Features, requirements, and limitations* Supports AMD RX5700, Radeon VII, Vega, 580/570/480/470, 460/560, Fury, 390/290 and older AMD GPUs with enough VRAM* Supports Nvidia 20x0, 16x0, 10x0 and 9x0 series as well as older cards with enough VRAM* Highly optimized OpenCL and CUDA cores for maximum ethash mining speed* Optional "green" kernels for RX580/570/560/480/470/460 to lower the power consumption by 2-3% with small, or no drop in hashrate* Lowest developer fee of 0.65% (35 seconds defvee mining per each 90 minutes)* Dual mining ethash/Blake2s with lowest devfee of 0.9% (35 seconds defvee mining per each 65 minutes)* Advanced statistics: actual difficulty of each share, effective hashrate at the pool, and optional showing of estimated income in USD* DAG file generation in the GPU for faster start-up and DAG epoch switches* Supports all ethash mining pools and stratum protocols* Supports secure pool connections (e.g. ssl://eu1.ethermine.org:5555) to prevent IP hijacking attacks* Detailed statistics, including the individual cards hashrate, shares, temperature, fan speed, clocks, voltages, etc.* Unlimited number of fail-over pools in epools.txt configuration file (or two on the command line)* Automatic GPU tuning for the AMD GPUs to achieve maximum performance with your rig* Supports devfee on alternative ethash currencies like ETC, EXP, Music, UBQ, Pirl, Ellaism, Metaverse ETP, PGC, Akroma, WhaleCoin, Victorium, Nekonium, Mix, EtherGem, Aura, HBC, Genom, EtherZero, Callisto, DubaiCoin, MOAC, Ether-1, and EtherCC. This allows you to use older cards with small VRAM or low hashate on current DAG epochs (e.g. GTX970).* Full compatibility with the industry standard Claymore's Dual Ethereum miner, including most of command-line options, configuration files, and remote monitoring and management.* Supports the new Ubqhash algorithm for the UBQ coin. Please note that you must add -coin ubq to your command line (or COIN: ubq to your epools.txt file) in order to mine UBQ* Supports the ProgPOW algorithm for the Bitcoin Interest (BCI) coin mining. Please note that you must add -coin bci to your command line (or COIN: bci to your epools.txt file) in order to mine BCI* Supports the ProgPOW algorithm for mining BCI.* More features coming soon!PhoenixMiner requires Windows x64 (Windows 7, Windows 10, etc.), or Linux x64 (tested on Ubuntu LTSand Debian stable).PhoenixMiner also supports dual mining (simultaneous mining of ethash/ubqhash and other cryptocoin algorithm).Currently we support only Blake2s as secondary algorithm for dual mining. Note that when using dual mining,there is no devfee on the secondary coin but the devfee on the main coin is increased to 0.9%. In other words,if you are using the dual mining feature PhoenixMiner will mine for us for 35 seconds every 65 minutes.Solo mining is supported since version 2.7c.While the miner is running, you can use some interactive commands. Press the key 'h' while theminer's console window has the keyboard focus to see the list of the available commands. Theinteractive commands are also listed at the end of the following section.3. Command-line argumentsNote that PhoenixMiner supports most of the command-line options of Claymore's dual Ethereum minerso you can use the same command line options as the ones you would have used with Claymore's miner.Pool options: -pool <host:port> Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining) -wal <wallet> Ethash wallet (some pools require appending of user name and/or worker) -pass <password> Ethash password (most pools don't require it, use 'x' as password if unsure) -worker <name> Ethash worker name (most pools accept it as part of wallet) -proto <n> Selects the kind of stratum protocol for the ethash pool: 1: miner-proxy stratum spec (e.g. coinotron) 2: eth-proxy (e.g. dwarfpool, nanopool) - this is the default, works for most pools 3: qtminer (e.g. ethpool) 4: EthereumStratum/1.0.0 (e.g. nicehash) 5: EthereumStratum/2.0.0 -coin <coin> Ethash coin to use for devfee to avoid switching DAGs: auto: Try to determine from the pool address (default) eth: Ethereum etc: Ethereum Classic exp: Expanse music: Musicoin ubq: UBIQ pirl: Pirl ella: Ellaism etp: Metaverse ETP pgc: Pegascoin akroma: Akroma whale: WhaleCoin vic: Victorium nuko: Nekonium mix: Mix egem: EtherGem aura: Aura hbc: Hotelbyte Coin gen: Genom etz: EtherZero clo: Callisto dbix: DubaiCoin moac: MOAC etho: Ether-1 etcc: EtherCC yoc: Yocoin b2g: Bitcoiin2Gen esn: Ethersocial ath: Atheios reosc: REOSC qkc: QuarkChain bci: Bitcoin Interest -stales <n> Submit stales to ethash pool: 1 - yes (default), 0 - no -pool2 <host:port> Failover ethash pool address. Same as -pool but for the failover pool -wal2 <wallet> Failover ethash wallet (if missing -wal will be used for the failover pool too) -pass2 <password> Failover ethash password (if missing -pass will be used for the failover pool too) -worker2 <name> Failover ethash worker name (if missing -worker will be used for the failover pool too) -proto2 <n> Failover ethash stratum protocol (if missing -proto will be used for the failover pool too) -coin2 <coin> Failover devfee Ethash coin (if missing -coin will be used for the failover pool too) -stales2 <n> Submit stales to the failover pool: 1 - yes (default), 0 - no -dpool <host:port> Dual mining pool address -dwal <wallet> Dual mining wallet -dpass <password> Dual mining pool password (most pools don't require it, use 'x' as password if unsure) -dworker <name> Dual mining worker name -dcoin blake2s Currently only the Blake2s algorithm is supported for dual mining. If you want to put all dual mining pools in dpools.txt, you need to set -dcoin blake2s in the command-line or in config.txt to force the miner to load the dual mining pools from dpools.txt -dstales <n> Submit stales to the dual mining pool: 1 - yes (default), 0 - noGeneral pool options: -fret <n> Switch to next pool afer N failed connection attempts (default: 3) -ftimeout <n> Reconnect if no new ethash job is receved for n seconds (default: 600) -ptimeout <n> Switch back to primary pool after n minutes. This setting is 30 minutes by default; set to 0 to disable automatic switch back to primary pool. -retrydelay <n> Seconds to wait before reconnecting (default: 20) -gwtime <n> Recheck period for Solo/GetWork mining (default: 200 ms) -rate <n> Report hashrate to the pool: 1 - yes, 0 - no (1 is the default), 2 - (for solo mining only) use alternative name of the report method "eth_submitHashRate" instead of "eth_submitHashrate"Benchmark mode: -bench [<n>],-benchmark [<n>] Benchmark mode, optionally specify DAG epoch. Use this to test your rig. If you specify only the -bench option, you will benchmark the ethash algorithm. If you want to bench the dual mining, use the options -bench <n> -dcoin blake2s. If you want to benchmark the ProgPOW BCI algorithm, use the options -bench <n> -coin bciRemote control options: -cdm <n> Selects the level of support of the CDM remote monitoring: 0: disabled 1: read-only - this is the default 2: full (only use on secure connections) -cdmport <port> Set the CDM remote monitoring port (default is 3333). You can also specify <ip_addr:port> if you have a secure VPN connection and want to bind the CDM port to it -cdmpass <pass> Set the CDM remote monitoring password -cdmrs Reload the settings if config.txt is edited/uploaded remotely. Note that most options require restart in order to change. Currently the follwing options can be changed without restarting: -mi, -gt, -sci, -clf, -nvf, and all hardware control parameters (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).Mining options: -amd Use only AMD cards -acm Turn on AMD compute mode on the supported GPUs. This is equivalent of pressing 'y' in the miner console. -nvidia Use only Nvidia cards -gpus <123 ..n> Use only the specified GPUs (if more than 10, separate the indexes with comma) -mi <n> Set the mining intensity (0 to 14; 12 is the default for the new kernels). You may specify this option per-GPU. -gt <n> Set the GPU tuning parameter (6 to 400). The default is 15. You can change the tuning parameter interactively with the '+' and '-' keys in the miner's console window. If you don't specify -gt or you specify value 0, the miner will start auto-tuning to determine the best GT value for each GPU Note that when the GPU is dual-mining, it ignores the -gt values, and uses -sci instead. -sci <n> Set the dual mining intensity (1 to 1000). The default is 30. As you increase the value of -sci, the secondary coin hashrate will increase but the price will be higher power consumption and/or lower ethash hashrate. You can change the this parameter interactively with the '+' and '-' keys in the miner console window. You may specify this option per-GPU. If you set -sci to 0, the miner will use auto-tuning to determine the best value, while trying to maximize the ethash hashrate regardless of the secondary coin hashrate. -clKernel <n> Type of OpenCL kernel: 0 - generic, 1 - optimized, 2 - alternative, 3 - turbo (1 is the default) -clGreen <n> Use the power-efficient ("green") kernels (0: no, 1: yes; default: 0). You may specify this option per-GPU. Note that you have to run auto-tune again as the optimal GT values are completely different for the green kernels -clNew <n> Use the new AMD kernels (0: no, 1: yes; default: 1) -clf <n> AMD kernel sync (0: never, 1: periodic; 2: always; default: 1) -nvKernel <n> Type of Nvidia kernel: 0 auto (default), 1 old (v1), 2 newer (v2), 3 latest (v3). Note that v3 kernels are only supported on GTX10x0 GPUs. Also note that dual mining is supported only by v2 kernels. You may specify this option per-GPU. -nvdo <n> Enable Nvidia driver-specific optimizations (0 - no, the default; 1 - yes). Try -nvdo 1 if your are unstable. You may specify this option per-GPU. -nvNew <n> Use new Nvidia kernels if supported (0: no, 1: yes; default: 1) -nvf <n> Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU. -mode <n> Mining mode (0: dual mining if dual pool(s) are specified; 1: ethash only even if dual pools are specified). You may specify this option per-GPU. -list List the detected GPUs devices and exit -gbase <n> Set the index of the first GPU (0 or 1, default: 1) -minRigSpeed <n> Restart the miner if avg 5 min speed is below <n> MH/s -eres <n> Allocate DAG buffers big enough for n epochs ahead (default: 2) to avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability -lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs (0-3, default: 0 - fastest, 3 - slowest). -gser <n> Serializing DAG creation on multiple GPUs (0 - no serializing, all GPUs generate the DAG simultaneously, this is the default; 1 - partial overlap of DAG generation on each GPU; 2 - no overalp (each GPU waits until the previous one has finished generating the DAG); 3-10 - from 1 to 8 seconds delay after each GPU DAG generation before the next one) -gpureset <n> Fully reset GPU when paused (0 - no, 1 - yes; default: no, except on 1080Ti). You may specify this option per-GPU. -altinit Use alternative way to initialize AMD cards to prevent startup crashes -rvram <n> Minimum free VRAM in MB (-1: don't check; default: 384 for Windows, and 128 for Linux) -wdog <n> Enable watchdog timer: 1 - yes, 0 - no (1 is the default). The watchdog timer checks periodically if any of the GPUs freezes and if it does, restarts the miner (see the -rmode command-line parameter for the restart modes) -wdtimeout <n> Watchdog timeout (30 - 300; default 45 seconds). You can use this parameter to increase the default watchdog timeout in case it restarts the miner needlessly -rmode <n> Selects the restart mode when a GPU crashes or freezes: 0: disabled - miner will shut down instead of restarting 1: restart with the same command line options - this is the default 2: reboot (shut down miner and execute reboot.bat) -log <n> Selects the log file mode: 0: disabled - no log file will be written 1: write log file but don't show debug messages on screen (default) 2: write log file and show debug messages on screen -logfile <name> Set the name of the logfile. If you place an asterisk (*) in the logfile name, it will be replaced by the current date/time to create a unique name every time PhoenixMiner is started. If there is no asterisk in the logfile name, the new log entries will be added to end of the same file. If you want to use the same logfile but the contents to be overwritten every time when you start the miner, put a dollar sign ($) character in the logfile name (e.g. -logfile my_log.txt$). -logdir <path> Set a path where the logfile(s) will be created -logsmaxsize <n> Maximum size of the logfiles in MB. The default is 200 MB (use 0 to turn off the limitation). On startup, if the logfiles are larger than the specified limit, the oldest are deleted. If you use a single logfile (by using -logfile), then it is truncated if it is bigger than the limit and a new one is created. -config <name> Load a file with configuration options that will be added to the command-line options. Note that the order is important. For example, if we have a config.txt file that contains -cclock 1000 and we specify command line -cclock 1100 -config config.txt, the options from the config.txt file will take precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100) then the second option takes precedence and the resulting -cclock will be 1100. Note that only one -config option is allowed. Also note that if you reload the config file with 'c' key or with the remote interface, its options will take precedence over whatever you have specified in the command-line. -timeout <n> Restart miner according to -rmode after n minutes -pauseat <hh:mm> Pause the miner at hh::mm (24 hours time). You can specify multiple times: -pauseat 6:00,12:00 -resumeat <hh:mm> Resume the miner at hh::mm (24 hours time). You can specify multiple times: -resumeat 8:00,22:00 -gswin <n> GPU stats time window (5-30 sec; default: 15; use 0 to revert to pre-2.8 way of showing momentary stats) -gsi <n> Speed stats interval (5-30 sec; default: 5; use 0 to disable). The detailed stats are still shown every 45 seconds and aren't affected by the -gsi value -astats <n> Show advanced stats from Web sources (0: no; 1: yes). By default the coin exchange rates are updated every 4 hours, and the coin difficulty is updated every 8 hours. You can increase these periods by specifying for example -astats 12, which will increase update periods to 12 and 24 hours respectively -gpow <n> Lower the GPU usage to n% of maximum (default: 100). If you already use -mi 0 (or other low value) use -li instead -li <n> Another way to lower the GPU usage. Bigger n values mean less GPU utilization; the default is 0. -resetoc Reset the hardware overclocking settings on startup -leaveoc Do not reset overclocking settings when closing the minerHardware control options, use comma to specify different values for each GPU: -tt <n> Set fan control target temperature (special values: 0 - no HW monitoring on ALL cards, 1-4 - only monitoring on all cards with 30-120 seconds interval, negative - fixed fan speed at n %) -hstats <n> Level of hardware monitoring: 0 - temperature and fan speed only; 1 - temperature, fan speed, and power; 2 - full (include core/memory clocks, voltages, P-states). The default is 1. -pidle <n> Idle power consumption of the rig in W. Will be added to the GPU power consumption when calculating the total power consumption of the rig. -ppf <n> The power usage of each GPU will be multiplied by this value to get the actual usage. This value is in percent, so for example if the GPU reports 100 W power usage and you have specified -ppf 106 the GPU power usage will be calculated to be 100 * (106 / 100) = 106 W. This allows you to correct for the efficiency of the PSUs and the individual GPUs. You can also specify this value for each GPU separately. -prate <n> Price of the electricity in USD per kWh (e.g. -prate 0.1). If specified the miner will calculate the rig daily electricity cost -fanmin <n> Set fan control min speed in % (-1 for default) -fanmax <n> Set fan control max speed in % (-1 for default) -fcm <n> Set fan control mode (0 - auto, 1 - use VBIOS fan control, 2 - forced fan control; default: 0) -tmax <n> Set fan control max temperature (0 for default) -powlim <n> Set GPU power limit in % (from -75 to 75, 0 for default) -cclock <n> Set GPU core clock in MHz (0 for default). For Nvidia cards use relative values (e.g. -300 or +400) -cvddc <n> Set GPU core voltage in mV (0 for default). For Nvidia cards use relative values (e.g. -300 or +400) -mclock <n> Set GPU memory clock in MHz (0 for default) -mvddc <n> Set GPU memory voltage in mV (0 for default) -tstop <n> Pause a GPU when temp is >= n deg C (0 for default; i.e. off) -tstart <n> Resume a GPU when temp is <= n deg C (0 for default; i.e. off) -mt <n> VRAM timings (AMD under Windows only): 0 - default VBIOS values; 1 - faster timings; 2 - fastest timings. The default is 0. This is useful for mining with AMD cards without modding the VBIOS. If you have modded BIOS, it is probably faster than even -mt 2General Options: -v,--version Show the version and exit -vs Show short version string (e.g. "4.1c") and exit -h,--help Show information about the command-line options and exitPer-GPU optionsSome of the PhoenixMiner options can provide either the same setting for all GPUs, or a differentsetting for each of the GPUs. For example, to specify the -gt value for all cards you would write-gt 90 but if you want to specify a different GT value for each of the cards, use something like this:-gt 20,15,40,90,90 for a five-GPU mining rig. This would set GT to 20 for the first GPU, 15 for the secondGPU, and so on. If you specify less values than you have GPUs, the rest of the GPUs will use the defaultvalue for the parameter.You can also use another, more flexible way of specifying different values for the different cards.This is best explained by example: -cclock *:1100,1-3:1090,4:1300 - here we are setting core clockto 1100 MHz for all cards, except the cards 1 to 3, on which it is set to 1090 MHz, and card 4 to 1300 MHz.The part before the colon (:) is the selector, which selects the GPUs for which the value after the colon is applied. The selector can be: - single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU - range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5 - asterisk, which sets the value for all GPUs - label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards - arbitrary string that starts with letter and can contain letters, numbers and asterisks, which is matched with the GPU name as listed by PhoenixMiner. Example: gtx*1070:+500 will set value +500 for all cards which contain 'gtx' and '1070' in their names with anything between them. This will match 'Nvidia GeForce GTX 1070' but not 'Nvidia GeForce 1070'. Note that if more than one selector matches given card, than only the last one counts.Example: -cclock *:1100,1-4:1090,2:1300 will set card 2 to 1300; cards 1,2, and 4 to 1090;and the rest of the cards to 1100 MHz core clock. Additionally, while the miner is running, you can use the following interactive commandsin the console window by pressing one of these keys: s Print detailed statistics 1-9 Pause/resume GPU1 ... GPU9 (if you have more than 9 GPUs, type 010 for card 10, 011 for card 11, etc.) p Pause/resume the whole miner +,- Increase/decrease GPU tuning parameter g Reset the GPU tuning parameter (and stop auto-tuning if active) x Select the GPU(s) for manual or automatic GT tuning z Start AMD auto-tune process r Reload epools.txt and switch to primary ethash pool e Select the current ethash pool (if you have more than 9 pools in the list, type 010 for pool 10, 011 for pool 11, etc.) d Select the current dual-mining pool y Turn on AMD Compute mode if it is off on some of the GPUs c Reload the config.txt file (some settings require restart, see -cdmrs option above for details) h Print this short help 4. Configuration filesNote that PhoenixMiner supports the same configuration files as Claymore's dual Ethereum minerso you can use your existing configuration files without any changes.Instead of using command-line options, you can also control PhoenixMiner with configurationfiles. If you run PhoenixMiner.exe without any options, it will search for the file config.txtin the current directory and will read its command-line options from it. If you want, you canuse file with another name by specifying its name as the only command-line optionwhen running PhoenixMiner.exe.You will find an example config.txt file in the PhoenixMiner's directory.Instead of specifying the pool(s) directly on the command line, you can use another configurationfile for this, named epools.txt. There you can specify one pool per line (you will find an exampleepools.txt file in the PhoenixMiner's directory).For the dual mining pools, you can use the dpools.txt file, which has the same format as epools.txtbut for the secondary coin. You will find an example epools.txt file in the PhoenixMiner's directory.Note that unlike the epools.txt, which is loaded each time when the miner starts, the dpools.txt fileis only read if you specify a dual mining pool on the command line with -dpool, or at least addthe -dcoin blake2s command-line option.The advantages of using config.txt and epools.txt/dpools.txt files are:- If you have multiple rigs, you can copy and paste all settings with these files- If you control your rigs via remote control, you can change pools and even the miner options byuploading new epools.txt files to the miner, or by uploading new config.txt file and restartingthe miner.5. Remote monitoring and managementPhoenix miner is fully compatible with Claymore's dual miner protocol for remote monitoring andmanagement. This means that you can use any tools that are build to support Claymore's dual miner,including the "Remote manager" application that is part of Claymore's dual miner package.We are working on much more powerful and secure remote monitoring and control functionality andcontrol center application, which will allow better control over your remote or local rigs and someunique features to increase your mining profits.6. Hardware control options Here are some important notes about the hardware control options: Hardware control options are supported for both AMD and Nvidia cards under Windows. Under Linux most options are supported only for AMD cards. If you specify a single value (e.g. -cvddc 1150), it will be used on all cards. Specify different values for each card like this (separate with comma): -cvddc 1100,1100,1150,1120,1090 If the specified values are less than the number of GPUs, the rest of GPUs will use the default values. We have tested only on relatively recent AMD GPUs (RX460/470/480/560/570/580, Vega, Radeon VII, RX5700). Your results may vary with older GPUs. The blockchain beta drivers from AMD show quite unstable results - often the voltages don't stick at all or revert back to the default after some time. For best results use the newer drivers from AMD: 18.5.1 or later, where most of the bugs are fixed. -tmax specifies the temperature at which the GPU should start to throttle (because the fans can't keep up). If you use other programs for hardware control, conflicts are possible and quite likely. Use something like GPU-Z to monitor the voltages, etc. MSI Afterburner also seems to behave OK (so you can use it to control the Nvidia cards while AMD cards are controller by PhoenixMiner). This should be obvious but still: if given clocks/voltages are causing crashes/freezes/incorrect shares when set with third-party program, they will be just as much unstable when set via PhoenixMiner hardware control options. If you have problems with hardware control options of PhoenixMiner and you were using something else to control clocks, fans, and voltages (MSI Aftrerburner, OverdriveNTool, etc.), which you were happy with, it is probably best to keep using it and ignore the hardware control options of PhoenixMiner (or use only some of them and continue tweaking the rest with your third-party tools).
