High performance Node.js (with native C addons) mining pool for CryptoNote based coins such as Bytecoin, DuckNote, Monero, QuazarCoin, Boolberry, Dashcoin, etc.. Comes with lightweight example front-end script which uses the pool's AJAX API.
- Features
- Community Support
- Pools Using This Software
- Usage
- Setting up Testnet
- JSON-RPC Commands from CLI
- Monitoring Your Pool
- Donations
- Credits
- License
- 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
- Support for configuration using tls (https) in pool code to allowing the same for web frontend
- Multiple modules can be started on command line instead of one or none.
- Onishin's keepalive function https://github.com/perl5577/cpuminer-multi/commit/0c8aedb
- 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 support is not currently working after fixes to get node modules to work after Mar 23, 2016 fork.
- MonetaVerde support not tested since changes for monero fork
- [NEW]Set miner's name and fixed difficulty on miner client by passing "address" param with ".[name]+[difficulty]" postfix. eg: 4BCe....CgvCDm.miner01+2000
- Prevent "transaction is too big" error with "payments.maxTransactionAmount" option
- [NEW]Add Worker stats pannel
- http://xmr.poolto.be run by PCFil
- http://xmr.cncoin.farm run by clintar
- Coin daemon(s) (find the coin's repo and build latest version from source)
- 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
- For Ubuntu:
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.
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 redis-server libboost1.55-all-dev nodejs-dev nodejs-legacy npm cmake libssl-devClone the repository and run npm update for all the dependencies to be installed:
git clone https://github.com/dannyzml/cryptonote-xmr-pool.git pool
cd pool
npm updateExplanation for each field:
{
"coin": "monero",
"symbol": "XMR",
"coinUnits": 1000000000000,
"coinDifficultyTarget": 120,
"logging": {
"files": {
"level": "info",
"directory": "logs",
"flushInterval": 5
},
"console": {
"level": "info",
"colors": true
}
},
"poolServer": {
"enabled": true,
"clusterForks": "auto",
"poolAddress": "44SnRTKJAz1fL4cUP2WWsnHZXLshVV2C7K35fJNNVKi59jzoy56Bw9KbVxnsccfQfm8ZMnshdisF46hFVnTuHFFCJ5wrLfV",
"blockRefreshInterval": 1000,
"minerTimeout": 900,
"ports": [
{
"port": 3333,
"difficulty": 100,
"desc": "Low end hardware"
},
{
"port": 5555,
"difficulty": 1000,
"desc": "Mid range hardware"
},
{
"port": 7777,
"difficulty": 2000,
"desc": "High end hardware"
},
{
"port": 8888,
"difficulty": 10000,
"desc": "Hidden port",
"hidden": true
}
],
"varDiff": {
"minDiff": 2,
"maxDiff": 50000,
"targetTime": 100,
"retargetTime": 60,
"variancePercent": 30,
"maxJump": 10
},
"fixedDiff": {
"enabled": true,
"addressSeparator": "+",
"workerSeparator": "."
},
"shareTrust": {
"enabled": true,
"min": 10,
"stepDown": 3,
"threshold": 10,
"penalty": 30
},
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 25,
"checkThreshold": 30
}
},
"payments": {
"enabled": true,
"interval": 600,
"maxAddresses": 50,
"mixin": 3,
"transferFee": 5000000000,
"minPayment": 1000000000000,
"maxTransactionAmount": 0,
"denomination": 100000000000
},
"blockUnlocker": {
"enabled": true,
"interval": 30,
"depth": 60,
"poolFee": 2,
"devDonation": 0.1,
"coreDevDonation": 0.1,
"extraFeaturesDevDonation":0.1
},
"api": {
"enabled": true,
"hashrateWindow": 600,
"updateInterval": 30,
"port": 8117,
"blocks": 30,
"payments": 30,
"ssl": false,
"sslport": 8119,
"sslcert": "./certs/cert.pem",
"sslkey": "./certs/privkey.pem",
"sslca": "./certs/chain.pem",
"password": "770108"
},
"daemon": {
"host": "127.0.0.1",
"port": 18081
},
"wallet": {
"host": "127.0.0.1",
"port": 8082
},
"redis": {
"host": "127.0.0.1",
"port": 6379
},
"monitoring": {
"daemon": {
"checkInterval": 60,
"rpcMethod": "getblockcount"
},
"wallet": {
"checkInterval": 60,
"rpcMethod": "getbalance"
}
},
"charts": {
"pool": {
"hashrate": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"workers": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"difficulty": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"price": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"profit": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
}
},
"user": {
"hashrate": {
"enabled": true,
"updateInterval": 180,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"payments": {
"enabled": true
}
}
}
}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
pool_host=example.com
pool_port=5555Rezip 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.
node init.jsThe 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.jsonThis software contains four distinct modules:
pool- Which opens ports for miners to connect and processes sharesapi- Used by the website to display network, pool and miners' dataunlocker- Processes block candidates and increases miners' balances when blocks are unlockedpayments- 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=apiExample screenshot of running the pool in single module mode with tmux.
Simply host the contents of the website directory on file server capable of serving simple static files.
Edit the variables in the website/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/#ducknote";
/* Contact email address. */
var email = "[email protected]";
/* Market stat display params from https://www.cryptonator.com/widget */
var cryptonatorWidget = ["XDN-BTC", "XDN-USD", "XDN-EUR", "XDN-CNY"];
/* 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";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.cssfor creating your own pool stylecustom.jsfor changing the functionality of your pool website
Then simply serve the files via nginx, Apache, Google Drive, or anything that can host static content.
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 pullto get the latest code. - Remove the dependencies by deleting the
node_modulesdirectory withrm -r node_modules. - Run
npm updateto force updating/reinstalling of the dependencies. - Compare your
config.jsonto 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.
Monero does have a testnet. Call daemon and simplewallet with --tesnet to connect to it. Downloading the testnet blockchain may still take a while to start usint testnet, so you can use this excellent tutorial http://moneroexamples.github.io/private-testnet/ to set up a private testnet. Should work with other coins, too, but below are original testnet instructions by server43 for reference, too.
For cryptonote based coins that don't have a testnet mode (yet), you can effectively create a testnet with the following steps:
- Open
/src/p2p/net_node.inland remove lines withADD_HARDCODED_SEED_NODEto prevent it from connecting to mainnet (Monero example: http://git.io/0a12_Q) - Build the coin from source
- 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
./coind --p2p-bind-port 28080 --allow-local-ip - Run second instance with
./coind --p2p-bind-port 5011 --rpc-bind-port 5010 --add-peer 0.0.0.0:28080 --allow-local-ip
- Run first instance with
- 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
Credit to surfer43 for these instructions
Documentation for JSON-RPC commands can be found here:
- Daemon https://wiki.bytecoin.org/wiki/Daemon_JSON_RPC_API
- Wallet https://wiki.bytecoin.org/wiki/Wallet_JSON_RPC_API
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:18081/json_rpc -d '{"method":"getblockheaderbyheight","params":{"height":100}}'- 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
-
MRO:
44SnRTKJAz1fL4cUP2WWsnHZXLshVV2C7K35fJNNVKi59jzoy56Bw9KbVxnsccfQfm8ZMnshdisF46hFVnTuHFFCJ5wrLfVCredits === -
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] (https://github.com/fancoder) Initial cryptonote-universal-pool creator
-
BTC:
1667jMt7NTZDaC8WXAxtMYBR8DPWCVoU4d- -
MRO:
48Y4SoUJM5L3YXBEfNQ8bFNsvTNsqcH5Rgq8RF7BwpgvTBj2xr7CmWVanaw7L4U9MnZ4AG7U6Pn1pBhfQhFyFZ1rL1efL8z -
[clintar] (https://github.com/clintar) Updates to support nodejs >0.10 and continuing updates License
Released under the GNU General Public License v2