ZenCash ZEN Mining Module
I have been receiving this question very often.. Now that the entire ZenCash ecosystem has changed with the 4x to the Zen network hashrate.. Where should you point your miners for max ZenCash mining profits?
By maintaining 88.14% of the mining reward with Zen. Hello,I check your blog named “Zen is Launching as a Harmonious Split with ZClassic in. Block Operations. Miningspeed Equihash Mining Pool: Stable, anonymous, and fair mining pool. May 23, 2017 - *The authors can be reached at rob@zensystem.io, rolf@zensystem.io, and jane@zensystem.io, respec- tively. Complishments include developing an open source mining pool application for both Zcash. Modules, discussions, and webinars on Zen principles and relevant subjects for Chap. Best Electra ECA Miner Hardware.
While I haven't been able to effectively study the new network for very long my initial 24 hour test shows promising results! This test is traceable on the block chain as well as at these Zen addys znnkiiu9DgngkAdaGtRZVRugUKyHKs5aD7a What do you think is the best mining pool for ZenCash? Donations truly appreciated and accepted BTC - 12PsgKuhcJrEqJbD3oMN7rcEcuyqyqRznL ETH - 0xDEe6A2ae293F8C58Ef4BbF382b6e70 ZEC - t1WRoxHVh8vhDJxAr6vpP4zzj3xHGF9ZbgQ ZEN - znb1iNFP6VctF2AhXLXtMsSjP7emvYDmeXR DASH - XpTt1nsjW1xt95WBZRyWciedDDBjgEctfD Like VoskCoin on facebook.
Jan 22, 2017 - A few weeks ago I posted a how-to on building a Linux GPU miner for Claymore. Well, at least as of right now, the Optiminer 1.5 Zcash miner is faster than Claymore. I have set up my mining rigs to run both Claymore and Optiminer now. I recommend you run Optiminer 1.5 on Ubuntu Linux. It's much easier. Oct 25, 2017 - Send 4 or 5 transactions of 0.1 to 0.25 zen to from the ZenCash wallet you have running on your PC or Mac. Clone this repository then install node modules. Had to upgrade the mining facility to more than 400 miners, put in place monitoring, and do some ZenCash related travel.
README.md Zcash® and Zclassic - Node Open Mining Portal This is a Equihash mining pool based off of Node Open Mining Portal. Donations for development are greatly appreciated!
• BTC: 18vHMxVzotQ9EPyESrf7Z1hNM9AwJeVHgD • ZCL: zcXDWbgReztLLXSTUMT2nEumiDM6zTzUXFb7vUnx9JNfJDVqbodyxwEQwgDkFw7Dp128tBU8n8rmVxT43DshmeTEM4LHcdz Production Usage Notice This is beta software. All of the following are things that can change and break an existing Z-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 / Support IRC • Support / general discussion join: If your pool uses Z-NOMP let us know and we will list your website here.
Some pools using Z-NOMP or node-stratum-module: Running MPOS and 0.5% of the fee goes to the Zclassic donation fund! 200+ blocks have been found as well! Zcash Pool with Custom Frontend w/Miner's Jackpot Custom frontend Custom frontend and 0% fee 0.5% fee Usage Requirements • Coin daemon(s) (find the coin's repo and build latest version from source) • v7+ () • key-value store v2.6+ () 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.: 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. 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=zclassicrpc rpcpassword=securepassword rpcport=8232 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: • • • • 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 stable git clone z-nomp cd z-nomp npm update npm install Pool config Take a look at the example json file inside the pool_configs directory. Rename it to zclassic.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 • In config.json set the port and password for blockNotifyListener • 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 zclassic.conf add the line blocknotify=node /home/user/z-nomp/scripts/cli.js blocknotify zclassic%s Alternatively, you can use a more efficient block notify script written in pure C.
Build and usage instructions are commented in. 3) Start the portal. Npm start Optional enhancements for your awesome new mining pool server setup: • Use something like to keep the node script running in case the master process crashes. • Use something like to have a nice GUI for exploring your redis database. • Use something like to rotate log output from Z-NOMP. • Use to monitor your Z-NOMP instance and server performance.
Upgrading Z-NOMP When updating Z-NOMP to the latest code its important to not only git pull the latest from this repo, but to also update the node-stratum-pool and node-multi-hashing modules, and any config files that may have been changed. • Inside your Z-NOMP directory (where the init.js script is) do git pull to get the latest Z-NOMP code. • Remove the dependenices 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 and pool_configs/coin.json configurations 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. Credits Z-NOMP • • • NOMP • - developer of NOMP • - got coin-switching fully working and developed proxy-per-algo feature • - designs for front-end and created the NOMP logo • - got p2p block notify working and implemented additional hashing algos • - co-developer & great tester • - answering an absurd amount of my questions and being a very helpful gentleman • - helped implement fee withdrawal in payment processing • - contributed the pure C block notify script • - sponsored development of MPOS mode • - helping out with the repo wiki • - ordered me a pizza.