bittorium-pool

Formerly known as cryptonote-forknote-pool, forked from Forknote Project.

High performance Node.js (with native C addons) mining pool for Cryptonote based coins, created with the Forknote software such as Bytecoin, Dashcoin, etc..

Comes with lightweight example front-end script which uses the pool's AJAX API.

Basic features

TCP (stratum-like) protocol for server-push based jobs
- Compared to old HTTP protocol, this has a higher hash rate, lower network/CPU server load, lower orphan block percent, and less error prone
IP banning to prevent low-diff share attacks
Socket flooding detection
Payment processing
- Splintered transactions to deal with max transaction size
- Minimum payment threshold before balance will be paid out
- Minimum denomination for truncating payment amount precision to reduce size/complexity of block transactions
Detailed logging
Ability to configure multiple ports - each with their own difficulty
Variable difficulty / share limiter
Share trust algorithm to reduce share validation hashing CPU load
Clustering for vertical scaling
Modular components for horizontal scaling (pool server, database, stats/API, payment processing, front-end)
Live stats API (using AJAX long polling with CORS)
- Currency network/block difficulty
- Current block height
- Network hashrate
- Pool hashrate
- Each miners' individual stats (hashrate, shares submitted, pending balance, total paid, etc)
- Blocks found (pending, confirmed, and orphaned)
An easily extendable, responsive, light-weight front-end using API to display data

Extra features

Admin panel
- Aggregated pool statistics
- Coin daemon & wallet RPC services stability monitoring
- Log files data access
- Users list with detailed statistics
Historic charts of pool's hashrate and miners count, coin difficulty, rates and coin profitability
Historic charts of users's hashrate and payments
Miner login(wallet address) validation
Five configurable CSS themes
Universal blocks and transactions explorer based on chainradar.com
FantomCoin & MonetaVerde support
Set fixed difficulty on miner client by passing "address" param with ".[difficulty]" postfix
Prevent "transaction is too big" error with "payments.maxTransactionAmount" option

Community / Support

Pools Using This Software

Usage

Requirements

Bittorium daemon
walletd
Node.js v0.10+ (follow these installation instructions)
Redis key-value store v2.6+ (follow these instructions)
libssl required for the node-multi-hashing module
- For Ubuntu: sudo apt-get install libssl-dev

Seriously

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.

Easy install on Ubuntu 14 LTS

Installing pool on different Linux distributives is different because it depends on system default components and versions. For now the easiest way to install pool is to use Ubuntu 14 LTS. Thus, all you had to do in order to prepare Ubunty 14 for pool installation is to run:

sudo apt-get install git build-essential redis-server libboost1.55-all-dev nodejs-dev nodejs-legacy npm cmake libssl-dev node-gyp
sudo ln -s /usr/bin/nodejs /usr/bin/node

1) Downloading & Installing

Clone the repository and run npm update for all the dependencies to be installed:

git clone https://github.com/mtl1979/bittorium-pool pool
cd pool
npm config set strict-ssl false
npm update

2) Configuration

Explanation for each field:

/* Used for storage in redis so multiple coins can share the same redis instance. */
"coin": "bittorium",

/* Used for front-end display */
"symbol": "BTOR",

/* Minimum units in a single coin, see COIN constant in DAEMON_CODE/src/cryptonote_config.h */
"coinUnits": 100,

/* Coin network time to mine one block, see DIFFICULTY_TARGET constant in DAEMON_CODE/src/cryptonote_config.h */
"coinDifficultyTarget": 240,

"logging": {

    "files": {

        /* Specifies the level of log output verbosity. This level and anything
           more severe will be logged. Options are: info, warn, or error. */
        "level": "info",

        /* Directory where to write log files. */
        "directory": "logs",

        /* How often (in seconds) to append/flush data to the log files. */
        "flushInterval": 5
    },

    "console": {
        "level": "info",
        /* 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. */
        "colors": true
    }
},

/* Modular Pool Server */
"poolServer": {
    "enabled": true,

    /* 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. */
    "clusterForks": "auto",

    /* Address where block rewards go, and miner payments come from. */
    "poolAddress": "bTXPouErxAPNQ9Ajwtn7NE589BiU7vb8y9rRow3vZYerBVA9AL2RGb498XgkXwYpUMLagvWSYfHEmW3X2LqCxd7214jA6JuyA"

    /* Poll RPC daemons for new blocks every this many milliseconds. */
    "blockRefreshInterval": 1000,

    /* How many seconds until we consider a miner disconnected. */
    "minerTimeout": 900,

    "ports": [
        {
            "port": 3333, //Port for mining apps to connect to
            "difficulty": 100, //Initial difficulty miners are set to
            "desc": "Low end hardware" //Description of port
        },
        {
            "port": 5555,
            "difficulty": 2000,
            "desc": "Mid range hardware"
        },
        {
            "port": 7777,
            "difficulty": 10000,
            "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
       overhead. */
    "varDiff": {
        "minDiff": 2, //Minimum difficulty
        "maxDiff": 100000,
        "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 retargeting
    },

    /* Set difficulty on miner client side by passing <address> param with .<difficulty> postfix
       minerd -u D3z2DDWygoZU4NniCNa4oMjjKi45dC2KHUWUyD1RZ1pfgnRgcHdfLVQgh5gmRv4jwEjCX5LoLERAf5PbjLS43Rkd8vFUM1m.5000 */
    "fixedDiff": {
        "enabled": true,
        "separator": ".", // character separator between <address> and <difficulty>
    },

    /* Feature to trust share difficulties from miners which can
       significantly reduce CPU load. */
    "shareTrust": {
        "enabled": true,
        "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. */
    "banning": {
        "enabled": true,
        "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
    },
    /* 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 */
    /* There is some bugs with enabled slushMining. Use with '"enabled": false' only. */

    "slushMining": {
        "enabled": false, // 'true' 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. */
"payments": {
    "enabled": true,
    "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": 1, //fee to pay for each transaction
    "minPayment": 1000, //miner balance required before sending payment
    "maxTransactionAmount": 0, //split transactions by this amount(to prevent "too big transaction" error)
    "denomination": 100 //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. */
"blockUnlocker": {
    "enabled": true,
    "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 */
    "depth": 60,
    "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 - works with Bytecoin, Monero, Dashcoin, QuarazCoin, Fantoncoin, AEON and OneEvilCoin
},

/* AJAX API used for front-end website. */
"api": {
    "enabled": true,
    "hashrateWindow": 600, //how many second worth of shares used to estimate hash rate
    "updateInterval": 3, //gather stats and broadcast every this many seconds
    "port": 8117,
    "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. */
"daemon": {
    "host": "127.0.0.1",
    "port": 34916
},

/* Wallet daemon connection details. */
"wallet": {
    "host": "127.0.0.1",
    "port": 8070,
    "password": "<replace with rpc password>"
},

/* Redis connection into. */
"redis": {
    "host": "127.0.0.1",
    "port": 6379
}

/* Monitoring RPC services. Statistics will be displayed in Admin panel */
"monitoring": {
    "daemon": {
        "checkInterval": 60, //interval of sending rpcMethod request
        "rpcMethod": "getblockcount" //RPC method name
    },
    "wallet": {
        "checkInterval": 60,
        "rpcMethod": "getBalance"
    }

/* Collect pool statistics to display in frontend charts  */
"charts": {
    "pool": {
        "hashrate": {
            "enabled": true, //enable data collection and chart displaying in frontend
            "updateInterval": 60, //how often to get current value
            "stepInterval": 1800, //chart step interval calculated as average of all updated values
            "maximumPeriod": 86400 //chart maximum periods (chart points number = maximumPeriod / stepInterval = 48)
        },
        "workers": {
            "enabled": true,
            "updateInterval": 60,
            "stepInterval": 1800, //chart step interval calculated as maximum of all updated values
            "maximumPeriod": 86400
        },
        "difficulty": {
            "enabled": true,
            "updateInterval": 1800,
            "stepInterval": 10800,
            "maximumPeriod": 604800
        },
        "price": { //USD price of one currency coin received from cryptonator.com/api
            "enabled": true,
            "updateInterval": 1800,
            "stepInterval": 10800,
            "maximumPeriod": 604800
        },
        "profit": { //Reward * Rate / Difficulty
            "enabled": true,
            "updateInterval": 1800,
            "stepInterval": 10800,
            "maximumPeriod": 604800
        }
    },
    "user": { //chart data displayed in user stats block
        "hashrate": {
            "enabled": true,
            "updateInterval": 180,
            "stepInterval": 1800,
            "maximumPeriod": 86400
        },
        "payments": { //payment chart uses all user payments data stored in DB
            "enabled": true
        }
    }

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 start up 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

pool_host=example.com
pool_port=5555

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

node init.js

The file config.json is used by default but a file can be specified using the -config=file command argument, for example:

node init.js -config=config_backup.json

This software contains four distinct modules:

pool - Which opens ports for miners to connect and processes shares
api - Used by the website to display network, pool and miners' data
unlocker - Processes block candidates and increases miners' balances when blocks are unlocked
payments - Sends out payments to miners according to their balances stored in redis

By default, running the init.js script will start up all four modules. You can optionally have the script start only start a specific module by using the -module=name command argument, for example:

node init.js -module=api

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";

/* Pool server host to instruct your miners to point to.  */
var poolHost = "poolhost.com";

/* IRC Server and room used for embedded KiwiIRC chat. */
var irc = "irc.freenode.net/#forknote";

/* Contact email address. */
var email = "[email protected]";

/* Market stat display params from https://www.cryptonator.com/widget */
var cryptonatorWidget = ["DSH-BTC", "DSH-USD", "DSH-EUR"];

/* 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. */
var blockchainExplorer = "http://chainradar.com/{symbol}/block/{id}";

/* Used by front-end transaction links. */
var transactionExplorer = "http://chainradar.com/{symbol}/transaction/{id}";

/* Any custom CSS theme for pool frontend */
var themeCss = "themes/default-theme.css";

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.

Upgrading

When updating to the latest code its important to not only git pull the latest from this repo, but to also update the Node.js modules, and any config files that may have been changed.

Inside your pool directory (where the init.js script is) do git pull to get the latest code.
Remove the dependencies 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 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.

Setting up Testnet

You can create a testnet with the following steps:

You now need to run two instance of the daemon and connect them to each other (without a connection to another instance the daemon will not accept RPC requests)
- Run first instance with ./Bittoriumd --testnet --p2p-bind-port 28080 --allow-local-ip
- Run second instance with ./Bittoriumd --testnet --p2p-bind-port 5011 --rpc-bind-port 5010 --add-peer 0.0.0.0:28080 --allow-local-ip
You should now have a local testnet setup. The ports can be changes as long as the second instance is pointed to the first instance, obviously

JSON-RPC Commands from CLI

Documentation for JSON-RPC commands can be found here:

Curl can be used to use the JSON-RPC commands from command-line. Here is an example of calling getblockheaderbyheight for block 100:

curl 127.0.0.1:39984/json_rpc -d '{"method":"getblockheaderbyheight","params":{"height":100}}'

Monitoring Your Pool

To inspect and make changes to redis I suggest using redis-commander
To monitor server load for CPU, Network, IO, etc - I suggest using New Relic
To keep your pool node script running in background, logging to file, and automatically restarting if it crashes - I suggest using forever

Configuring Blockchain Explorer

You need the latest stable version of Bittoriumd from Bittorium GitHub.

Start the daemon with:

Bittoriumd.exe --enable_blockexplorer --rpc-bind-ip 0.0.0.0 --enable-cors *

or

./Bittoriumd --enable_blockexplorer --rpc-bind-ip 0.0.0.0 --enable-cors "*"

Change the following line in the pool's frontend config.json:

var api_blockexplorer = "http://daemonhost.com:34916";

Credits

mtl1979 - Modifications for PinkstarcoinV2 and Bittorium
leisegang - Modifications for PinkstarcoinV2, Top 10 miners
LucasJones - Co-dev on this project; did tons of debugging for binary structures and fixing them. Pool couldn't have been made without him.
surfer43 - Did lots of testing during development to help figure out bugs and get them fixed
wallet42 - Funded development of payment denominating and min threshold feature
Wolf0 - Helped try to deobfuscate some of the daemon code for getting a bug fixed
Tacotime - helping with figuring out certain problems and lead the bounty for this project's creation
fancoder - See his repo for the changes

Donations

If you want to support development of bittorium-pool, you can send donations using following addresses or set "devDonation" to non-zero in config.json:

BCH: qryfpsnz3v607kupyrvnjgqang7urfj0fsetc3a9mf
BTC: 1D1YBHmFkd4J7bEG6PYfZBLoXtp98hKsfw
ETH: 0xc1d2DDB00c5B110855FAD9E2C7b8157D358b050e
ETN: etnjxvV1JwWJRCdbZETJ4d1NZAH1bmQyBBwfyJsB6cDKDj1U6fXcRnvJhDJZ5QJGG3Cqm3fLTA7ZCABhfa2fyb6P2Fwj1asPy2
ITNS: iz4zpuXFmwVKsKYmHZt2TzHd7BaSuUiep9VxCEBvCgPy3ijAkVb2ZMhVp7shCyrYvmGmcWoByUBJW3NqyAGMD1KX2oTNvZKFT
LTC: MAaio5kmZbzcJ8VGfSwtKQKdho8KK7GsTo
PSTAR: P6ZDs32zWmAgoXE6Caom2L7nNaKRtNjqvFsv6NQp8XzUZsB47V8XRPCG7dzLf59KPMXhyjLpPbSqyWaYpaDNwV121EFsG4Btr
BTOR: bTXPouErxAPNQ9Ajwtn7NE589BiU7vb8y9rRow3vZYerBVA9AL2RGb498XgkXwYpUMLagvWSYfHEmW3X2LqCxd7214jA6JuyA

License

Released under the GNU General Public License v2

http://www.gnu.org/licenses/gpl-2.0.html

Name		Name	Last commit message	Last commit date
Latest commit History 475 Commits
lib		lib
website		website
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
config.json		config.json
init.js		init.js
package.json		package.json
redisBlocksUpgrade.js		redisBlocksUpgrade.js

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

bittorium-pool

Table of Contents

Basic features

Extra features

Community / Support

Pools Using This Software

Usage

Requirements

Seriously

Easy install on Ubuntu 14 LTS

1) Downloading & Installing

2) Configuration

3) [Optional] Configure cryptonote-easy-miner for your pool

4) Start the pool

5) Host the front-end

6) Customize your website

Upgrading

Setting up Testnet

JSON-RPC Commands from CLI

Monitoring Your Pool

Configuring Blockchain Explorer

Credits

Donations

License

About

Releases

Packages

Contributors 23

Languages

License

mtl1979/bittorium-pool

Folders and files

Latest commit

History

Repository files navigation

bittorium-pool

Table of Contents

Basic features

Extra features

Community / Support

Pools Using This Software

Usage

Requirements

Seriously

Easy install on Ubuntu 14 LTS

1) Downloading & Installing

2) Configuration

3) [Optional] Configure cryptonote-easy-miner for your pool

4) Start the pool

5) Host the front-end

6) Customize your website

Upgrading

Setting up Testnet

JSON-RPC Commands from CLI

Monitoring Your Pool

Configuring Blockchain Explorer

Credits

Donations

License

About

Topics

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 23

Languages

Packages