CommerciumBlockchain // Commercium Pool-github
Zcash® and Zclassic – Node Open Mining Portal
This is a Equihash mining pool based off of Node Open Mining Portal.
Production Usage Notice
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.
Community / Support
If your pool uses Z-NOMP let us know and we will list your website here.
Some pools using Z-NOMP or node-stratum-module:
http://luckpool.org Zcash Pool with Custom Frontend w/Miner’s Jackpot
http://zclmine.com/ Custom frontend
http://zclassic.miningspeed.com Custom frontend and 0% fee
https://zpool.it 0.5% fee
- Coin daemon(s) (find the coin’s repo and build latest version from source)
- Node.js v7+ (follow these installation instructions)
- Redis key-value store v2.6+ (follow these instructions)
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.
0) Setting up coin daemon
Follow the build/install instructions for your coin daemon. Your coin.conf file should end up looking something like this:
daemon=1 rpcuser=x rpcpassword=q rpcport=16112
For 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:
1) Downloading & Installing
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/Snowgem/snowgem-pool.git z-nomp cd z-nomp npm update npm install
Take a look at the example json file inside the
pool_configs directory. Rename it to
snowgem.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.
[Optional, recommended] Setting up blocknotify
config.jsonset the port and password for
- In your daemon conf file set the
blocknotifycommand to use:
node [path to cli.js] [coin name in config] [block hash symbol]
snowgem.conf add the line
blocknotify=node /home/user/z-nomp/scripts/cli.js blocknotify zclassic %s
Alternatively, you can use a more efficient block notify script written in pure C. Build and usage instructions are commented in scripts/blocknotify.c.
3) Start the portal
Optional enhancements for your awesome new mining pool server setup:
- Use something like forever to keep the node script running in case the master process crashes.
- Use something like redis-commander to have a nice GUI for exploring your redis database.
- Use something like logrotator to rotate log output from Z-NOMP.
- Use New Relic to monitor your Z-NOMP instance and server performance.
When 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-multi-hashing modules, and any config files that may have been changed.
- Inside your Z-NOMP directory (where the init.js script is) do
git pullto get the latest Z-NOMP code.
- Remove the dependenices by deleting the
rm -r node_modules.
npm updateto force updating/reinstalling of the dependencies.
- Compare your
pool_configs/coin.jsonconfigurations 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.
|Type||Name||Latest commit message||Commit time|
|coins||4 months ago|
|libs||8 months ago|
|pool_configs||8 months ago|
|scripts||8 months ago|
|website||8 months ago|
|.gitignore||8 months ago|
|CHANGELOG.md||8 months ago|
|LICENSE||8 months ago|
|README.md||8 months ago|
|config_example.json||8 months ago|
|init.js||8 months ago|
|npm-debug.log||8 months ago|
|package-lock.json||8 months ago|
|package.json||8 months ago|