Setup Ethereum Mining Pool using open source ethereum pool

This a step by step guide on how to setup your own Ethereum Mining Pool. This guide is going over how to setup an ethereum pool using open source ethereum pool software. 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 http://myetherpool.org/ what to see more pool check this list

For this guide purpose we I will be using Ethereum Crypto Currency .

Requirements

 

Setup

At this point you should have your VPS started, putty up and running and your logged in as root.

 

Update Ubuntu

[junkie-hightlights color=”grey”] apt-get update [/junkie-hightlights]
[junkie-hightlights color=”grey”]apt-get dist-upgrade[/junkie-hightlights]

Setup SWAP

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.

 

[junkie-hightlights color=”grey”]dd if=/dev/zero of=/mnt/myswap.swap bs=1M count=4000[/junkie-hightlights]
[junkie-hightlights color=”grey”]mkswap /mnt/myswap.swap[/junkie-hightlights]
[junkie-hightlights color=”grey”]swapon /mnt/myswap.swap[/junkie-hightlights]

 

Now let’s add it into fstab so it’ll activate at boot.

[junkie-hightlights color=”grey”]nano /etc/fstab[/junkie-hightlights]

Add the following line at the end of the file.

[junkie-hightlights color=”grey”]/mnt/myswap.swap none swap sw 0 0[/junkie-hightlights]

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

 

[junkie-hightlights color=”grey”]apt-get install git[/junkie-hightlights]
[junkie-hightlights color=”grey”]apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev[/junkie-hightlights]
[junkie-hightlights color=”grey”]apt-get install libboost-all-dev git npm nodejs nodejs-legacy libminiupnpc-dev redis-server[/junkie-hightlights]
[junkie-hightlights color=”grey”]apt-get update[/junkie-hightlights]
[junkie-hightlights color=”grey”]apt-get install libdb4.8-dev libdb4.8++-dev[/junkie-hightlights]
[junkie-hightlights color=”grey”]apt-get install golang[/junkie-hightlights]

 

Installing nginx

 

[junkie-hightlights color=”grey”]sudo apt-get update[/junkie-hightlights]
[junkie-hightlights color=”grey”]sudo apt-get install nginx[/junkie-hightlights]

Ethereum Daemon Setup (Wallet)

 

Now let’s setup the coin daemon, I will be using Ethereum.

We can install in 2 way her is guide ..

First>> Installing from PPA

[junkie-hightlights color=”grey”]sudo apt-get install software-properties-common[/junkie-hightlights]
[junkie-hightlights color=”grey”]sudo add-apt-repository -y ppa:ethereum/ethereum[/junkie-hightlights]
[junkie-hightlights color=”grey”]sudo apt-get update[/junkie-hightlights]
[junkie-hightlights color=”grey”]sudo apt-get install ethereum[/junkie-hightlights]

If you want to stay on the bleeding edge, install the ethereum-unstable package instead.

After installing, run geth account new to create an account on your node.

You should now be able to run geth and connect to the network.

Make sure to check the different options and commands with geth --help

You can alternatively install only the geth CLI with apt-get install geth if you don’t want to install the other utilities (bootnode, evm, disasm, rlpdump, ethtest).

Second>> Building from source

Clone the repository to a directory of your choosing:

[junkie-hightlights color=”grey”]git clone https://github.com/ethereum/go-ethereum[/junkie-hightlights]

Install latest distribution of Golang (v1.7) if you don’t have it already:

Building geth requires Go and C compilers to be installed:

[junkie-hightlights color=”grey”]sudo apt-get install -y build-essential golang[/junkie-hightlights]

Finally, build the geth program using the following command.

[junkie-hightlights color=”grey”]cd go-ethereum[/junkie-hightlights]
[junkie-hightlights color=”grey”]make geth[/junkie-hightlights]

You can now run build/bin/geth to start your node.

Mining Pool Setup

 

Clone & compile:

[junkie-hightlights color=”grey”]git config --global http.https://gopkg.in.followRedirects true[/junkie-hightlights]
[junkie-hightlights color=”grey”]git clone https://github.com/sammy007/open-ethereum-pool.git[/junkie-hightlights]
[junkie-hightlights color=”grey”]cd open-ethereum-pool[/junkie-hightlights]
[junkie-hightlights color=”grey”]make[/junkie-hightlights]

Also Read  Eobot cloud mining service review

Running Pool

 

[junkie-hightlights color=”grey”]./build/bin/open-ethereum-pool config.json[/junkie-hightlights]

You can use Ubuntu upstart – check for sample config in upstart.conf.

Building Frontend

 

The frontend is a single-page Ember.js application that polls the pool API to render miner stats.

[junkie-hightlights color=”grey”]cd www[/junkie-hightlights]

Change ApiUrl: '//example.net/' in www/config/environment.js to match your domain name. Also don’t forget to adjust other options.

[junkie-hightlights color=”grey”]npm install -g ember-cli@2.9.1[/junkie-hightlights]
[junkie-hightlights color=”grey”]npm install -g bower[/junkie-hightlights]
[junkie-hightlights color=”grey”]npm install[/junkie-hightlights]
[junkie-hightlights color=”grey”]bower install[/junkie-hightlights]
[junkie-hightlights color=”grey”]./build.sh[/junkie-hightlights]

Configure nginx to serve API on /api subdirectory. Configure nginx to serve www/dist as static website.

Serving API using nginx

Create an upstream for API:

upstream api {
server 127.0.0.1:8080;
}

and add this setting after location /:

location /api {
proxy_pass http://api;
}

Customization

You can customize the layout using built-in web server with live reload:

[junkie-hightlights color=”grey”]ember server --port 8082 --environment development[/junkie-hightlights]

Don’t use built-in web server in production.

Check out www/app/templates directory and edit these templates in order to customise the frontend.

Configuration

 

Configuration is actually simple, just read it twice and think twice before changing defaults.

Don’t copy config directly from this manual. Use the example config from the package, otherwise you will get errors on start because of JSON comments.

{
// Set to the number of CPU cores of your server
“threads”: 2,
// Prefix for keys in redis store
“coin”: “eth”,
// Give unique name to each instance
“name”: “main”,

“proxy”: {
“enabled”: true,

// Bind HTTP mining endpoint to this IP:PORT
“listen”: “0.0.0.0:8888”,

// Allow only this header and body size of HTTP request from miners
“limitHeadersSize”: 1024,
“limitBodySize”: 256,

/* Set to true if you are behind CloudFlare (not recommended) or behind http-reverse
proxy to enable IP detection from X-Forwarded-For header.
Advanced users only. It’s tricky to make it right and secure.
*/
“behindReverseProxy”: false,

// Stratum mining endpoint
“stratum”: {
“enabled”: true,
// Bind stratum mining socket to this IP:PORT
“listen”: “0.0.0.0:8008”,
“timeout”: “120s”,
“maxConn”: 8192
},

// Try to get new job from geth in this interval
“blockRefreshInterval”: “120ms”,
“stateUpdateInterval”: “3s”,
// Require this share difficulty from miners
“difficulty”: 2000000000,

/* Reply error to miner instead of job if redis is unavailable.
Should save electricity to miners if pool is sick and they didn’t set up failovers.
*/
“healthCheck”: true,
// Mark pool sick after this number of redis failures.
“maxFails”: 100,
// TTL for workers stats, usually should be equal to large hashrate window from API section
“hashrateExpiration”: “3h”,

“policy”: {
“workers”: 8,
“resetInterval”: “60m”,
“refreshInterval”: “1m”,

“banning”: {
“enabled”: false,
/* Name of ipset for banning.
Check http://ipset.netfilter.org/ documentation.
*/
“ipset”: “blacklist”,
// Remove ban after this amount of time
“timeout”: 1800,
// Percent of invalid shares from all shares to ban miner
“invalidPercent”: 30,
// Check after after miner submitted this number of shares
“checkThreshold”: 30,
// Bad miner after this number of malformed requests
“malformedLimit”: 5
},
// Connection rate limit
“limits”: {
“enabled”: false,
// Number of initial connections
“limit”: 30,
“grace”: “5m”,
// Increase allowed number of connections on each valid share
“limitJump”: 10
}
}
},

// Provides JSON data for frontend which is static website
“api”: {
“enabled”: true,
“listen”: “0.0.0.0:8080”,
// Collect miners stats (hashrate, …) in this interval
“statsCollectInterval”: “5s”,
// Purge stale stats interval
“purgeInterval”: “10m”,
// Fast hashrate estimation window for each miner from it’s shares
“hashrateWindow”: “30m”,
// Long and precise hashrate from shares, 3h is cool, keep it
“hashrateLargeWindow”: “3h”,
// Collect stats for shares/diff ratio for this number of blocks
“luckWindow”: [64, 128, 256],
// Max number of payments to display in frontend
“payments”: 50,
// Max numbers of blocks to display in frontend
“blocks”: 50,

/* If you are running API node on a different server where this module
is reading data from redis writeable slave, you must run an api instance with this option enabled in order to purge hashrate stats from main redis node.
Only redis writeable slave will work properly if you are distributing using redis slaves.
Very advanced. Usually all modules should share same redis instance.
*/
“purgeOnly”: false
},

// Check health of each geth node in this interval
“upstreamCheckInterval”: “5s”,

/* List of geth nodes to poll for new jobs. Pool will try to get work from
first alive one and check in background for failed to back up.
Current block template of the pool is always cached in RAM indeed.
*/
“upstream”: [
{
“name”: “main”,
“url”: “http://127.0.0.1:8545”,
“timeout”: “10s”
},
{
“name”: “backup”,
“url”: “http://127.0.0.2:8545”,
“timeout”: “10s”
}
],

// This is standard redis connection options
“redis”: {
// Where your redis instance is listening for commands
“endpoint”: “127.0.0.1:6379”,
“poolSize”: 10,
“database”: 0,
“password”: “”
},

// This module periodically remits ether to miners
“unlocker”: {
“enabled”: false,
// Pool fee percentage
“poolFee”: 1.0,
// Pool fees beneficiary address (leave it blank to disable fee withdrawals)
“poolFeeAddress”: “”,
// Donate 10% from pool fees to developers
“donate”: true,
// Unlock only if this number of blocks mined back
“depth”: 120,
// Simply don’t touch this option
“immatureDepth”: 20,
// Keep mined transaction fees as pool fees
“keepTxFees”: false,
// Run unlocker in this interval
“interval”: “10m”,
// Geth instance node rpc endpoint for unlocking blocks
“daemon”: “http://127.0.0.1:8545”,
// Rise error if can’t reach geth in this amount of time
“timeout”: “10s”
},

// Pay out miners using this module
“payouts”: {
“enabled”: false,
// Require minimum number of peers on node
“requirePeers”: 25,
// Run payouts in this interval
“interval”: “12h”,
// Geth instance node rpc endpoint for payouts processing
“daemon”: “http://127.0.0.1:8545”,
// Rise error if can’t reach geth in this amount of time
“timeout”: “10s”,
// Address with pool balance
“address”: “0x0”,
// Let geth to determine gas and gasPrice
“autoGas”: true,
// Gas amount and price for payout tx (advanced users only)
“gas”: “21000”,
“gasPrice”: “50000000000”,
// Send payment only if miner’s balance is >= 0.5 Ether
“threshold”: 500000000,
// Perform BGSAVE on Redis after successful payouts session
“bgsave”: false
}
}

If you are distributing your pool deployment to several servers or processes, create several configs and disable unneeded modules on each server. (Advanced users)

Also Read  Review of cloudmining at Topmine.io

I recommend this deployment strategy:

  1. Mining instance – 1x (it depends, you can run one node for EU, one for US, one for Asia)
  2. Unlocker and payouts instance – 1x each (strict!)
  3. API instance – 1x

 

Congratulations You have now your own Mining Pool Ready to Start

If you liked this guide, please donate to me as well!
BTC: 18xRnsa828YALPgbvjRXQuQ63QqikPbKxq

Leave a Comment