This a step by step guide on how to setup your own crypto-currency mining pool. This guide is going over how to setup an Monero mining pool . This is meant to setup a mining pool for a SINGLE CRYPTO CURRENCY. This is not a guide for a Multipool!!!!
If you want to see what it looks like before you set it all up, head to the Monero Mining Pool.
For this guide purpose I will be using Monero Crypto Currency .
- VPS with at least 2GB of Ram you can get it from any where like vultr , lenode , digitalocen
- Ubuntu 14.04 x64 or 16.04 x64
- Putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
- WinSCP (http://winscp.net/eng/download.php)
At this point you should have your VPS started, putty up and running and your logged in as root.
I am setting up a 4GB swap, which may be overkill but it’s the most common swap sized used in most guides so ill keep it at that.
dd if=/dev/zero of=/mnt/myswap.swap bs=1M count=4000
Now let’s add it into fstab so it’ll activate at boot.nano /etc/fstab
Add the following line at the end of the file./mnt/myswap.swap none swap sw 0 0
Ctrl+O to save, and Ctrl+X to exit the nano editor.
Now your swap is setup, you can modify the size in the future if you need more or less.
–Install Required Packages
apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev
apt-get install libboost-all-dev git npm nodejs nodejs-legacy libminiupnpc-dev redis-server
apt-get install libdb4.8-dev libdb4.8++-dev
curl -sL https://raw.githubusercontent.com/creationix/nvm/v0.31.0/install.sh -o install_nvm.sh
nvm install 0.10.48
nvm use 0.10.48
nvm alias default 0.10.48
nvm use default
Monero Daemon Setup (Wallet)
Now let’s setup the coin daemon, I will be using monero.
Now boot up putty .
We download a prebuilt version Monero from there offilcail site here:
tar -xjvf monero-linux-x64-v0.11.0.0.tar.bz2
After issuing “ls” you will see many files are in the directory. you need to start demon now so that it will start sync to blockchain network./monerod
You can see demon is starting and you can see that it started syncing with network . Depend on your vps network speed it will take some time to fully sync .
** On the other hand we can do this sync process faster by using this command so what ever you like you can do it
-- Fastest way to synchronize the daemon
The fastest way to achieve this, is to download the current blockchain and import it into the daemon.
First download it;
wget -c --progress=bar https://downloads.getmonero.org/blockchain.raw
If it fails half-way, just re-run it. The above command will continue where it left off.
Finally import it into the daemon by running;
./monero-blockchain-import --verify 0 --input-file ./blockchain.raw
Do remember though, run with
--verify 0 only from a trusted source like above.
When it finishes u can safely remove the *.raw file;
rm -rf ./blockchain.raw
Now we need to verify and link to moneno network to current state./monerod
You can see all list of detail and showing that it connect to network success message ..
you need to use exit command so that it will save the sync done otherwise you have to again do the sync process
Finally start the monero daemon, which most likely, u will want running in detached/background mode;
Mining Pool Setup
We will use node-cryptonote-pool to setup the pool and front end site.
- Downloading and Installing
Clone the repository and run
npm update for all the dependencies to be installed:
git clone https://github.com/zone117x/node-cryptonote-pool.git pool
Once the above process done we need to copy the config_example.json to active configuration to so your pool start workingcp config_example.json config.json
This will copy all default config file data to active config file “ config.json ”
Warning for Cyrptonote coins other than Monero: this software may or may not work with any given cryptonote coin. Be wary of altcoins that change the number of minimum coin units because you will have to reconfigure several config values to account for those changes. Unless you’re offering a bounty reward – do not open an issue asking for help getting a coin other than Monero working with this software.
Now start up the wincp and put your root login detail to start up once done head over to
/root/pool folder and right click on config.json and edit now you can see all config detail as per below mention and you can edit as per your need .
Explanation for each field:
/* Used for storage in redis so multiple coins can share the same redis instance. */
/* Used for front-end display */
/* Specifies the level of log output verbosity. This level and anything
more severe will be logged. Options are: info, warn, or error. */
/* Directory where to write log files. */
/* How often (in seconds) to append/flush data to the log files. */
/* Gives console output useful colors. If you direct that output to a log file
then disable this feature to avoid nasty characters in the file. */
/* Modular Pool Server */
/* Set to “auto” by default which will spawn one process/fork/worker for each CPU
core in your system. Each of these workers will run a separate instance of your
pool(s), and the kernel will load balance miners using these forks. Optionally,
the ‘forks’ field can be a number for how many forks will be spawned. */
/* Address where block rewards go, and miner payments come from. */
/* Poll RPC daemons for new blocks every this many milliseconds. */
/* How many seconds until we consider a miner disconnected. */
“port”: 3333, //Port for mining apps to connect to
“difficulty”: 100, //Initial difficulty miners are set to
“desc”: “Low end hardware” //Description of port
“desc”: “Mid range hardware”
“desc”: “High end hardware”
/* Variable difficulty is a feature that will automatically adjust difficulty for
individual miners based on their hashrate in order to lower networking and CPU
“minDiff”: 2, //Minimum difficulty
“targetTime”: 100, //Try to get 1 share per this many seconds
“retargetTime”: 30, //Check to see if we should retarget every this many seconds
“variancePercent”: 30, //Allow time to very this % from target without retargeting
“maxJump”: 100 //Limit diff percent increase/decrease in a single retargetting
/* Feature to trust share difficulties from miners which can
significantly reduce CPU load. */
“min”: 10, //Minimum percent probability for share hashing
“stepDown”: 3, //Increase trust probability % this much with each valid share
“threshold”: 10, //Amount of valid shares required before trusting begins
“penalty”: 30 //Upon breaking trust require this many valid share before trusting
/* If under low-diff share attack we can ban their IP to reduce system/network load. */
“time”: 600, //How many seconds to ban worker for
“invalidPercent”: 25, //What percent of invalid shares triggers ban
“checkThreshold”: 30 //Perform check when this many shares have been submitted
/* [Warning: several reports of this feature being broken. Contributions to fix this are welcome.]
Slush Mining is a reward calculation technique which disincentivizes pool hopping and rewards
users to mine with the pool steadily: Values of each share decrease in time – younger shares
are valued higher than older shares.
More about it here: https://mining.bitcoin.cz/help/#!/manual/rewards */
“enabled”: false, //Enables slush mining. Recommended for pools catering to professional miners
“weight”: 120, //defines how fast value assigned to a share declines in time
“lastBlockCheckRate”: 1 //How often the pool checks for the timestamp of the last block. Lower numbers increase load for the Redis db, but make the share value more precise.
/* Module that sends payments to miners according to their submitted shares. */
“interval”: 600, //how often to run in seconds
“maxAddresses”: 50, //split up payments if sending to more than this many addresses
“mixin”: 3, //number of transactions yours is indistinguishable from
“transferFee”: 5000000000, //fee to pay for each transaction
“minPayment”: 100000000000, //miner balance required before sending payment
“denomination”: 100000000000 //truncate to this precision and store remainder
/* Module that monitors the submitted block maturities and manages rounds. Confirmed
blocks mark the end of a round where workers’ balances are increased in proportion
to their shares. */
“interval”: 30, //how often to check block statuses in seconds
/* Block depth required for a block to unlocked/mature. Found in daemon source as
the variable CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW */
“poolFee”: 1.8, //1.8% pool fee (2% total fee total including donations)
“devDonation”: 0.1, //0.1% donation to send to pool dev – only works with Monero
“coreDevDonation”: 0.1 //0.1% donation to send to core devs – only works with Monero
/* AJAX API used for front-end website. */
“hashrateWindow”: 600, //how many second worth of shares used to estimate hash rate
“updateInterval”: 3, //gather stats and broadcast every this many seconds
“blocks”: 30, //amount of blocks to send at a time
“payments”: 30, //amount of payments to send at a time
“password”: “test” //password required for admin stats
/* Coin daemon connection details. */
/* Wallet daemon connection details. */
/* Redis connection into. */
“auth”: null //If set, client will run redis auth command on connect. Use for remote db
3. [Optional] Configure cryptonote-easy-miner for your pool
Your miners that are Windows users can use cryptonote-easy-miner which will automatically generate their wallet address and stratup multiple threads of simpleminer. You can download it and edit the config.ini file to point to your own pool. Inside the easyminer folder, edit config.init to point to your pool details
Rezip and upload to your server or a file host. Then change the easyminerDownload link in your config.json file to point to your zip file.
4. Start the pool
This will show all running and start accepting share for your pool
we need to now install forever so that this pool will remain running even on close of sshnpm install forever -g
once installation done final start the poolforever start init.js
Example screenshot of running the pool in single module mode with tmux.
5. Host the front end
Simply host the contents of the website_example directory on file server capable of serving simple static files.
Edit the variables in the website_example/config.js file to use your pool’s specific configuration. Variable explanations:
/* Must point to the API setup in your config.json file. */
var api = “http://poolhost:8117”;
/* Minimum units in a single coin, for Bytecoin its 100000000. */
var coinUnits = 1000000000000;
/* Pool server host to instruct your miners to point to. */
var poolHost = “cryppit.com”;
/* IRC Server and room used for embedded KiwiIRC chat. */
var irc = “irc.freenode.net/#monero”;
/* Contact email address. */
var email = “[email protected]”;
/* Market stat display params from https://www.cryptonator.com/widget */
var cryptonatorWidget = [“XMR-BTC”, “XMR-USD”, “XMR-EUR”, “XMR-GBP”];
/* Download link to cryptonote-easy-miner for Windows users. */
var easyminerDownload = “https://github.com/zone117x/cryptonote-easy-miner/releases/”;
/* Used for front-end block links. For other coins it can be changed, for example with
Bytecoin you can use “https://minergate.com/blockchain/bcn/block/”. */
var blockchainExplorer = “http://monerochain.info/block/”;
/* Used by front-end transaction links. Change for other coins. */
var transactionExplorer = “http://monerochain.info/tx/”;
6. Customize your website
The following files are included so that you can customize your pool website without having to make significant changes to index.html or other front-end files thus reducing the difficulty of merging updates with your own changes:
- custom.css for creating your own pool style
- custom.js for changing the functionality of your pool website
Then simply serve the files via nginx, Apache, Google Drive, or anything that can host static content.
Congratulations You have now your own Monero Mining Pool Ready to Start
If you liked this guide, please donate to me as well!