This fork is for Bitcoin and Bitcoin Cash mining. A few improvements have been made, such as;
- Upgraded to .NET 8
- Upgraded all packages to their latest versions, including fixing some breaking changes
- Modified VarDiff to use an integer instead of double
- Removed all alt-coin specific functionality.
Everything else is still the same.
- 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
Code contributions are very welcome and should be submitted as standard pull requests (PR) based on the dev branch.
git clone https://github.com/owenashurst/miningcore
cd miningcoreDepending on your OS Version run either of these scripts:
./build-debian-11.shor
./build-ubuntu-20.04.shor
./build-ubuntu-21.04.shDownload and install the .NET 8 SDK
git clone https://github.com/owenashurst/miningcore
cd miningcore
build-windows.bat- Install Visual Studio 2022. Visual Studio Community Edition is fine.
- Open
Miningcore.slnin Visual Studio (or Jetbrains Rider)
In case you don't want to install any dependencies then you can build the app using the official Microsoft .NET SDK Docker image.
git clone https://github.com/owenashurst/miningcore
cd miningcoreThen build using Docker:
docker run --rm -v $(pwd):/app -w /app mcr.microsoft.com/dotnet/sdk:8.0 /bin/bash -c 'apt update && apt install libssl-dev pkg-config libboost-all-dev libsodium-dev build-essential cmake -y --no-install-recommends && cd src/Miningcore && dotnet publish -c Release --framework net8.0 -o /app/build/'It will use a Linux container, you will build a Linux executable that will not run on Windows or macOS. You can use a runtime argument (-r) to specify the type of assets that you want to publish (if they don't match the SDK container). The following examples assume you want assets that match your host operating system, and use runtime arguments to ensure that.
For macOS:
docker run --rm -v $(pwd):/app -w /app mcr.microsoft.com/dotnet/sdk:8.0 /bin/bash -c 'apt update && apt install libssl-dev pkg-config libboost-all-dev libsodium-dev build-essential cmake -y --no-install-recommends && cd src/Miningcore && dotnet publish -c Release --framework net8.0 -o /app/build/ -r osx-x64 --self-contained false'note - The build scripts optimize the build for the hardware platform the container is built on ( does it have avx for example). If you run this container on a platform that does NOT have the same architecture you could have unexplained crashes. YOU SHOULD BUILD THIS CONTAINER ON THE HOST YOU ARE GOING TO RUN THIS CONTAINER ON.
Commands to build container: docker build -t <your_dockerhubid>/miningcore:v73-foo .
The docker build assumes you are going to mount your config file in a volume mount. for example:
docker run -d \
-p 4000:4000 \
-p 4066:4066 \
-p 4067:4067 \
--name mc \
-v `pwd`/config_prod.json:/app/config.json \
--restart=unless-stopped \
<your_dockerhubid>/miningcore:v73-foo
For Windows using Linux container:
docker run --rm -v $(pwd):/app -w /app mcr.microsoft.com/dotnet/sdk:8.0 /bin/bash -c 'apt update && apt install libssl-dev pkg-config libboost-all-dev libsodium-dev build-essential cmake -y --no-install-recommends && cd src/Miningcore && dotnet publish -c Release --framework net8.0 -o /app/build/ -r win-x64 --self-contained false'To delete used images and containers you can run after all:
docker system prune -afWindows is not a supported production environment. Only Linux is. Please do not file issues related to running a pool on Windows. Windows topics should be posted under discussions.
Running and developing Miningcore on Windows is of course supported.
Miningcore currently requires PostgreSQL 10 or higher.
Run Postgres's psql tool:
sudo -u postgres psqlIn psql execute:
CREATE ROLE miningcore WITH LOGIN ENCRYPTED PASSWORD 'your-secure-password';
CREATE DATABASE miningcore OWNER miningcore;Quit psql with \q
Import the database schema:
sudo -u postgres psql -d miningcore -f miningcore/src/Miningcore/Persistence/Postgres/Scripts/createdb.sqlIf you are planning to run a Multipool-Cluster, the simple setup might not perform well enough under high load. In this case you are strongly advised to use PostgreSQL 11 or higher. After performing the steps outlined in the basic setup above, perform these additional steps:
WARNING: The following step will delete all recorded shares. Do NOT do this on a production pool unless you backup your shares table using pg_backup first!
sudo -u postgres psql -d miningcore -f miningcore/src/Miningcore/Persistence/Postgres/Scripts/createdb_postgresql_11_appendix.sqlAfter executing the command, your shares table is now a list-partitioned table which dramatically improves query performance, since almost all database operations Miningcore performs are scoped to a certain pool.
The following step needs to performed once for every new pool you add to your cluster. Be sure to replace all occurences of mypool1 in the statement below with the id of your pool from your Miningcore configuration file:
CREATE TABLE shares_mypool1 PARTITION OF shares FOR VALUES IN ('mypool1');Once you have done this for all of your existing pools you should now restore your shares from backup.
Create a configuration file config.json as described here.
cd build
Miningcore -c config.jsonRefer to this file for a complete list.
Miningcore comes with an integrated REST API. Please refer to this page for instructions: https://github.com/oliverw/miningcore/wiki/API
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.
Once again, do not run a production pool on Windows! This is not a supported configuration.