nanominer by nanopool

version: 3.10

Driver requirements
Reporting bugs and technical support
Setup
Log Files
Remote Monitoring
Automatic Restart Function
Parameters
Configuration File
Launching from command line
Examples of Configuration Files

nanominer is a program product developed by nanopool to create structural cryptocurrency units based on the following algorithms:

| Algo | Coin | Dev Fee (once per 2 hours) | AMD | Nvidia | Intel Arc | CPU | |:-------------:|:-------------:|:---------------------------:|:-----------:|:-----------:|:-----------:|:-------:| | Ethash | ETH & other | 1% | ✓ | ✓ | ✓ | | | Etchash | ETC | 1% | ✓ | ✓ | ✓ | | | EthashB3 | RTH | 1% | ✓ | ✓ | | | | FishHash | IRON | 1% | ✓ | ✓ | | | | Karlsenhashv2| KLS | 1% | ✓ | ✓ | | | | Ubqhash | UBQ | 1% | ✓ | ✓ | ✓ | | | FiroPow | FIRO | 1% | ✓ | ✓ | | | | KawPow | RVN | 2% | ✓ | ✓ | | | | Octopus | CFX | 2% | | ✓ | | | | Autolykos | ERG | 2.5% | ✓ | ✓ | | | | RandomX | XMR, ZEPH, ...| 2% | | | | ✓ | | RandomNevo | NEVO | 2% | | | | ✓ | | Verushash | VRSC | 2% | | | | ✓ | | Verthash | VTC | 1% | ✓ | | | |

nanominer also supports Zilliqa mining in the current configurations (see config examples):

| Configuration | Merged (same pool) | Split (different pools)†| |:-------------:|:-------------------:|:-----------------------:| | ETC+ZIL | ✓ | ✓ | | KLS+ZIL | | ✓ | | CFX+ZIL | | ✓ | | ERG+ZIL | | ✓ | | RVN+ZIL | | ✓ | | FIRO+ZIL | | ✓ | When mining Zilliqa on a different pool, nanominer will use a placeholder 0xffffffffffffffffffffffffffffffffffffffff ETH/ETC address to authorize on Zilliqa pool. † Intel Arc does not support split Zilliqa mining at this moment (under construction).

nanominer also supports trial mining: {ETC,CFX,RVN,KLS,FIRO,ERG,...}+ZIL+{CPU coin}

Driver requirements

In order to work with Nvidia GPUs nanominer needs Nvidia driver 410.48 and newer on Linux or 411.31 and newer on Windows.

In order to begin mining Ethereum Classic with nanominer, it's enough to simply input your wallet in the configuration file.

Testing on nanominer demonstrated high performance working with Ethereum Classic, EthereumPOW, Ravencoin, Conflux, QuarkChain, Ubiq, Monero, Ergo, Firo and other currencies. Ethash, Etchash and KawPow implementations have some know-how optimizations for DAG size in memory which is critical for 3 GB and 4 GB GPUs. Independently of this, nanominer stands out with its high stability and simple setup.

Reporting bugs and technical support

For reporting bugs, technical support, feature requests and community discussions feel free to use the following communication channels:

Support email: support@nanominer.org
GitHub issues tracker: https://github.com/nanopool/nanominer/issues
Community chat in telegram (developers read it too): https://t.me/nanominer_en
Our Discord channel https://discord.gg/JtKHCbm8Yg

Setup

At launch nanominer reads the config.ini setup file from the program's current directory. In order to assign a specific name to the config file, it should be written as the first argument in the command line. For example:

nanominer.exe config_etc.ini

When launching with the -d command line option (e.g. nanominer.exe -d) the miner displays a list of the devices it detects, including their PCI addresses and their amount of memory. In order to use this function on Windows the program must be launched from the command prompt (cmd).

nanominer does not require any pools to be specified in the config file. If a pool (or list of pools) is not specified, nanominer will automatically use the pools on nanopool.org corresponding to the chosen cryptocurrency (except for coins not listed on Nanopool). QuarkChain public full nodes (fullnode.quarkchain.io and fullnode2.quarkchain.io) which are maintained by QuarkChain developers are used by default for QuarkChain.

When nanominer starts up it displays the main work information in the console log, including the program’s current version, the name of the rig, the number and type of graphics cards installed and the program’s current settings.

Log Files

The event log function on nanominer is automatically activated each time the program starts up. The log files that are created contain all the information displayed on the console while the miner is running. By default, the log files are saved in the logs folder of the program's current directory. Deactivating event logging, as well as assigning a random catalogue for recording log files, can be done by using the corresponding configuration parameters (see the examples in the Parameters section of this file).

Remote Monitoring

nanominer has web interface for getting rig statistics, discovering other instances of nanominer in the local network and managing them. You can edit miners' config via web as well as restart the miners. In order to perform these actions on a running instance of nanominer, its config must contain a password for web interface (see the webPassword option). By default nanominer starts a HTTP server on port 9090, which can be found on http://127.0.0.1:9090. In the program's config file, the port can be configured and the API function can be deactived with the webPort option (or it can be set to 0 to disable web interface). BoringAPI for getting rig statistics is supported aswell, which can be found on http://127.0.0.1:9090/stats.

nanominer also supports the network API program EthMan for rig monitoring. By default it opens port 3333 in “read-only” mode without the ability to restart the miner or rig through the network. In the program's config file, the port can be configured and the API function can be deactived with the mport function. The config file also lets you set a password for monitoring with the ethmanPassword option.

Automatic Restart Function

With default settings, nanominer will automatically restart if it encounters critical errors in the GPU or lag. (These errors usually arise due to hardware problems or overclocking the GPU.) The automatic restart function can be deactivated using the watchdog parameter.

Likewise, the minHashrate (minimum hashrate) parameter allows the user to set the value of the minimum hashrate which, if exceeded, will cause the miner to restart. This function uses the average hashrate over the last ten minutes, as displayed in blue in the console log. If the average hashrate over 10 minutes is lower than the set value, the miner will restart. With default settings the minimum hashrate is not set.

Another function on nanominer that improves the miner's automatic functioning is handled by the restarts parameter.It sets the number of times the miner restarts before rebooting the worker (rig). By default the miner will only restart itself.

More detailed information on using these functions can be found in the Parameters section of this file.

Parameters

The settings for nanominer can be found in the configuration file with the *.ini extension (config.ini by default). Config file can contain common params and algorithm params (in sections with corresponding algorithm names). Section names can be defined as “Ethash”, “Etchash”, “KawPow”, “Octopus”, “Ubqhash”, “RandomX”, “Verushash”, “Autolykos” or “Zilliqa”. Configuration file must be in the following format:

commonparameter1=commonvalue1
commonparameter2=commonvalue2
commonparameterX=commonvalueX

[AlgoName1]
devices=0,1
wallet = wallet1
algoparameter1=algovalue1_1
algoparameter2=algovalue1_2
algoparameterY=algovalue1_Y

[AlgoName2]
devices=2,3
wallet = wallet2
algoparameter1=algovalue2_1
algoparameter2=algovalue2_2
algoparameterZ=algovalue2_Z

[AlgoName3]
devices=4,5
wallet = wallet3

More config examples can be found below.

This file permits the presence of empty lines and comments. Comment lines should begin with a ";" (semicolon). The parameters and values are not case-sensitive, which means it makes no difference to the program whether you type ETH, eth or Eth, or whether you type wallet or Wallet. If an incorrect value is set for a parameter, the default value will be

Nanominer

Install / Use

README