Click here for the official - Zcash® and Zclassic Stratum Mining Pool Installation Guide
This is a Equihash mining pool based off of Node Open Mining Portal.
Donations for development are greatly appreciated!
This is beta software. All of the following are things that can change and break an existing Z-NOMP setup: functionality of any feature, structure of configuration files and structure of redis data. If you use this software in production then DO NOT pull new code straight into production usage because it can and often will break your setup and require you to tweak things like config files or redis data. Only tagged releases are considered stable.
Usage of this software requires abilities with sysadmin, database admin, coin daemons, and sometimes a bit of programming. Running a production pool can literally be more work than a full-time job.
IRC
If your pool uses Z-NOMP let us know and we will list your website here.
http://mineflowpool.pl Z-nomp based pool. Custom frontend and API.
http://luckpool.org Zcash Pool with Custom Frontend w/Miner's Jackpot
http://zclassic.miningspeed.com Custom frontend and 0% fee
https://lucky-mining.com.ua/ Running MPOS and no fee, [vot][zcl][zen][hush][btg].lucky-mining.com.ua <-- Ukraine
Those are legitimate requirements. If you use old versions of Node.js or Redis that may come with your system package manager then you will have problems. Follow the linked instructions to get the last stable versions.
Redis security warning: be sure firewall access to redis - an easy way is to
include bind 127.0.0.1 in your redis.conf file. Also it's a good idea to learn about and understand software that
you are using - a good place to start with redis is data persistence.
Follow the build/install instructions for your coin daemon. Your coin.conf file should end up looking something like this:
daemon=1
rpcuser=zclassicrpc
rpcpassword=securepassword
rpcport=8232For redundancy, its recommended to have at least two daemon instances running in case one drops out-of-sync or offline,
all instances will be polled for block/transaction updates and be used for submitting blocks. Creating a backup daemon
involves spawning a daemon using the -datadir=/backup command-line argument which creates a new daemon instance with
it's own config directory and coin.conf file. Learn about the daemon, how to use it and how it works if you want to be
a good pool operator. For starters be sure to read:
Clone the repository and run npm update for all the dependencies to be installed:
sudo apt-get install build-essential libsodium-dev npm
sudo npm install n -g
sudo n stable
git clone https://github.com/joshuayabut/node-open-mining-portal.git z-nomp
cd z-nomp
npm update
npm installTake a look at the example json file inside the pool_configs directory. Rename it to zclassic.json and change the
example fields to fit your setup.
Please Note that: 1 Difficulty is actually 8192, 0.125 Difficulty is actually 1024.
Whenever a miner submits a share, the pool counts the difficulty and keeps adding them as the shares.
ie: Miner 1 mines at 0.1 difficulty and finds 10 shares, the pool sees it as 1 share. Miner 2 mines at 0.5 difficulty and finds 5 shares, the pool sees it as 2.5 shares. config.json set the port and password for blockNotifyListenerblocknotify command to use:
node [path to cli.js] [coin name in config] [block hash symbol]Example: inside zclassic.conf add the line
blocknotify=node /home/user/z-nomp/scripts/cli.js blocknotify zclassic %sAlternatively, you can use a more efficient block notify script written in pure C. Build and usage instructions are commented in scripts/blocknotify.c.
npm startWhen updating Z-NOMP to the latest code its important to not only git pull the latest from this repo, but to also update
the node-stratum-pool and node-multi-hashing modules, and any config files that may have been changed.
git pull to get the latest Z-NOMP code.node_modules directory with rm -r node_modules.npm update to force updating/reinstalling of the dependencies.config.json and pool_configs/coin.json configurations to the latest example ones in this repo or the ones in the setup instructions where each config field is explained. You may need to modify or add any new changes.Released under the MIT License. See LICENSE file.