A few months ago we announced our public minining pool for TurtleCoin that runs on OrangePi One Plus.
As this project was not enough, we stepped up to the challenge and recently set up a new pool for another privacy coin project in which we are involved – DeroGold.
Doing a pool for DeroGold is a bigger challenge. Why? One of the main reasons for that is DeroGold at the time of writing has 20 seconds block time. Keeping up your nodes synced with blockchain could be a challenge, and on a lower spec hardware you need to understand what you’re doing, as well as be able to do some basic performance troubleshooting & tuning.
It took us a few weeks to come up with a concept of building a really sturdy and reliable cluster of nodes to serve our DeroGold mining pool fast and reliable. We use haproxy loadbalancer to actively load balance between DeroGold nodes, and monit to monitor and recycle stuck or crashed daemons.
Unlike the architecture for the TurtleCoin pool where we put all components (nodejs pool, payment gateway and the TurtleCoin node itself) onto a single board deliberately, we decided to split components across multiple board for DeroGold.
As we mentioned earlier, reason we went for a distributed configuration was mainly because DeroGold has 10 seconds faster blocks when compared with TurtleCoin (30 seconds), as well as the number of transactions on the DeroGold network seems to be fairly heavy (8.3m transactions since the network went live in December 2018, compared with 4.2m transactions in the TurtleCoin network since its go live in December 2017). Additionally, DeroGold’s blockchain size at the time of writing reached 136 GB (compared with TurtleCoin’s 75 GB).
We run the pool components on the OrangePi 3 with 2GB RAM, 8GB emmc storage for the OS (Ubuntu Server) and a 512 GB SSD drive connected via USB3-to-SATA3 interface. The pool web front-end is pointed to another SBC board (frontend) that NGINX reverse proxy with SSL; and served via another SBC board in the backend that runs Apache and serves the actual pool static html website. The pool API backend is hooked to the NGINX SSL reverse proxy as well.
The three nodes that serve the pool are as follows – one on the OrangePi One Plus, one on a self-hosted Intel i3 Fujitsu server, and one in a remote location (UK datacenter) VPS server.
How does the pool run? Very well in our view. You can give it a go yourself by pointing your favorite miner (has to support cryptonight-turtle algo) to:
You can access the front-end of the Cuvée DeroGold pool in the following website: