import a couple of source files from the program const parseOptions = require ( "./nicehash-calculator/options/index" ). Take the compiled JavaScript (the dist folder) and just drop it into your project somewhere (in this example a folder named "nicehash-calculator"). If you are already using nodejs, you could interface directly with the source code. (Hint: use node -no-header -no-warnings -output=json to only print machine readable JSON) nicehash-calculator-web used to do this in the past. You could spawn a new node process and read stdout. (hint: use -debug to find out what URLs are being requested - look for request(): requested. If you only care about a few specific coins, then just use the What to Mine API directly. See `Running` Using nicehash-calculator in other programs
Mining hash calculator x16r update#
# Update dependencies & build the new code (see `Usage`) # Reset any changes you made and pull new changes from GitHub # If these commands do not work, delete the repository and clone it again. Instructions for upgrading from an older version of nicehash-calculator to a newer one. * Ethereum Classic (ETC) (DaggerHashimoto) As coins become inactive they will become unsupported. * Bitcoin (BTC) (SHA-256) Supported coinsĪs coins are added to What To Mine they should automatically be supported if they use an algorithm on NiceHash. # You can easily determine what your filters include using `-list-coins` # To monitor all Scrypt coins except Litecoin and also monitor Bitcoin you could do: To monitor all Scrypt coins **except** Litecoin you could do: # You can mix exclusion rules with regular rules. # To monitor all coins **except** Scrypt coins you could do: # To run on all coins **except** Bitcoin you could do: # You can prepend a single `-` to any filter (coin name, coin ticker, algorithm name, etc.) to disable that coin (or algorithm) instead of enabling it. # To monitor all Scrypt coins and Bitcoin you could do: # Coin names/tickers and algorithm names can be mixed together. # To monitor all Scrypt coins you could do: # You can also use the names of algorithms to monitor all coins of that algorithm. # A coin's ticker or abbreviation has the same effect as the name: # To monitor only Bitcoin, Litecoin, and Ethereum you could do: # The easiest filtering rule is to simply list the names of the coins you want to monitor. # Warnings will be printed if something you enter is not recognized. 'bitcoin', 'bItCoIn', 'Bitcoin', and 'bITCOIN' all have the same effect. Coin filtering rules allow you to do this: Instead, you probably want to monitor a few specific coins or algorithms that you have wallets or pools setup for. This is slow and probably not what you want. Coinsīy default it will do calculations for all known coins. You can also put arguments you would like to always be added in arguments.txt. 1000 can be replaced with any other number (including 0 to effectively disable a delay, but be warned you might get hit by rate limits)ĭelay between runs with watch mode enabled Valid values for thing are minimum (minimum with miners) and minimum-with-speedĬhanges the time waited between each coin in milliseconds. Valid values for thing are pretty (default), json, and delayed-jsonĬhanges the how prices to buy hashing power are obtained. ArgumentĮnables experimental fee support (only a 3% fee in calculations for now)ĭisables the large message printed at the startĬhanges the format of the output. You should see a warning if you did something wrong.
You must use an = to seperate argument names from their value if an arguments takes a value (do not use a space instead of =). You must use - before each argument name, - will not work (it is used for coin filtering). Npm start - ArgumentsĪrgument parsing is very strict.
0 kommentar(er)
