- Differences between this and Z-NOMP
- Using Docker (easy)
- Bare metal installation
- More Config Information
- License
- This is meant for Komodo mining
- Founders, Treasury, and other ZEC/ZEN specific stuff is removed
This method sets up 2 docker containers, one with knomp and one with redis.
It will directly use your host system's network so you can connect to the coin daemon without opening up RPC beyond 127.0.0.1.
The ports it listens on must not be in use, this includes 8080 for the website, 6379 for redis and any ports you open for stratums (default is 3333).
Install Docker and docker-compose
git clone https://github.com/webworker01/knomp.git
cd ./knomp
cp config_example.json config.json
Setup your config.json, ./coins/
and ./pool_configs/
in here, then:
docker-compose up &
docker-compose down
docker-compose down
docker rmi knomp_knomp
git pull
docker-compose up &
- node v10
- libsodium
- boost
- Redis (see https://redis.io/topics/quickstart for details)
Please be sure to backup your ./coins
and ./pool_configs
directory before upgrading
Kill your running pool (CTRL-C)
cd knomp
git pull
npm install
npm start
Some initial setup
# The following packages are needed to build both Komodo and this stratum:
sudo apt-get update
sudo apt-get install build-essential pkg-config libc6-dev m4 g++-multilib autoconf libtool ncurses-dev unzip git python python3-zmq zlib1g-dev wget libcurl4-openssl-dev bsdmainutils automake curl libboost-dev libboost-system-dev libsodium-dev jq redis-server nano -y
Now, let's build Komodo
git clone https://github.com/jl777/komodo -b dev
cd komodo
zcutil/fetch-params.sh
zcutil/build.sh -j8
strip src/komodod
strip src/komodo-cli
Now, let's run the assets. This will start ALL of the assets might take a day or so to sync, depending on system speed/network connection.
If you are setting up a single chain to mine and/or don't know what pubkey is, skip this step and use the startup params for the komodod daemon as provided by the individual coin's team.
cd ~/komodo/src
./assetchains
Once all the chains you want on your pool have synced up we can configure the stratum.
We need node and npm installed
# Install NVM
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
# Install node 14
nvm install 14
# Use node 14
nvm use 14
Now, let's build our stratum and run it. This will install the pool and configure it for all the assetchains on your system automatically. It must be run from the same user as the coin deamons were launched, as it pulls the rpcuser/pass from the conf file in the home directory.
git clone https://github.com/webworker01/knomp
cd knomp
npm install
cp config_example.json config.json (and configure it)
nano gencfg.sh
Edit line 3 in so that it has your own KMD based address, CTRL-X then Y to save and exit
We need to generate the coins files (coin daemon must be running!): gencfg.sh <coin name>
You can run just gencfg.sh with no coin name to use the assetchains.json in komodo/src directory for all coins. Make sure you edit the template with the correct values you want before running the config generator.
Finally we are ready to start the pool software
npm start
If all went well the program should start without error and you should be able to browse to your pool website on your server via port 8080.
This mode uses -pubkey to tell the daemon where the coinbase should be sent, and uses the daemons coinbase transaction rather then having the pool create the coinabse transaction. This enables special coinbase transactions, such as ac_founders and ac_script or new modes with CC vouts in the coinbase not yet created, it will work with all coins, except Full Z support described below.
To enable it, change the value in the ./coins/*.json
to "disablecb" : true
The pool fee is taken in the payment processor using this mode, and might not be 100% accurate down to the single satoshi, so the pool address may end up with some small amount of coins over time.
Please note that the default configs generated are for solo mining. If you wish to create a public pool please modify the configs like in this example config
There is now a config option you can add to your pool_configs/coin.json to toggle making an attempt at a payment upon pool startup.
"paymentProcessing": {
"payOnStart": true,
...
}
You can add an option to your pool_config to have any miners that mine with an invalid address (if they somehow get through) to pay out to an address of your choosing
"invalidAddress":"zsValidAddressOfYourChoosingThatsNotThePoolZAddress"
This is an option to force miners to use a Z address as their username for payouts
In your coins file add:
"privateChain": true,
"burnFees": true
In coins/pirate.json file:
"privateChain": true,
"burnFees": true,
"sapling": 152855
Please note, PIRATE sapling became active around 2018-12-15 01:15UTC at block 152855 Now that this has passed this can just be set to "sapling":true
In pool_config:
"zAddress": "zsPoolsSaplingAddress",
"walletInterval": 2,
"validateWorkerUsername": true,
"paymentProcessing": {
"minConf": 5,
"paymentInterval": 180,
"maxBlocksPerPayment": 20,
Further info on config and some sample configs
Forked from ComputerGenie repo (deleted)
Released under the GNU General Public License v2 http://www.gnu.org/licenses/gpl-2.0.html
Forked from z-classic/z-nomp which is incorrectly licensed under MIT License - see zone117x/node-open-mining-portal