LightBIT - Node Open Mining Portal

This is a YespowerLitb, YesPoWer, Yescrypt-0.5, Lyra2REv2, sha256d and more algo mining pool based off of Node Open Mining Portal.

Donations for development are greatly appreciated!

• ZNY: ZmnBu9jPKvVFL22PcwMHSEuVpTxFeCdvNv
• NUKO: 0xa79bde46faab3c40632604728e9f2165b052581c
• KOTO :k16dV6stRkFtZpFtMTrznqvavRuMfh4PB1R
• SUSU: SeXbMBaax7NgnTEFEMxin5ycXy9r9CDBot
• MONA: mona1qnur6ljkl5pe8w6ql8xfqw4aa38d5xa9q68dxll
• BELL: BCVicYRSqKKt1ynJKPrXHA46hUWLrbjR49
• BTC: 3KedzPANAtCzADPbhT7GMv3LjxyeRXc4AE

Production Usage Notice

This is beta software. All of the following are things that can change and break an existing LIGHTBIT-NOMP setup: functionality of any feature, structure of configuration files and structure of redis data. If you use this software in production then DO NOT pull new code straight into production usage because it can and often will break your setup and require you to tweak things like config files or redis data. Only tagged releases are considered stable.

Paid Solution

Usage of this software requires abilities with sysadmin, database admin, coin daemons, and sometimes a bit of programming. Running a production pool can literally be more work than a full-time job.

Community

Discord

• https://discord.gg/WRMuMxp

If your pool uses LIGHTBIT-NOMP let us know and we will list your website here.

Some pools using LIGHTBIT-NOMP or node-stratum-yescrypt-0.5-module:

• HASHpex
• CPU pool

Usage

Requirements

• Coin daemon(s) (find the coin's repo and build latest version from source)
• Node.js v7+ (follow these installation instructions)
• Redis key-value store v2.6+ (follow these instructions)

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.

0) Setting up coin daemon

Follow the build/install instructions for your coin daemon. Your coin.conf file should end up looking something like this:

daemon=1
rpcuser=username
rpcpassword=password
rpcport=1605

For redundancy, its recommended to have at least two daemon instances running in case one drops out-of-sync or offline, all instances will be polled for block/transaction updates and be used for submitting blocks. Creating a backup daemon involves spawning a daemon using the -datadir=/backup command-line argument which creates a new daemon instance with it's own config directory and coin.conf file. Learn about the daemon, how to use it and how it works if you want to be a good pool operator. For starters be sure to read:

• https://en.bitcoin.it/wiki/Running_bitcoind
• https://en.bitcoin.it/wiki/Data_directory
• https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list
• https://en.bitcoin.it/wiki/Difficulty

1) Downloading & Installing

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

sudo apt-get install build-essential libsodium-dev npm
sudo npm install n -g
sudo n v9
git clone https://github.com/Beehivenetwork/lightbit-nomp.git
cd lightbit-nomp
npm update
npm install

Pool config

Take a look at the example json file inside the pool_configs directory. Rename it to lightbit.json and change the example fields to fit your setup.

Please Note that: 1 Difficulty is actually 8192, 0.125 Difficulty is actually 1024.

Whenever a miner submits a share, the pool counts the difficulty and keeps adding them as the shares.

ie: Miner 1 mines at 0.1 difficulty and finds 10 shares, the pool sees it as 1 share. Miner 2 mines at 0.5 difficulty and finds 5 shares, the pool sees it as 2.5 shares.

[Optional, recommended] Setting up blocknotify

1. In config.json set the port and password for blockNotifyListener
2. In your daemon conf file set the blocknotify command to use:

node [path to cli.js] [coin name in config] [block hash symbol]

Example: inside lightbit.conf add the line

blocknotify=node /home/user/lightbit-nomp/scripts/cli.js blocknotify lightbit %s

Alternatively, you can use a more efficient block notify script written in pure C. Build and usage instructions are commented in scripts/blocknotify.c.

3) Start the portal

npm start

Optional enhancements for your awesome new mining pool server setup:

• Use something like forever to keep the node script running in case the master process crashes.
• Use something like redis-commander to have a nice GUI for exploring your redis database.
• Use something like logrotator to rotate log output from ZNY-NOMP.
• Use New Relic to monitor your ZNY-NOMP instance and server performance.

Credits

ZNY-NOMP

• ROZ-MOFUMOFU-ME

K-NOMP

• yoshuki43

Z-NOMP

• Joshua Yabut / movrcx
• Aayan L / anarch3
• hellcatz

NOMP

• Matthew Little / zone117x - developer of NOMP
• Jerry Brady / mintyfresh68 - got coin-switching fully working and developed proxy-per-algo feature
• Tony Dobbs - designs for front-end and created the NOMP logo
• LucasJones - got p2p block notify working and implemented additional hashing algos
• vekexasia - co-developer & great tester
• TheSeven - answering an absurd amount of my questions and being a very helpful gentleman
• UdjinM6 - helped implement fee withdrawal in payment processing
• Alex Petrov / sysmanalex - contributed the pure C block notify script
• svirusxxx - sponsored development of MPOS mode
• icecube45 - helping out with the repo wiki
• Fcases - ordered me a pizza <3
• Those that contributed to node-stratum-pool

License

Released under the MIT License. See LICENSE file.