├── README.md └── Terms of Use Nanominer.pdf /README.md: -------------------------------------------------------------------------------- 1 | # nanominer by nanopool 2 | # version: 3.10 3 | # Table of Contents 4 | 1. [Driver requirements](#driver-requirements) 5 | 1. [Reporting bugs and technical support](#reporting-bugs-and-technical-support) 6 | 1. [Setup](#setup) 7 | 1. [Log Files](#log-files) 8 | 1. [Remote Monitoring](#remote-monitoring) 9 | 1. [Automatic Restart Function](#automatic-restart-function) 10 | 1. [Parameters](#parameters) 11 | 1. [Configuration File](#configuration-file) 12 | 1. [Launching from command line](#launching-from-command-line) 13 | 1. [Examples of Configuration Files](#examples-of-configuration-files) 14 | 15 | **nanominer** is a program product developed by nanopool to create structural cryptocurrency units based on the following algorithms: 16 | 17 | | Algo | Coin | Dev Fee (once per 2 hours) | AMD | Nvidia | Intel Arc | CPU | 18 | |:-------------:|:-------------:|:---------------------------:|:-----------:|:-----------:|:-----------:|:-------:| 19 | | Ethash | ETH & other | 1% | ✓ | ✓ | ✓ | | 20 | | Etchash | ETC | 1% | ✓ | ✓ | ✓ | | 21 | | EthashB3 | RTH | 1% | ✓ | ✓ | | | 22 | | FishHash | IRON | 1% | ✓ | ✓ | | | 23 | | Karlsenhashv2| KLS | 1% | ✓ | ✓ | | | 24 | | Ubqhash | UBQ | 1% | ✓ | ✓ | ✓ | | 25 | | FiroPow | FIRO | 1% | ✓ | ✓ | | | 26 | | KawPow | RVN | 2% | ✓ | ✓ | | | 27 | | Octopus | CFX | 2% | | ✓ | | | 28 | | Autolykos | ERG | 2.5% | ✓ | ✓ | | | 29 | | RandomX | XMR, ZEPH, ...| 2% | | | | ✓ | 30 | | RandomNevo | NEVO | 2% | | | | ✓ | 31 | | Verushash | VRSC | 2% | | | | ✓ | 32 | | Verthash | VTC | 1% | ✓ | | | | 33 | 34 | 35 | **nanominer** also supports Zilliqa mining in the current configurations (see config examples): 36 | 37 | | Configuration | Merged (same pool) | Split (different pools)†| 38 | |:-------------:|:-------------------:|:-----------------------:| 39 | | ETC+ZIL | ✓ | ✓ | 40 | | KLS+ZIL | | ✓ | 41 | | CFX+ZIL | | ✓ | 42 | | ERG+ZIL | | ✓ | 43 | | RVN+ZIL | | ✓ | 44 | | FIRO+ZIL | | ✓ | 45 | When mining Zilliqa on a different pool, **nanominer** will use a placeholder `0xffffffffffffffffffffffffffffffffffffffff` ETH/ETC address to authorize on Zilliqa pool. 46 | † Intel Arc does not support split Zilliqa mining at this moment (under construction). 47 | 48 | **nanominer** also supports trial mining: 49 | {`ETC`,`CFX`,`RVN`,`KLS`,`FIRO`,`ERG`,`...`}+`ZIL`+{CPU coin} 50 | 51 | 52 | ## Driver requirements 53 | 54 | In order to work with Nvidia GPUs **nanominer** needs Nvidia driver **410.48 and newer on Linux** or **411.31 and newer on Windows**. 55 | 56 | In order to begin mining Ethereum Classic with nanominer, ***it's enough to simply input your wallet*** in the configuration file. 57 | 58 | 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. 59 | 60 | ## Reporting bugs and technical support 61 | For reporting bugs, technical support, feature requests and community discussions feel free to use the following communication channels: 62 | * Support email: support@nanominer.org 63 | * GitHub issues tracker: https://github.com/nanopool/nanominer/issues 64 | * Community chat in telegram (developers read it too): https://t.me/nanominer_en 65 | * Our Discord channel https://discord.gg/JtKHCbm8Yg 66 | 67 | ## Setup 68 | At launch **nanominer** reads the _config.ini_ setup file from the program's current directory. In order to 69 | assign a specific name to the config file, it should be written as the first argument in the command 70 | line. For example: 71 | ``` 72 | nanominer.exe config_etc.ini 73 | ``` 74 | 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). 75 | 76 | **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](https://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. 77 | 78 | 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. 79 | ## Log Files 80 | 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). 81 | 82 | ## Remote Monitoring 83 | **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). 84 | 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). 85 | [BoringAPI](https://github.com/nanopool/BoringAPI) for getting rig statistics is supported aswell, which can be found on http://127.0.0.1:9090/stats. 86 | 87 | **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. 88 | 89 | ## Automatic Restart Function 90 | 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. 91 | 92 | 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. 93 | 94 | 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. 95 | 96 | More detailed information on using these functions can be found in the _Parameters_ section of this file. 97 | 98 | ## Parameters 99 | 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: 100 | ```ini 101 | commonparameter1=commonvalue1 102 | commonparameter2=commonvalue2 103 | commonparameterX=commonvalueX 104 | 105 | [AlgoName1] 106 | devices=0,1 107 | wallet = wallet1 108 | algoparameter1=algovalue1_1 109 | algoparameter2=algovalue1_2 110 | algoparameterY=algovalue1_Y 111 | 112 | [AlgoName2] 113 | devices=2,3 114 | wallet = wallet2 115 | algoparameter1=algovalue2_1 116 | algoparameter2=algovalue2_2 117 | algoparameterZ=algovalue2_Z 118 | 119 | [AlgoName3] 120 | devices=4,5 121 | wallet = wallet3 122 | ``` 123 | More config examples can be found below. 124 | 125 | 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 used instead (note that this rule does not apply to the _wallet_ parameter). 126 | 127 | What follows is a list of the parameters that can be set on **nanominer**. 128 | ### wallet 129 | Mandatory parameter. 130 | This is the user's wallet, where funds will be deposited. 131 | ### coin 132 | Optional parameter. 133 | This chooses the default coin for the pool. The default pool is [nanopool.org](https://nanopool.org/). 134 | The coin parameter accepts one of the following values: ETHW (or EthereumPOW), ETC (or Ethereum Classic), RVN (or Raven), CFX (or Conflux), QKC (or QuarkChain), UBQ (or Ubiq), XMR (or Monero), VRSC (or Verus), ERG (or Ergo), VTC (or Vertcoin), FIRO, ZIL (or Zilliqa). When a coin is specified and equals one of the values mentioned above, **nanominer** automatically tries to determine the pool necessary for it to function if none have been provided in a separate parameter. If a coin is specified but **nanominer** cannot recognize it, then the name of the coin is used only for logging. If a coin is not specified, **nanominer** will use the default coin for the corresponding algorithm. Moreover, if [nanopool.org](https://nanopool.org/) is specified in the configuration file for Ethereum Classic, EthereumPOW, Ergo or Monero, **nanominer** will determine the coin from the pool's settings. 135 | 136 | *Important*: when using **nanominer** to mine EthereumPOW on the default pool, it is necessary to define the coin (coin=ETHW). In that case the pools will be determined automatically. 137 | 138 | If the pools are clearly defined with the aid of the _pool1, pool2, ..._, parameters, then **nanominer** will function according to the tasks it receives from those pools. 139 | ### rigName 140 | Optional parameter. Can be specified in common parameter section instead of the algorithm section to be applied for all algorithms at once. 141 | This is the name of the rig (computer/worker). It will be displayed in the pool's statistics. If this parameter is not set, the program will generate a unique name and provide it to the pool. To disable rigname completely just set it to empty string with 142 | ```ini 143 | rigName= 144 | ``` 145 | ### email 146 | Optional parameter. Can be specified in common parameter section instead of the algorithm section to be applied for all algorithms at once. 147 | This is the user’s e-mail address. It is provided to the pool where the rig will be operating. The pool can use it when sending out service notifications. 148 | ### pool1, pool2, ... 149 | Optional parameter. 150 | This defines the set of mining pools used. Values must be given in the format url:port (e.g. `pool1=etc-eu1.nanopool.org:19999`). The parameters should be defined in ascending, sequential order, from pool1 to poolN (for example: pool1, pool2, pool3). If the pool list is provided, the best pool will be chosen from the order of the pool list. If a `sortPools=true` option is specified, the best pool will be chosen by the connection speed. If the pool (or list of pools) is not defined, **nanominer** will automatically use the pools on [nanopool.org](https://nanopool.org/) that correspond to the chosen cryptocurrency. For QuarkChain public full nodes are used if no pools are defined. For Ubiq [Ubiqpool.io](https://ubiqpool.io) pools are used if no pools are defined. 151 | 152 | ### protocol 153 | Optional parameter. 154 | Can be used to set the pool protocol to _stratum_. If not specified, **nanominer** will try to detect the pool protocol automatically. 155 | 156 | ### rigPassword 157 | Optional parameter. 158 | The password for the rig (or worker). It may be necessary when working with pools that require registration and setting a rig password. 159 | ### watchdog 160 | Optional parameter. 161 | This parameter manages the miner's restart function when running into critical GPU errors or lag. It accepts the values _true_ or _false_. By default, _true_ – automatic restart – is activated. 162 | ### restarts 163 | Optional parameter. 164 | This parameter sets the number of times the miner will restart before rebooting the rig. In case of GPU problems like hardware errors or lag, or in case of hashrate degradation (if the _minhashrate_ option is used), **nanominer** will restart. However, certain errors cannot be fixed by restarting the program. In such cases it is necessary to reboot the rig. To reboot, the miner loads the _reboot.bat_ script from the current directory if running on Windows or _reboot.sh_ if on Linux: 165 | ``` 166 | reboot 167 | ``` 168 | **The reboot.sh file on Linux must be given execute permissions in order for it to work.** 169 | The typical content of the _reboot.bat_ script for Windows: 170 | ``` 171 | shutdown /r /t 5 /f 172 | ``` 173 | The script must be written by the user. 174 | To run reboot script instead of restarting miner every time a critical error occurs, just set `restarts=0` 175 | ### minHashrate 176 | Optional parameter. 177 | This is the minimum acceptable hashrate. This function keeps track of the rig's total hashrate and compares it with this parameter. If five minutes after the miner is launched the set minimum is not reached, **nanominer** will automatically restart. Likewise, the miner will restart if for any reason the average hashrate over a ten-minute period falls below the set value. This value can be set with an optional modifier letter that represents a thousand for kilohash or a million for megahash per second. For example, setting the value to 100 megahashes per second can be written as 100M, 100.0M, 100m, 100000k, 100000K or 100000000. If this parameter is not defined, the miner will not restart (with the exception of the situations described in the _watchdog_ section). Restarts caused by this option count towards the _restarts_ parameter. 178 | ### maxRejectedShares 179 | Optional paramter. 180 | Can be used to set the maximum amount of rejected shares before restarting miner process/rebooting the rig. Restarts caused by this option count towards the _restarts_ parameter. 181 | Option is disabled by default. 182 | ### devices 183 | Optional paramter. 184 | These are the graphics cards that will be used by the miner. If you do not want to launch the miner on all available GPUs but only on some of them, their numbers can be provided in the _devices_ parameter separated by a comma or space. **nanominer** numbers the GPUs starting from zero in ascending order of their PCI addresses. You can see a list of available GPUs and the order in which they're in by launching **nanominer** with the _-d_ command line option: 185 | ``` 186 | nanominer -d 187 | ``` 188 | For example, if there are four GPUs in the system (0, 1, 2, 3) and all but the second-to-last one (indexed as 2) must be set to mine, then the devices option must be set in the following manner: 189 | ```ini 190 | devices=0,1,3 191 | ``` 192 | The order of devices determines the order of displayed hashrate. For example, if it is set as 193 | ```ini 194 | devices=3,1,0 195 | ``` 196 | then the hashrate line will first display GPU3, then GPU1 and finally GPU0. 197 | 198 | ### checkForUpdates 199 | Optional parameter. 200 | This parameter accepts the values _true_ or _false_ (the default is _true_). If this parameter is set to _false_ then **nanominer** stops checking for the newest release version on every startup. 201 | 202 | ### autoUpdate 203 | Optional parameter. 204 | This parameter accepts the values _true_ or _false_ (the default is _false_). If this parameter is set to _true_ and checking for updates is enabled, then **nanominer** will update itself on every startup, provided there is a newer version available. 205 | 206 | ### coreClocks, memClocks 207 | Optional parameters. 208 | Can be used to overclock/underclock NVIDIA GPU's. Absolute (e.g. 4200) as well as relative (e.g. +200, -150) values in MHz are accepted. Parameter values must be separated by a comma or space (first value is for GPU0, second is for GPU1, and so on). For example, if it is set as 209 | ```ini 210 | coreClocks=+200,-150 211 | memClocks=+300,3900 212 | ``` 213 | then GPU0 will be overclocked by 200 MHz of core and 300 MHz of memory, whereas GPU1 core clock will be underclocked by 150 MHz, and its memory clock set to 3900 MHz. 214 | You can also apply same settings for each GPU by defining only one core and memory clock value, for example: 215 | ```ini 216 | coreClocks=+200 217 | memClocks=+300 218 | ``` 219 | 220 | ### powerLimits 221 | Optional parameter. 222 | Can be used to set Nvidia cards power limits from -50 to 50. For example, -20 means 80% power limit, 10 means 110% power limit. Parameter values must be separated by a comma or space (first value is for GPU0, second is for GPU1, and so on). You can also apply same settings for each GPU by defining only one power limit value. 223 | 224 | ### memTweak 225 | Optional parameter. 226 | Can be set to modify AMD GPU timings on the fly for Ethash/Etchash/Ubqhash algorithms. The following AMD ASICs are currently supported: gfx900, gfx901, gfx906, gfx907, Baffin, Ellesmere, gfx804, Hawaii, Tahiti, Pitcairn, Tonga. 227 | 228 | Miner must be launched using admin/root privileges in order to change timings. 229 | 230 | Default memory tweak value is 1 which means slightly improving memory timings. Zero value means timings are left as is without modifications. Parameter values must be separated by a comma or space (first value is for GPU0, second is for GPU1, and so on). Supported memory tweak value range is from 0 to 10 (0 means disabling timings modification, 1 is the least intense, 10 is the most intense), for example: 231 | ```ini 232 | memTweak=9,8,10 233 | ``` 234 | It is recommended to begin from lower values and increase them if the miner works stably. 235 | 236 | You can also apply same settings for each GPU by defining only one memory tweak value: 237 | ```ini 238 | memTweak=10 239 | ``` 240 | 241 | ### fanSpeed 242 | Optional parameter. 243 | Used to set the GPU fan speed to a specific percentage from 30% to 100%. If below 30, automatically sets to 30. If the value is incorrect, i.e. negative or non-numeric value, sets to the last used value. 244 | 245 | ### epoch 246 | Optional parameter. 247 | Ethash algorithm specific option to check miner behaviour on different Ethash epochs. 248 | 249 | ### zilEpoch 250 | Optional parameter. 251 | Sets the epoch of Zilliqa DAG to store in GPU memory (default is 0). 252 | 253 | ### noLog 254 | Optional parameter. 255 | This parameter accepts the values _true_ or _false_ (the default is _false_). If this parameter is set to _true_ then no log files will be recorded onto the hard drive. 256 | 257 | ### noColor 258 | Optional parameter. 259 | This parameter accepts the values _true_ or _false_ (the default is _false_). If this parameter is set to _true_ then the console output won't contain any colors. 260 | 261 | ### logPath 262 | Optional parameter. 263 | This parameter can either be used to set the name of the folder in which log files will be created (e.g. `logPath=logfolder/`), or to specify a path to single file, which will be used for all logs (e.g. `logPath=logs/log.txt`, `logPath=/var/log/nanominer/log.txt`, `logPath=C:\logs\log.txt`). Both relative and absolute paths work. 264 | Default value for this parameter is _logs/_. 265 | 266 | ### webPassword 267 | Optional parameter. 268 | Password for web interface. There is no password by default (web interface is read-only). 269 | 270 | ### webPort 271 | Optional parameter. 272 | Port for web interface. The default port is 9090. Zero value disables web interface. 273 | 274 | ### mport 275 | Optional parameter. 276 | This is the network port for remote monitoring and program management through EthMan or other programs that use a similar API protocol format. 277 | The program supports all API functions, including restarting the miner and rig(s). 278 | You can block miner management through API (in which case the miner will only display the statistics and won't respond to any commands). To enable this function, a "minus" (-) sign must be written before the port number. 279 | And you can completely deactivate remote monitoring. To do this, the port number must be set to "0" (zero). 280 | Default value: -3333 (This means that the miner blocks management through API and displays statistics on port 3333). 281 | 282 | ### ethmanPassword 283 | Optional parameter. 284 | Your password for monitoring with EthMan and other utilities that support the same network API. 285 | 286 | ### useSSL 287 | Optional parameter. 288 | This parameter accepts the values _true_ or _false_ (the default is _true_). If this parameter is set to _true_ then miner always tries to use SSL pool connection first and fallbacks to unencrypted connection if SSL connection failed. If this parameter is set to _false_ then miner doesn't try using SSL for pool connection. 289 | 290 | ### shardId 291 | Optional parameter. 292 | Can be used to set a shard ID for QuarkChain solo mining. This parameter should be specified in hex, e.g. 0x1, 0x10001, 0x10002, 0x50001, etc. For root chain shard ID `null` must be specified. For more information on shards, visit [this](https://github.com/QuarkChain/pyquarkchain/wiki/Address,-Shard-Key,-Chain-Id,-Shard-Id) and [this](https://github.com/quarkChain/pyquarkchain/releases/latest) link. Default shard ID is 0x1. Shard ID is passed to QuarkChain node "as is" so all current and future Ethash shards are supported. 293 | 294 | ### farmRecheck 295 | Optional parameter. 296 | The interval (in milliseconds) between polling the node for new jobs in solo mining mode for QuarkChain. Default value is 200. 297 | 298 | ### cpuThreads 299 | Optional parameter for CPU mining. 300 | Specifies the number of concurrent CPU threads to use for mining. All threads are used by default. 301 | 302 | ### sortPools 303 | Optional parameter. 304 | This parameter accepts the values _true_ or _false_ (the default is _false_). If this parameter is set to _true_ then the best pool will be chosen by least ping (not by the pool list). 305 | 306 | ### countDevShares 307 | Optional parameter. 308 | This parameter accepts the values _true_ or _false_ (the default is _false_ for QuarkChain solo mining and _true_ for other coins). If this parameter is set to _true_ then shares accepted or rejected by pool during fee time will be included in miner statistics. Otherwise only shares during user mining are included to miner statistics. 309 | 310 | ### validateShares 311 | Optional parameter. 312 | This parameter accepts the values _true_ or _false_ (the default is _false_). If this parameter is set to _true_ then shares of ethash algorithms family on AMD GPUs are validated by CPU. Also in this case share difficulty is shown for AMD GPUs. 313 | 314 | ### sendHashrate 315 | Optional parameter for Ethash, Etchash and Ubqhash algorithms. This parameter accepts the values _true_ or _false_. The default value is _true_ (if JSON-RPC pool protocol is used). 316 | 317 | ### silence 318 | Optional parameter. This parameter accepts the values from 0 to 3. Control the amount of information displayed in the logs and on the screen. 319 | 0: All the information is logged. Default behaviour. 320 | 1: Hide frequent job messages. 321 | 2: Also hide shares messages. 322 | 3: Also hide hashrate prints. 323 | 324 | ### dagSer 325 | Optional parameter for Ethash, Etchash, FiroPow and KawPow algorithms. 326 | This parameter accepts the values _true_ or _false_ (the default is _false_). If this parameter is set to _true_ then the DAG will be generated sequentially on each GPU. Otherwise all the GPUs generate DAG at the same time. 327 | 328 | ### lhr 329 | Optional parameter for Ethash and Etchash algorithms. Can be used to set desired percentage of full unlocked hashrate. Valid range is from 50 to 100. Also can be set to _off_ (-1) or _auto_ (0). Use _off_ for non-LHR cards and _auto_ for automatic LHR card detection and tuning. Default is _auto_. This parameter can be set for each GPU separately. In this case, order must correspond to the order of GPUs, specified in _devices_ parameter. For example: 330 | ```ini 331 | devices=0,2,3 332 | lhr=71.5,off,0 333 | ``` 334 | means 71.5% for GPU0, _off_ for GPU2 and _auto_ for GPU3. 335 | 336 | ## Configuration File 337 | The minimum configuration file for Ethereum Classic may contain only a wallet: 338 | ```ini 339 | wallet= 340 | ``` 341 | **nanominer** will automatically use Ethereum Classic pools. 342 | 343 | To work with EthereumPOW, the coin must be specified: 344 | ```ini 345 | wallet= 346 | coin=ETHW 347 | ``` 348 | In this case **nanominer** will use pools corresponding to EthereumPOW. 349 | 350 | ## IMPORTANT! 351 | For coins that are not supported by [nanopool.org](https://nanopool.org/), **you must** specify a **wallet** and pools (**pool1...**). 352 | 353 | ## Launching from command line 354 | It is possible to run nanominer from the command line with the desired arguments. At least one algorithm and wallet are required to be passed. All common config parameters in the command line must be specified before the first "algo" parameter. Here are some examples of command lines for launching Ethereum Classic and Monero: 355 | 356 | Windows: 357 | ``` 358 | nanominer.exe -algo etchash -wallet YOUR_ETC_WALLET -coin eth -rigName YOUR_ETC_WORKER -email YOUR_EMAIL -algo randomx -wallet YOUR_XMR_WALLET -coin xmr -rigName YOUR_XMR_WORKER -email YOUR_EMAIL 359 | ``` 360 | Linux: 361 | ``` 362 | ./nanominer -algo etchash -wallet YOUR_ETC_WALLET -coin eth -rigName YOUR_ETC_WORKER -email YOUR_EMAIL -algo randomx -wallet YOUR_XMR_WALLET -coin xmr -rigName YOUR_XMR_WORKER -email YOUR_EMAIL 363 | ``` 364 | 365 | If no algo specified, etchash is used by default. So the following commands will launch the etchash algorithm: 366 | 367 | Windows: 368 | ``` 369 | nanominer.exe -wallet YOUR_WALLET 370 | ``` 371 | Linux: 372 | ``` 373 | ./nanominer -wallet YOUR_WALLET 374 | ``` 375 | 376 | The helper scripts folder with all of its contents is still there, for those who use it. 377 | 378 | ## Examples of Configuration Files 379 | 380 | Example of a configuration file for Ethereum Classic and Monero: 381 | ```ini 382 | [Etchash] 383 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 384 | rigName = rig1 385 | email = someemail@org 386 | pool1 = etc-eu1.nanopool.org:19999 387 | pool2 = etc-eu2.nanopool.org:19999 388 | pool3 = etc-us-east1.nanopool.org:19999 389 | pool4 = etc-us-west1.nanopool.org:19999 390 | pool5 = etc-asia1.nanopool.org:19999 391 | pool6 = etc-jp1.nanopool.org:19999 392 | pool7 = etc-au1.nanopool.org:19999 393 | [RandomX] 394 | wallet = fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 395 | rigName = rig1 396 | email = someemail@org 397 | pool1 = xmr-eu1.nanopool.org:14433 398 | pool2 = xmr-eu2.nanopool.org:14433 399 | pool3 = xmr-us-east1.nanopool.org:14433 400 | pool4 = xmr-us-west1.nanopool.org:14433 401 | pool5 = xmr-asia1.nanopool.org:14433 402 | ``` 403 | Example of a configuration file for split Ethereum Classic and Zilliqa: 404 | ```ini 405 | [Etchash] 406 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 407 | ; nanopool by default 408 | [Zilliqa] 409 | wallet = zilxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 410 | pool1 = eu.ezil.me:4444 411 | pool2 = us-west.ezil.me:4444 412 | pool3 = asia.ezil.me:4444 413 | ``` 414 | 415 | Example of a configuration file for merged Ethereum Classic and Zilliqa: 416 | ```ini 417 | [Etchash] 418 | wallet = 0xffffffffffffffffffffffffffffffffffffffff.zilxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 419 | zilEpoch = 0 420 | pool1 = eu.ezil.me:4444 421 | pool2 = us-west.ezil.me:4444 422 | pool3 = asia.ezil.me:4444 423 | ``` 424 | Example of a configuration file for Ethereum Classic: 425 | ```ini 426 | [Etchash] 427 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 428 | rigName = rig1 429 | email = someemail@org 430 | pool1 = etc-eu1.nanopool.org:19999 431 | pool2 = etc-eu2.nanopool.org:19999 432 | pool3 = etc-us-east1.nanopool.org:19999 433 | pool4 = etc-us-west1.nanopool.org:19999 434 | pool5 = etc-asia1.nanopool.org:19999 435 | pool6 = etc-jp1.nanopool.org:19999 436 | pool7 = etc-au1.nanopool.org:19999 437 | ``` 438 | Example of an equivalent file for Ethereum Classic: 439 | ```ini 440 | [Etchash] 441 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 442 | rigName = rig1 443 | email = someemail@org 444 | ``` 445 | Example of a minimum file for Ethereum Classic: 446 | ```ini 447 | [Etchash] 448 | wallet=0xffffffffffffffffffffffffffffffffffffffff 449 | ``` 450 | Example of a configuration file for split EthereumPOW and Zilliqa: 451 | ```ini 452 | [Ethash] 453 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 454 | ; nanopool by default 455 | [Zilliqa] 456 | wallet = zilxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 457 | pool1 = eu.ezil.me:4444 458 | pool2 = us-west.ezil.me:4444 459 | pool3 = asia.ezil.me:4444 460 | ``` 461 | Example of a configuration file for EthereumPOW: 462 | ```ini 463 | [Ethash] 464 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 465 | coin=ETHW 466 | rigName = rig1 467 | email = someemail@org 468 | pool1 = ethw-eu1.nanopool.org:15433 469 | pool2 = ethw-eu2.nanopool.org:15433 470 | pool3 = ethw-us-east1.nanopool.org:15433 471 | pool4 = ethw-us-west1.nanopool.org:15433 472 | pool5 = ethw-asia1.nanopool.org:15433 473 | pool6 = ethw-jp1.nanopool.org:15433 474 | pool7 = ethw-au1.nanopool.org:15433 475 | ``` 476 | Example of an equivalent file for EthereumPOW: 477 | ```ini 478 | [Ethash] 479 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 480 | coin=ETHW 481 | rigName = rig1 482 | email = someemail@org 483 | ``` 484 | Example of a minimum file for EthereumPOW: 485 | ```ini 486 | [Ethash] 487 | wallet=0xffffffffffffffffffffffffffffffffffffffff 488 | coin=ETHW 489 | ``` 490 | Example of a complete configuration file for solo QuarkChain mining: 491 | ```ini 492 | [Ethash] 493 | wallet=0xffffffffffffffffffffffffffffffffffffffff 494 | shardId=0x30001 495 | farmRecheck=200 496 | coin=Qkc 497 | pool1=localhost:38391 498 | protocol=getwork 499 | ``` 500 | Example of a minimum file for solo QuarkChain mining: 501 | ```ini 502 | [Ethash] 503 | wallet=0xffffffffffffffffffffffffffffffffffffffff 504 | coin=Qkc 505 | pool1=localhost:38391 506 | shardId=0x50001 507 | ``` 508 | Example of a file for solo QuarkChain mining on root shard: 509 | ```ini 510 | [Ethash] 511 | wallet=0xffffffffffffffffffffffffffffffffffffffff 512 | coin=Qkc 513 | pool1=localhost:38391 514 | shardId=null 515 | ``` 516 | Example of a minimum file for QuarkChain mining using public nodes: 517 | ```ini 518 | [Ethash] 519 | wallet=0xffffffffffffffffffffffffffffffffffffffff 520 | coin=Qkc 521 | shardId=0x30001 522 | ``` 523 | 524 | Example of a configuration file for Ubiq: 525 | ```ini 526 | [Ubqhash] 527 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 528 | coin=Ubq 529 | rigName = rig1 530 | email = someemail@org 531 | pool1 = us.ubiqpool.io:8008 532 | pool2 = eu.ubiqpool.io:8008 533 | ``` 534 | Example of a minimum file for Ubiq: 535 | ```ini 536 | coin=UBQ 537 | wallet=0xffffffffffffffffffffffffffffffffffffffff 538 | ``` 539 | Example of a complete file for Monero: 540 | ```ini 541 | [RandomX] 542 | wallet = fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 543 | rigName = rig1 544 | email = someemail@org 545 | pool1 = xmr-eu1.nanopool.org:14433 546 | pool2 = xmr-eu2.nanopool.org:14433 547 | pool3 = xmr-us-east1.nanopool.org:14433 548 | pool4 = xmr-us-west1.nanopool.org:14433 549 | pool5 = xmr-asia1.nanopool.org:14433 550 | ``` 551 | Example of an equivalent file for Monero: 552 | ```ini 553 | [RandomX] 554 | wallet = fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 555 | rigName = rig1 556 | email = someemail@org 557 | ``` 558 | Example of a minimum file for Monero: 559 | ```ini 560 | [RandomX] 561 | wallet = fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 562 | ``` 563 | 564 | Example of a minimum file for Zephyr: 565 | ```ini 566 | [RandomX] 567 | wallet = fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 568 | pool1 = zeph-eu1.nanopool.org:10943 569 | ``` 570 | 571 | Example of a configuration file for Ravencoin: 572 | ```ini 573 | [Kawpow] 574 | wallet = Rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 575 | coin=Rvn 576 | rigName = rig1 577 | email = someemail@org 578 | pool1 = rvn-eu1.nanopool.org:12433 579 | pool2 = rvn-eu2.nanopool.org:12433 580 | pool3 = rvn-us-east1.nanopool.org:12433 581 | pool4 = rvn-us-west1.nanopool.org:12433 582 | pool5 = rvn-asia1.nanopool.org:12433 583 | pool6 = rvn-jp1.nanopool.org:12433 584 | pool7 = rvn-au1.nanopool.org:12433 585 | 586 | ``` 587 | Example of a minimum file for Ravencoin: 588 | ```ini 589 | wallet=Rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr 590 | ``` 591 | 592 | Example of a complete file for Conflux: 593 | ```ini 594 | [Octopus] 595 | wallet = cfx:ffffffffffffffffffffffffffffffffffffffffff 596 | rigName = rig1 597 | email = someemail@org 598 | pool1=cfx-eu1.nanopool.org:17433 599 | pool2=cfx-eu2.nanopool.org:17433 600 | pool3=cfx-us-east1.nanopool.org:17433 601 | pool4=cfx-us-west1.nanopool.org:17433 602 | pool5=cfx-asia1.nanopool.org:17433 603 | pool6=cfx-jp1.nanopool.org:17433 604 | pool7=cfx-au1.nanopool.org:17433 605 | ``` 606 | 607 | Example of an equivalent file for Conflux: 608 | ```ini 609 | [Octopus] 610 | wallet = cfx:ffffffffffffffffffffffffffffffffffffffffff 611 | rigName = rig1 612 | email = someemail@org 613 | ``` 614 | Example of a minimum file for Conflux: 615 | ```ini 616 | wallet = cfx:ffffffffffffffffffffffffffffffffffffffffff 617 | coin = CFX 618 | ``` 619 | Example of a configuration file for Conflux and Zilliqa: 620 | ```ini 621 | [Octopus] 622 | wallet = cfx:ffffffffffffffffffffffffffffffffffffffffff 623 | [Zilliqa] 624 | wallet = zilxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 625 | pool1 = eu.ezil.me:4444 626 | pool2 = us-west.ezil.me:4444 627 | pool3 = asia.ezil.me:4444 628 | ``` 629 | 630 | Example of a complete file for VerusCoin: 631 | ```ini 632 | [Verushash] 633 | wallet = REoPcdGXthL5yeTCrJtrQv5xhYTknbFbec 634 | coin = VRSC 635 | rigName = speed_test 636 | rigPassword=d=4 637 | cpuThreads=4 638 | pool1 = na.luckpool.net:3956 639 | ``` 640 | 641 | Example of a minimum file for VerusCoin: 642 | ```ini 643 | coin = VRSC 644 | wallet = REoPcdGXthL5yeTCrJtrQv5xhYTknbFbec 645 | pool1 = na.luckpool.net:3956 646 | ``` 647 | 648 | Example of a complete file for Ergo: 649 | ```ini 650 | [autolykos] 651 | wallet = 9he6BZYMN8FMKxYKsqPvQJ6fbNar4bWuhJsR9JJt4x9Z6fiqSo1 652 | rigName = rig1 653 | email = someemail@org 654 | pool1 = ergo-eu1.nanopool.org:11433 655 | pool2 = ergo-us-east1.nanopool.org:11433 656 | pool3 = ergo-us-west1.nanopool.org:11433 657 | pool4 = ergo-eu2.nanopool.org:11433 658 | pool5 = ergo-asia1.nanopool.org:11433 659 | pool6 = ergo-jp1.nanopool.org:11433 660 | pool7 = ergo-au1.nanopool.org:11433 661 | ``` 662 | 663 | Example of an equivalent file for Ergo: 664 | ```ini 665 | [autolykos] 666 | wallet = 9he6BZYMN8FMKxYKsqPvQJ6fbNar4bWuhJsR9JJt4x9Z6fiqSo1 667 | rigName = rig1 668 | email = someemail@org 669 | ``` 670 | Example of a minimum file for Ergo: 671 | ```ini 672 | coin=ergo 673 | wallet = 9he6BZYMN8FMKxYKsqPvQJ6fbNar4bWuhJsR9JJt4x9Z6fiqSo1 674 | ``` 675 | 676 | Example of a configuration file for Firo: 677 | ```ini 678 | [FiroPow] 679 | wallet = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa 680 | coin=Firo 681 | rigName = rig1 682 | email = someemail@org 683 | pool1 = firo-eu1.picopool.org:22222 684 | 685 | ``` 686 | 687 | Example of IronFish 688 | ```ini 689 | [fishhash] 690 | wallet = 388b74938c5996a491d315cc75d425832ed47bcf258c7759a5e275fc84a3fa5d 691 | ``` 692 | 693 | Example of dual mining ETC + Zilliqa 694 | ```ini 695 | [etchash] 696 | wallet = 0x9eab4b0fc468a7f5d46228bf5a76cb52370d068d 697 | 698 | [zil] 699 | wallet = zil1rpxnv479xy9c2jlgry3wy3869rnt4rjvjwjtuv 700 | pool1 = eu.etc.k1pool.com:1111 701 | zilEpoch = 1 ; number of DAG epoch for caching 702 | ``` 703 | 704 | Example of configuration file for mining Ethereum Classic, Ergo, Ubiq and Monero on same 8 GPUs rig using separate devices: 705 | ```ini 706 | rigName = rig1 707 | [Etchash] 708 | wallet = 0xffffffffffffffffffffffffffffffffffffffff 709 | devices = 0,1 710 | [Autolykos] 711 | wallet = 9he6BZYMN8FMKxYKsqPvQJ6fbNar4bWuhJsR9JJt4x9Z6fiqSo1 712 | devices = 5 713 | [Ubqhash] 714 | wallet = 0x1111111111111111111111111111111111111111 715 | pool1 = eu.ubiqpool.io:8008 716 | devices = 2,3,4,6,7 717 | [RandomX] 718 | wallet=fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff 719 | ``` 720 | 721 | Example of configuration file for mining Raven, Zilliqa and Nevocoin: 722 | ```ini 723 | [kawpow] 724 | wallet = RRL5mMNeox75MGbqnfUZEhn3RferuvFGcy 725 | 726 | [zil] 727 | wallet = zil1rpxnv479xy9c2jlgry3wy3869rnt4rjvjwjtuv 728 | zilEpoch = 1 ; number of DAG epoch for caching 729 | pool1 = eu.ezil.me:4444 730 | 731 | [RandomNevo] 732 | wallet = NS3B3hTCmhMZiMMpm7mPv56mLWGjUntbcUGiDtXyMHkh31PPd2kuyW6bTs7urbpLUPR2AZVWMgTmY5C6LEaiQeA41mTKBSZ9c 733 | pool1 = nevocoin.ch:2052 734 | ``` 735 | -------------------------------------------------------------------------------- /Terms of Use Nanominer.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/nanopool/nanominer/ef65c9c3d948a6ee9e51e0c03fb050cba0226cba/Terms of Use Nanominer.pdf --------------------------------------------------------------------------------