Ceres Combine-Harvester
Ceres is a combine harvester designed to harvest plots for Chia blockchain and its forks using proof-of-space-and-time(PoST) consensus algorithm.
Features
-
Single harvester, multiple forks harvested
-
Ceres is based on Chia's source code, with least modification
-
Ceres is running with only one harvester server, not each server for each fork
-
Almost same cpu and memory usage as a single Chia harvester
-
Follow Chia's asyncio design pattern, by principle multiple forks activities will not affect Chia harvestering
-
Easy to configure to support more forks as you wish
-
Multi-platforms supported, such as Raspberry Pi
Installing
Ceres can be installed the same way installing Chia normally.
It's highly recommended to read through Chia's wiki, easpecially this article , Farming on many machines · Chia-Network/chia-blockchain Wiki · GitHub before using Ceres.
git clone https://github.com/hulatangeric/Ceres-CombineHarvester.git
sudo chmod +x install.sh
./install.sh
Init
if you have setup forks you want to harvest, it is to say you have got .chia or .forks under your home directory, you an just skip this chapter to Run
here we init from absolutly fresh install, just run:
ceres init_all
this command will generate root path for each forks, like .chia, .flax under your home directory
next we generate ssl files for each forks, for example you want to harvest flax:
-
copy ca directory from you farmer computer to local [path_to_ca]
-
run:
ceres init -n flax -c [path_to_ca]
Finally, what you need to change is your famer-peer ip address under Harvester section(not full node section) in each fork's config.yaml
Run
activate venv first, then run:
ceres start harvester -r
Network Architecture
Defult Chia Harvester and Famer is structured as below
By Chia default, you should run one harvester for each fork's farmer.
Ceres has a different structure, like below:
By using Ceres, you can run an unique Harvester server which will response to all the farmer's request. Thanks to Chia's asyncio pattern, a single Harvester server has enough throughput to proccess farmer's asynchronous challenge hash request.
Compatibility
For a harvester, it is responsible for communicating with famer by complying chia's Harvester Protocol.
Inspecting most fork's source code shown that there exsits two way to modify Chia's source code.
-
Chia family:
forks like flax, goji and many uses the exactly same harvester protocol as Chia
-
Spare family:
forks like spare uses their extended harvester protocol, by which change the process harvester communicate with farmer,.
Currently, Creres only support the Chia family forks, these fork's harvester say the same language to their farmer like Chia does.
Spare family forks will be supported very soon.
Current supported forks:
How to add more forks?
It is easy for Ceres to add more forks support .
Just download the all-coin-config.yaml from github and replace the old file in chia/util subdirectory.
then run:
ceres stop all -d
ceres start harvester -r
How to remove forks you don't want to harvester
edit the file ceres/util/all-coins-config.yaml
just comment forks you don't want to harvester, like below
chia:
network_id: "mainnet"
flax:
network_id: "flax-mainnet"
#kale:
#network_id: "kale-mainnet"
#version: "0.1.21"
#goji:
#network_id: "mainnet"
#version: "0.2.3"
then:
ceres stop all -d
ceres start harvester -r
1 Nov 05, 2021
20 Dec 16, 2022
17 Oct 07, 2022
4 Mar 16, 2022
27 Jan 08, 2023
2 Jan 03, 2022
5 Jul 30, 2022
162 Dec 21, 2022
1 Jan 23, 2022
633 Dec 23, 2022
1 Nov 29, 2021
96 Dec 05, 2022
0 Jun 14, 2022
1.6k Jan 07, 2023
473 Dec 25, 2022
24 Jun 17, 2022
7 Apr 21, 2022
10 Jul 13, 2022
2 Apr 03, 2022
1 Jan 27, 2022