Configuration files

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.

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.

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 dpools.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 if you add the -dcoin blake2s command-line option.

You can combine the config.txt file with some options that are specified directly on the command-line by using the -config <name> command-line option. It will instruct the miner to load a file with configuration options that will be added to the options read from the command-line.

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 the miner.