Open expanse pool
https://github.com/expanse-org/open-expanse-pool
Last updated
Was this helpful?
https://github.com/expanse-org/open-expanse-pool
Last updated
Was this helpful?
This branch is 14 commits ahead of sammy007:master.
This pool is being further developed to provide an easy to use pool for Expanse 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
HTTP proxy with web interface
for Expanse
Dependencies:
go >= 1.9
geth or parity
redis-server >= 2.8.0
nodejs >= 4 LTS
nginx
I highly recommend to use Ubuntu 16.04 LTS.
Clone & compile:
Install redis-server.
You can use Ubuntu upstart - check for sample config in upstart.conf
.
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.
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.
Made by expanse-org. Licensed under GPLv3.
ETH/ETC: 0xb85150eb365e7df0941f0cf08235f987ba91506a
Highly appreciated.
First install .
Install nodejs. I suggest using LTS version >= 4.x from or from your Linux distribution or simply install nodejs on Ubuntu Xenial 16.04.
This pool is tested to work with . Mining and block unlocking works, but I am not sure about payouts and suggest to run official geth node for payments.