- Zeronode support
- Supports clusters of pools each running individual currencies
- Ultra-low-latency, multi-threaded Stratum implementation using asynchronous I/O
- Adaptive share difficulty ("vardiff")
- PoW validation (hashing) using native code for maximum performance
- Session management for purging DDoS/flood initiated zombie workers
- Payment processing
- Banning System
- Live Stats API on Port 4000
- WebSocket streaming of notable events like Blocks found, Blocks unlocked, Payments and more
- POW (proof-of-work) & POS (proof-of-stake) support
- Detailed per-pool logging to console & filesystem
- Runs on Linux and Windows
- Pools need to be configured with both a t-addr and z-addr (new configuration property "z-address" of the pool configuration element)
- First configured zerod daemon needs to control both the t-addr and the z-addr (have the private key)
- To increase the share processing throughput it is advisable to increase the maximum number of concurrent equihash solvers through the new configuration property "equihashMaxThreads" of the cluster configuration element. Increasing this value by one increases the peak memory consumption of the pool cluster by 1 GB.
- Miners may use both t-addresses and z-addresses when connecting to the pool
- When zeronodes are enabled a the block subsity for masternodes will be a trickle. Less than one day before the masternode enforcement blockheight a spork will be enabled on the zeronode network changing the Miner Reward to 7.83POW 2.16ZN(MN-POS).
- Due the spork zeronodes will receive reward according to the live zero 3.0x daemon blocktemplate used on the community pool.
- If you are using this privately and don't wish to pay any amount to zeronodes until enforcement is enabled change src/Miningcore/Blockchain/Equihash/Equihashjob.cs @line 128 to "if (coin.HasZeroNodes && BlockTemplate.ZeroNodePaymentsEnabled && BlockTemplate.ZeroNodePaymentsEnforced)"
- .Net Core 2.1 Runtime
- PostgreSQL Database
- Coin Daemon (per pool)
- .Net Core 2.1 SDK
- PostgreSQL Database
- Coin Daemon (per pool)
- Miningcore needs to be built from source on Linux. Refer to the section further down below for instructions.
- Download miningcore-win-x64.zip from the latest Release
- Extract the Archive
- Setup the database as outlined below
- Create a configuration file
config.json
as described here - Run
dotnet Miningcore.dll -c config.json
Create the database:
$ createuser miningcore
$ createdb miningcore
$ psql (enter the password for postgres)
Run the query after login:
alter user miningcore with encrypted password 'some-secure-password';
grant all privileges on database miningcore to miningcore;
Import the database schema:
$ wget https://raw.githubusercontent.com/coinfoundry/miningcore/master/src/Miningcore/Persistence/Postgres/Scripts/createdb.sql
$ psql -d miningcore -U miningcore -f createdb.sql
$ wget -q https://packages.microsoft.com/config/ubuntu/16.04/packages-microsoft-prod.deb
$ sudo dpkg -i packages-microsoft-prod.deb
$ sudo apt-get update -y
$ sudo apt-get install apt-transport-https -y
$ sudo apt-get update -y
$ sudo apt-get -y install dotnet-sdk-2.1 git cmake build-essential libssl-dev pkg-config libboost-all-dev libsodium-dev libzmq5
$ git clone https://github.com/coinfoundry/miningcore
$ cd miningcore/src/Miningcore
$ dotnet publish -c Release --framework netcoreapp2.1 -o ../../build
Download and install the .Net Core 2.1 SDK
> git clone https://github.com/coinfoundry/miningcore
> cd miningcore/src/Miningcore
> dotnet publish -c Release --framework netcoreapp2.1 -o ..\..\build
- Download and install the .Net Core 2.1 SDK
- Install Visual Studio 2017. Visual Studio Community Edition is fine.
- Open
Miningcore.sln
in VS 2017
Create a configuration file config.json
as described here
cd ../../build
dotnet Miningcore.dll -c config.json
A public production pool requires a web-frontend for your users to check their hashrate, earnings etc. Miningcore does not include such frontend but there are several community projects that can be used as starting point.