Nanominer

Nanominer is a specialized cryptocurrency mining software designed for smooth operation with both AMD and Nvidia graphics processors, as well as central processors. It supports various algorithms such as Ethash, Etchash, KawPow, Octopus, Ubqhash, Autolykos, RandomX, and Verushash, receiving regular updates for optimal performance.

The development of Nanominer focused on seamless integration with the Nanopool mining pool, a collaboration we plan to engage in. These instructions are tailored for setting up mining operations targeting Ethereum Classic (ETC), Ethereum (ETH), and Ergo, using a mining farm equipped with either AMD or Nvidia components.

For newcomers to mining, it’s essential to understand that a mining pool involves miners collaborating to distribute rewards based on their contributions. Opting for a mining pool is more advantageous for those without a substantial mining setup compared to solo mining endeavors.

System requirements:

• Mining farm based on Windows 10 with Nvdia/AMD video cards, each of which has more than 4 GB of video memory.
• Wallet address to deposit your mined coins.

LHR unlock

Nanominer supports full LHR unlock for Nvidia LHR v1 and v2 graphics processors. It is recommended to use drivers 512.77 for Windows and 510.60.02 for Linux. Currently, full LHR unlock is not supported on versions 512.95 and 515.x.

The LHR parameter is optional for Ethash and Etchash algorithms. It can be used to set the desired percentage of the full unlocked hash rate within the range of 50 to 100. Additionally, values of “off” (-1) or “auto” (0) are possible. Use “off” for non-LHR cards and “auto” for automatic detection and configuration of LHR cards. The default value is “auto”. This parameter can be set for each GPU separately, and the order should correspond to the GPU order specified in the “devices” parameter. For example:

devices=0,2,3
lhr=71.5,off,0
means 71.5% for GPU0, off for GPU2 and auto for GPU3.

These settings mean 71.5% unlock for GPU0, LHR off for GPU2 and automatic for GPU3.

Launching the program and hashrate

• Added pool: ergo-eu2.nanopool.org:11111 – we added a mining pool.
• Using all GPU devices – all available GPUs are being utilized.
• Log path: ./logs/ – path to the miner’s event log files.
• GPU watchdog is enabled – the default watchdog timer is enabled.
• Never calling reboot.bat (always restarting the miner in case of errors) – the miner will be restarted at the beginning, not the system. To reboot the system, the miner loads the reboot.bat script from the current directory if running on Windows, or reboot.sh if on Linux.
• Setting up algorithm: Autolykos – the Autolykos hashing algorithm is being used.
• Connected to pool: ergo-eu2.nanopool.org:11111 – we are connecting to the pool.
• New job from ergo-eu2.nanopool.org:11111 – we have received new tasks for GPU calculations from the pool.
• Ergo - Total speed: 61.109 MH/s, Total shares: 0 Rejected: 0, Time: 01:07 – here we see the total hashing speed.
• GPU0 t=61°C fan 51% power 150.36W. Total power: 150.36W – temperature, fan speed, power consumption, and total power consumption.
• Ergo - Total speed: 61.109 MH/s, Total shares: 1 Rejected: 0, Time: 01:36 – hashing speed again.
• Ergo - SHARE FOUND (GPU: 0, nonce: 0xa49187fa3e737cc4) – finally, we found a share (solution). This is what earns rewards in mining.

Here is the launch code listing:

Email was not set.
Hashrate threshold to restart miner is not set
Number of rejected shares per hour to restart miner is not set

Auto pool sorting is disabled
Using all GPU devices
	— Common parameters:	
Log path: ./logs/
Log is written to file 
GPU watchdog is enabled
Never calling reboot.bat (always restarting the miner in case of errors).
2021-Aug-26 17:51:19: Setting up algorithm: Autolykos 
2021-Aug-26 17:51:20: Connecting to pools...
2021-Aug-26 17:51:20: Connected to pool: ergo-eu2.nanopool.org:11111 | IP: 213.32.74.157 
2021-Aug-26 17:51:21: New job from ergo-eu2.nanopool.org:11111 | share difficulty = 10 GH Ergo - Total speed: 0.000 H/s, Total shares: 0 Rejected: 0, Time: 00:01
GPU0 t=50°C fan 0% power 56.99W. Total power: 56.99W
2021-Aug-26 17:51:22: GPU0: 2048 MB data generated in 1.64 seconds
2021-Aug-26 17:51:54: New job from ergo-eu2.nanopool.org:11111
Ergo - Total speed: 0.000 H/s, Total shares: 0 Rejected: 0, Time: 00:35
Ergo last 10 min - Total: 0.000 H/s.
Ergo - Total speed: 61.109 MH/s, Total shares: 0 Rejected: 0, Time: 01:07
GPU0 t=61°C fan 51% power 150.36W. Total power: 150.36W
2021-Aug-26 17:52:44: Ergo - SHARE FOUND (GPU: 0, nonce: 0xa4913398afae4d93).
Ergo: share accepted (58 ms)!
2021-Aug-26 17:52:55: New job from ergo-eu2.nanopool.org:11111
Ergo - Total speed: 61.109 MH/s, Total shares: 1 Rejected: 0, Time: 01:36
2021-Aug-26 17:53:08: Ergo - SHARE FOUND (GPU: 0, nonce: 0xa49187fa3e737cc4).
Ergo: share accepted (58 ms)!

Launch via config

To run through the configuration file – config.ini we need two files:

• Config.bat – here we specify the path to the configuration file (.ini).
• Config.ini – this is where the configuration settings themselves will be.

To run, you need to enter two commands into each file. Let’s start from the first – Config.bat:

• nanominer.exe – specifying which program will be launched.
• config_eth.ini – specifying the path to the required configuration (you can specify a different configuration file).

The miner now reads the config_eth.ini file. Let’s move on to it.

• 0x3aa3e06C47caDEf96202D378aB7C407CF46A36A4 – replace the wallet with your own.
• speed_test – specify the rig name (worker).

File code Config.bat:

nanominer.exe config_eth.ini
pause

File code config_eth.ini:

; Address to send funds to. Change this address to yours!
wallet = 0x3aa3e06C47caDEf96202D378aB7C407CF46A36A4

; (Optional) Rig (worker) name.
rigName = speed_test

Dual mining

The program also supports dual mining.

Examples:

Ergo+Zil

[autolykos]
wallet = 9hEq42Jrr21uHJehvUNZ7uuo9429EEKb6WPSG9y7SargP3wF9rp
; nanopool pools by default

[zil]
wallet = zil10y5vnfapk7f35a9q3ld6zl7ytfhexv0jryzfzw
zilEpoch = 0 ; number of DAG epoch for caching
pool1 = eu.ezil.me:5555
pool2 = us-east.ezil.me:5555
pool3 = us-west.ezil.me:5555
pool4 = asia.ezil.me:5555

We’ll start with the wallet for Ergo, followed by the wallet and pools for Zilliqa.

Ravencoin (2miners) + Zilliqa (ezil.me)

[KawPow]
coin = RVN
wallet = RKAeArXkWLNERjWo5YF3R1xFnYCwKf11sX
pool1 = rvn.2miners.com:6060
[zil]
wallet = zil10y5vnfapk7f35a9q3ld6zl7ytfhexv0jryzfzw
zilEpoch = 0 ; number of DAG epoch for caching
pool1 = eu.ezil.me:5555

Ethereum и Monero

[Ethash]
wallet = 0x3aa3e06C47caDEf96202D378aB7C407CF46A36A4
rigName = rig1
email = your_mail@org
pool1 = eth-eu1.nanopool.org:9433
pool2 = eth-eu2.nanopool.org:9433
pool3 = eth-us-east1.nanopool.org:9433
pool4 = eth-us-west1.nanopool.org:9433
pool5 = eth-asia1.nanopool.org:9433
pool6 = eth-jp1.nanopool.org:9433
pool7 = eth-au1.nanopool.org:9433
[RandomX]
wallet = 89ivqChdkg6D3QvnRFLY6CYzzXzgY3ePaSZZv8iZoXinHKtjoRu2vzijWfgvN17DNshc2N9bDdVvE7UJpqzqYbe8EHZLsqQ
rigName = rig1
email = your_mail@org
pool1 = xmr-eu1.nanopool.org:14433
pool2 = xmr-eu2.nanopool.org:14433
pool3 = xmr-us-east1.nanopool.org:14433
pool4 = xmr-us-west1.nanopool.org:14433
pool5 = xmr-asia1.nanopool.org:14433

We have discussed the basic parameters that will enable you to start mining. It is recommended to perform the initial launch with minimal or even no GPU overclocking settings to assess the stability of Nanominer. While the program is being tested, you can proceed to configure more advanced settings and utilize various commands.

Commands and Command Line Arguments

Now let’s look at the settings and capabilities of the program in more detail.

MemTweak – performance and intensity settings

MemTweak is an optional parameter. It allows you to dynamically adjust AMD timings for Ethash/Etchash/Ubqhash algorithms. Currently, the following architectures are supported: gfx900, gfx901, gfx906, gfx907, Baffin, Ellesmere, gfx804, Hawaii, Tahiti, Pitcairn, Tonga.

The miner must be launched with administrator privileges (root in Linux) to modify timings.

Available values:

• The default memory setting value is 1, indicating a slight improvement in memory timings.
• A value of zero means that timings are left unchanged.
• Values from 3 up to 10.

Parameter values should be separated by a comma or space (the first value is for GPU0, the second for GPU1, and so on). The supported range for memory tuning values is from 0 to 10 (where 0 means disabling memory timing changes, 1 is the least intensive, and 10 is the most intensive), for example:

memTweak=9,8,10

It is recommended to start with lower values and gradually increase them if the miner operates stably.

You can also apply the same settings to each graphics processor by specifying only one memory tuning value:

memTweak=10

• minHashrate – set the minimum acceptable hash rate. This function monitors the overall hash rate of the mining rig by comparing it to the set value. If, within five minutes of the miner’s launch, the hash rate does not reach the specified minimum, the nanominer will automatically restart. Similarly, the miner will restart automatically if, at any point within a ten-minute period, the average hash rate falls below the defined level. The value of this parameter can be set using an optional letter modifier, representing thousands for kilohashes or millions for megahashes per second. For example, setting a value of 100 megahashes per second can be expressed as 100M, 100.0M, 100m, 100000k, 100000K, or 100000000. If this parameter is not defined, the miner will not be restarted, except in situations described in the “watchdog” section. Restarts triggered by this option are recorded in the restart counter.
• maxRejectedShares – is employed to establish the maximum number of rejected shares before triggering a miner process restart or a farm reboot. Restarts initiated by this option are taken into account in the restart counter. By default, this option is disabled.

Reboot – reboot settings

Under default settings, nanominer will automatically restart upon detecting critical errors in the graphics processor or delays. These errors typically arise from hardware issues or GPU overclocking. The option for automatic restart can be disabled using the watchdog parameter.

Similarly, the minHashrate parameter allows the user to set a minimum hash rate value, exceeding which will trigger a miner restart. This function utilizes the average hash rate over the last ten minutes, displayed in blue in the console log. If the average hash rate over 10 minutes falls below the set value, the miner will restart. The minimum hash rate value is not set by default.

Another feature that enhances the automatic functioning of the miner is managed by the restarts parameter, which specifies the number of miner restarts before reloading the worker (rig). By default, the miner only restarts itself without initiating a system reboot.

reboot – is an optional parameter that determines the number of miner restarts before initiating a full farm reboot. In situations related to the graphics processor, such as hardware errors, delays, or a decrease in hash rate (if the minhashrate parameter is activated), nanominer will perform an automatic restart. However, some errors cannot be resolved by simply restarting the program. In such cases, a rig reboot is required. To execute the reboot, the miner loads the reboot.bat script from the current directory when operating in the Windows operating system.

Example content of a typical reboot.bat script for Windows:

shutdown /r /t 5 /f

Auto update – enable/disable

• autoUpdate is an optional parameter. This option takes values of true or false (default is false). If this parameter is set to true and update checking is enabled, nanominer will automatically update itself upon each launch if a newer version is available.
• checkForUpdates is an optional parameter. It checks for the existence of updates. This option takes values of true or false (default is true). If this parameter is set to false, nanominer will stop checking for the latest version of the program with each launch.

History of creation

3.3.8

• Fixed the KawPow algorithm for some users under HiveOS.
• Corrected issues with incorrect shares for certain XMR tasks due to an incorrect length of a large binary object.

3.3.3

• Added zombie mode for Ergo on 2GB GPUs from both Nvidia and AMD.