Important message for everyone that is running older versions of PhoenixMiner (before 4.2):
Changes in version 4.2c (since 4.1c):
- Added support for dual mining Ethash and Blake2s on Nvidia GPUs
- Added new Nvidia kernels v3 with slightly higher hashrate and lower power consumption (up to about 1-1.5% less power). The new kernels are supported only on GTX1050/1060/1070/1080/Ti GPUs and are enabled by default on these GPUs. Note that you can’t use these kernels for dual-mining, only -nvkernel 2 works for dual mining on Nvidia.
- Added new command-line option -nvkernel to select the old (v1 CUDA kernels from PhoenixMiner 3.5), newer (v2 introduced with PhoenixMiner 4.0), or the latest CUDA kernels (v3). The possible values are 0 (auto; the default, selects the best kernel for each GPU), 1 , 2, or 3 (forces v1, v2, or v3 kernels respectively). Note that only v2 CUDA kernels support dual mining.
- Added experimental support for ProgPOW mining of Bitcoin Interest (BCI) . Note that the kernels are not optimized and only work on AMD. You must add -coin bci to the command line (or COIN: bci to your epools.txt file) in order to mine BCI.
- Added parameter to enable or disable driver-specific optimizations on Nvidia GPUs. Use -nvdo 1 (the default is 0) to enable the optimizations. This won’t change hashrate (or will change it only slightly) but can make the cards more stable depending on the concrete Nvidia driver.
- Added support for EthereumStratum/2.0.0 protocol (use -proto 5 if the pool requires it).
- AMD hardware control code was rewritten, now should be more stable and work on older cards too
- Added command-line option -fcm to set the way fans are controlled (AMD/Windows only). The possible values are 0 (auto; the default behavior), 1 (use VBIOS/driver), 2 (force custom control of the fans regardless of VBIOS/drivers fan curves, etc). Use -fcm 2 if the fans are not controlled properly or at all
- Added support for Radeon VII
- Added support for Windows AMD drivers 19.3.3
- Increased the maximum supported DAG epoch to 329. This should be fine for at least a year or so.
- Added support for direct mining without DAG switching of Yocoin (YOC) , Bitcoiin2Gen (B2G) , Ethersocial (ESN) , Atheios (ATH) , and REOSC . See the -coin parameter in Readme.txt for more information.
- Fixed the slower DAG generation on Vega and Radeon VII GPUs
- Fixed the problem with the watchdog timer when solo mining
- Other small improvements and fixes.
PhoenixMiner is fast (arguably the fastest) Ethash (ETH, ETC, Muiscoin, EXP, UBQ, etc.) miner that supports
both AMD and Nvidia cards (including in mixed mining rigs). It runs under Windows x64 and Linux x64
and has a developer fee of 0.65% (the lowest in the industry). This means that every 90
minutes the miner will mine for us, its developers, for 35 seconds.
PhoenixMiner also supports Ubqhash for mining UBQ, ProgPOW for mining BCI , and dual mining
Ethash/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 or
higher depending on the GPUs). To achieve highest possible speed on AMD cards it may be needed
to manually adjust the GPU tune factor (a number from 8 to about 400, which can be changed
interactively with the + and - keys while the miner is running).
If you have used Claymore’s Dual Ethereum miner, you can switch to PhoenixMiner with
minimal hassle as we support most of Claymore’s command-line options and confirguration
1. Quick start
You can download PhoenixMiner 4.2c from here:
(MEGA) - /mega.nz/#F!TQcCnADA!rEvfBgr0BSsqcVlnpFYtGQ
Examples of settings for different pools.
ethermine org (ETH):
PhoenixMiner.exe -pool eu1 ethermine org:4444 -pool2 us1 ethermine org:4444 -wal YourEthWalletAddress.WorkerName -proto 3
ethermine org (ETH, secure connection):
PhoenixMiner.exe -pool ssl: //eu1 ethermine org: 5555 -pool2 ssl: //us1 ethermine org: 5555 -wal YourEthWalletAddress.WorkerName -proto 3
ethpool 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 x
nanopool org (ETH):
PhoenixMiner.exe -pool eu1 nanopool org:9999 -wal YourEthWalletAddress / WorkerName -pass x
PhoenixMiner.exe -pool stratum + tcp: //daggerhashimoto eu nicehash com: 3353 -wal YourBtcWalletAddress -pass x -proto 4 -stales 0
PhoenixMiner.exe -epool eth f2pool com:8008 -ewal YourEthWalletAddress -pass x -worker WorkerName
PhoenixMiner.exe -pool us-east ethash-hub miningpoolhub com:20535 -wal YourLoginName.WorkerName -pass x -proto 1
coinotron com (ETH):
PhoenixMiner.exe -pool coinotron com:3344 -wal YourLoginName.WorkerName -pass x -proto 1
ethermine org (ETC):
PhoenixMiner.exe -pool eu1-etc ethermine org:4444 -wal YourEtcWalletAddress.WorkerName
dwarfpool com (EXP):
PhoenixMiner.exe -pool exp-eu dwarfpool com:8018 -wal YourExpWalletAddress / WorkerName
PhoenixMiner.exe -pool europe ethash-hub miningpoolhub com:20585 -wal YourLoginName.WorkerName -pass x -proto 1
PhoenixMiner.exe -pool stratum + tcp: //eu ubiqpool io: 8008 -wal YourUbiqWalletAddress -pass x -worker WorkerName
minerpool net (PIRL):
PhoenixMiner.exe -pool pirl minerpool net:8002 -wal YourPirlWalletAddress -pass x -worker WorkerName
dodopool com (Metaverse ETP):
PhoenixMiner.exe -pool etp dodopool com:8008 -wal YourMetaverseETPWalletAddress -worker Rig1 -pass
minerpool net (Ellaism):
PhoenixMiner.exe -pool ella minerpool net:8002 -wal YourEllaismWalletAddress -worker Rig1 -pass x
3. Command-line arguments
Note that PhoenixMiner supports most of the command-line options of Claymore’s dual Ethereum miner
so you can use the same command line options as the ones you would have used with Claymore’s miner.
-pool <hostort> 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)
-coin <coin> Ethash coin to use for devfee to avoid switching DAGs:
auto: Try to determine from the pool address (default)
etc: Ethereum Classic
etp: Metaverse ETP
hbc: Hotelbyte Coin
4. Configuration files
Note that PhoenixMiner supports the same configuration files as Claymore’s dual Ethereum miner
so you can use your existing configuration files without any changes.
Instead of using command-line options, you can also control PhoenixMiner with configuration
files. If you run PhoenixMiner.exe without any options, it will search for the file config.txt
in the current directory and will read its command-line options from it. If you want, you can
use file with another name by specifying its name as the only command-line option
when 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 configuration
file for this, named epools.txt. There you can specify one pool per line (you will find an example
epools.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.txt
but 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 file
is only read if you specify a dual mining pool on the command line with -dpool, or at least add
the -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 by
uploading new epools.txt files to the miner, or by uploading new config.txt file and restarting
5. Remote monitoring and management
Phoenix miner is fully compatible with Claymore’s dual miner protocol for remote monitoring and
management. 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 and
control center application, which will allow better control over your remote or local rigs and some
unique features to increase your mining profits.