Open ethereum classic pool pplns

Сама команда запуска(должны быть в директории /pool/open-ethereum-pool):

screen -S pool ./build/bin/ethash-mining-pool config_api.json

Команда screen позволяет перейти ĸ процессу после подĸлючения ĸ серверу ĸомандой screen -x pool или server, если просто запустить и заĸрыть оĸно терминала — процесс прервется.

Источник

Open ethereum classic pool pplns

Open Source Ethereum Classic Mining Pool

This pool is being further developed to provide an easy to use pool for Ethereum Classic miners. Testing and bug submissions are welcome!

• Support for HTTP and Stratum mining
• Detailed block stats with luck percentage and full reward
• Failover geth instances: geth high availability built in
• Modern beautiful Ember.js frontend
• Separate stats for workers: can highlight timed-out workers so miners can perform maintenance of rigs
• JSON-API for stats
• PPLNS block reward
• Multi-tx payout at once
• Beautiful front-end highcharts embedded

• Ether-Proxy HTTP proxy with web interface
• Stratum Proxy for Ethereum

Guide to make your very own ETC mining pool

Building on Linux

I highly recommend to use Ubuntu 16.04 LTS.

Install go lang

It is recommended to bind your DB address on 127.0.0.1 or on internal ip. Also, please set up the password for advanced security.

Search on Google for nginx-setting

This will install the latest nodejs

Install Ethereum Classic node

Run Ethereum Classic node

If you use Ubuntu, it is easier to control services by using serviced.

Copy the following example

Then run ethereum classic by the following commands

If you want to debug the node command

Register pool account and open wallet for transaction. This process is always required, when the wallet node is restarted.

Install Ethereum Classic Pool

If you face open-classic-pool after ls

/open-classic-pool/build/bin/, the installation has completed.

Set up Ethereum Classic pool

Set up based on commands below.

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

I recommend this deployment strategy:

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

It is required to run pool by serviced. If it is not, the terminal could be stopped, and pool doesn’t work.

Copy the following example

Then run pool by the following commands

If you want to debug the node command

Backend operation has completed so far.

Firewall should be opened to operate this service. Whether Ubuntu firewall is basically opened or not, the firewall should be opened based on your situation. You can open firewall by opening 80,443,8080,8888,8008.

Modify configuration file

Make some modifications in these settings.

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

As you can see above, the frontend of the pool homepage is created. Then, move to the directory, www, which services the file.

Modify based on configuration file.

After setting nginx is completed, run the command below.

Type your homepage address or IP address on the web. If you face screen without any issues, pool installation has completed.

Extra) How To Secure the pool frontend with Let’s Encrypt (https)

First, install the Certbot’s Nginx package with apt-get

And then open your nginx setting file, make sure the server name is configured!

Change the _ to your pool domain, and now you can obtain your auto-renewaled ssl certificate for free!

Now you can access your pool’s frontend via https! Share your pool link!

• Unlocking and payouts are sequential, 1st tx go, 2nd waiting for 1st to confirm and so on. You can disable that in code. Carefully read docs/PAYOUTS.md .
• Also, keep in mind that unlocking and payouts will halt in case of backend or node RPC errors. In that case check everything and restart.
• You must restart module if you see errors with the word suspended.
• Don’t run payouts and unlocker modules as part of mining node. Create separate configs for both, launch independently and make sure you have a single instance of each module running.
• If poolFeeAddress is not specified all pool profit will remain on coinbase address. If it specified, make sure to periodically send some dust back required for payments.
• DO NOT OPEN YOUR RPC OR REDIS ON 0.0.0.0. It will eventually cause coin theft.

Made by sammy007. Licensed under GPLv3. Modified by Akira Takizawa & The Ellaism Project.

Источник

Open ethereum classic pool pplns

Open Source Ethereum Mining Pool

This pool is being further developed to provide an easy to use pool for Ethereum miners. This software is functional however an optimised release of the pool is expected soon. Testing and bug submissions are welcome!

• Support for HTTP and Stratum mining
• Detailed block stats with luck percentage and full reward
• Failover geth instances: geth high availability built in
• Modern beautiful Ember.js frontend
• Separate stats for workers: can highlight timed-out workers so miners can perform maintenance of rigs
• JSON-API for stats

• Ether-Proxy HTTP proxy with web interface
• Stratum Proxy for Ethereum

Building on Linux

• go >= 1.9
• geth or parity
• redis-server >= 2.8.0
• nodejs >= 4 LTS
• nginx

I highly recommend to use Ubuntu 16.04 LTS.

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

Install nodejs. I suggest using LTS version >= 4.x from https://github.com/nodesource/distributions or from your Linux distribution or simply install nodejs on Ubuntu Xenial 16.04.

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

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

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:

and add this setting after location / :

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

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 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.

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

I recommend this deployment strategy:

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

• Unlocking and payouts are sequential, 1st tx go, 2nd waiting for 1st to confirm and so on. You can disable that in code. Carefully read docs/PAYOUTS.md .
• Also, keep in mind that unlocking and payouts will halt in case of backend or node RPC errors. In that case check everything and restart.
• You must restart module if you see errors with the word suspended.
• Don’t run payouts and unlocker modules as part of mining node. Create separate configs for both, launch independently and make sure you have a single instance of each module running.
• If poolFeeAddress is not specified all pool profit will remain on coinbase address. If it specified, make sure to periodically send some dust back required for payments.

Alternative Ethereum Implementations

This pool is tested to work with Ethcore’s Parity. Mining and block unlocking works, but I am not sure about payouts and suggest to run official geth node for payments.

Источник