Skip to content
ZNY-NOMP is mining pool software for BitZeny so you can create internet money in your home!
Branch: master
Clone or download
Pull request Compare This branch is 152 commits ahead, 12 commits behind yoshuki43:master.
Type Name Latest commit message Commit time
Failed to load latest commit information.
coins Add missing getReadableLuckTime Jul 6, 2019
libs Update paymentProcessor.js Mar 11, 2019
pool_configs Add CPUchain support Jul 5, 2019
scripts add doc Jan 4, 2018
website Add missing getReadableLuckTime Jul 6, 2019
.gitignore Add CPUchain support Jul 5, 2019 Create Nov 28, 2016
LICENSE Updated to MIT license Dec 27, 2016 Update Jan 29, 2019
config_example.json add redis password auth Jul 2, 2017
init.js Update init.js May 12, 2017
package.json Update package.json Jan 19, 2019

BitZeny - Node Open Mining Portal

This is a Yescrypt-0.5, YesPoWer, Lyra2REv2, sha256d and more algo mining pool based off of Node Open Mining Portal.

Donations for development are greatly appreciated!

  • ZNY: ZmnBu9jPKvVFL22PcwMHSEuVpTxFeCdvNv
  • NUKO: 0xa79bde46faab3c40632604728e9f2165b052581c
  • KOTO :k16dV6stRkFtZpFtMTrznqvavRuMfh4PB1R
  • SUSU: SeXbMBaax7NgnTEFEMxin5ycXy9r9CDBot
  • MONA: mona1qnur6ljkl5pe8w6ql8xfqw4aa38d5xa9q68dxll
  • BELL: BCVicYRSqKKt1ynJKPrXHA46hUWLrbjR49
  • BTC: 3KedzPANAtCzADPbhT7GMv3LjxyeRXc4AE

Production Usage Notice

This is beta software. All of the following are things that can change and break an existing ZNY-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.

Paid Solution

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.





If your pool uses ZNY-NOMP let us know and we will list your website here.

Some pools using ZNY-NOMP or node-stratum-yescrypt-0.5-module:




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 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:


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 v9
git clone
cd zny-nomp
npm update
npm install
Pool config

Take a look at the example json file inside the pool_configs directory. Rename it to bitzeny.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
  1. In config.json set the port and password for blockNotifyListener
  2. In your daemon conf file set the blocknotify command to use:
node [path to cli.js] [coin name in config] [block hash symbol]

Example: inside bitzeny.conf add the line

blocknotify=node /home/user/zny-nomp/scripts/cli.js blocknotify bitzeny %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

npm start
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 ZNY-NOMP.
  • Use New Relic to monitor your ZNY-NOMP instance and server performance.

Upgrading ZNY-NOMP

When updating ZNY-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-yescrypt-0.5 and node-multi-hashing-yescrypt-0.5 modules, and any config files that may have been changed.

  • Inside your ZNY-NOMP directory (where the init.js script is) do git pull to get the latest ZNY-NOMP code.
  • Remove the dependenices by deleting the node_modules directory with rm -r node_modules.
  • Run npm update to force updating/reinstalling of the dependencies.
  • Compare your 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.

You can’t perform that action at this time.