IMPORTANT! The latest Nvidia drivers for Windows 10 460.79 and 460.89 cause crash when PhoenixMiner starts. If you want to use these drivers, you need to upgrade to PhoenixMiner 5.4c or later version.
IMPORTANT! Ethereum Classic (ETC) network switched to a modified version of ethash, called ETCHash. If you are mining ETC you must upgrade to PhoenixMiner 5.3b or later, otherwise you will get only rejected shares when mining ETC.
The current ETC DAG is 195 instead of 390, with corresponding “shrinking” of the DAG buffer to about 2.5 GB. With this DAG size you will be able to mine with 3GB and 4GB cards without problems. After that, each DAG epoch on the ETC network will be twice as long, so the DAG size will grow with half the speed as before. As a result, it will be possible to mine ETC with 4GB cards for about 4 more years.
The switch went without problems, all our test rigs switched to the new DAG and are mining normally. You may need to run auto-tuning again if to get an optimal speed with the new DAG size.
IMPORTANT! All owners of AMD cards with 6 GB or 8 GB RAM must either keep drivers 20.4.x or lower (do not upgrade to 20.5.1 or later), or upgrade to PhoenixMiner 5.2e or later version to continue mining after DAG epoch 384 (ETH will pass it before the end of 2020).
IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.2e or later version to continue mining after DAG epoch 373. Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.2e and later:
Changes in version 5.4c (since 5.3b):
Added support for DAG epochs up to 500
New kernels for AMD Vega and Navi GPUs that are slightly faster when the DAG buffer is approaching or passing 4GB in size (the current ETH DAG is close to 4GB). To use these new kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
Fixed crash (or GPUs not detected error) when using the latest Windows Nvidia drivers 460.79 and 460.89
Validated support for Nvidia RTX 3090, 3080, 3070, and 3060Ti GPUs. Those still use the current kernels and there are no speed increases fom the previous PhoenixMiner release
Automatic re-running auto-tune as needed when switching to a different DAG buffer type (e.g. when switching from ETH to ETC, or back)
Fixed crash when trying to set -mvddc on very old AMD drivers (including the beta blockchain drivers from 2017)
Added support for the latest AMD Windows 10 drivers 20.12.1 and 20.11.3
Add support for the older AMD Linux driver 19.50-1011208-ubuntu-18.04 (used by some Linux mining OSes and other software)
Added new kernels to allow mining on AMD Hawaii cards (R9 390, etc.) with the current and future DAG epochs (even with DAG buffer above 4GB for the 8GB cards). Note that the AMD Windows drivers do not support compute mode for Hawaii cards, so the hashrate will be quite low (14-15 MH/s with the current ETH DAG epoch). This problem is fixed under Linux, where you can get the full 29-30 MH/s speed out of the Hawaii cards.
Other small fixes and improvements
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 ETCHash for mining ETC, 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
Please 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.
1. Quick start
You can download PhoenixMiner 5.4c: from here:
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 Ethash pool address (prepend the host name with ssl:// for SSL pool, or http:// for solo mining)
-wal Ethash wallet (some pools require appending of user name and/or worker)
-pass Ethash password (most pools don’t require it, use ‘x’ as password if unsure)
-worker Ethash worker name (most pools accept it as part of wallet)
-proto 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 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.