How to setup a Chia Harvester


To get a Harvester computer setup, follow these steps.

These steps assume you already have a FULL NODE computer running.


HOME will be your user folder on a machine.

Linux		/home/<username>
Windows		C:\Users\<username>
FULL NODE will be the machine you are running as a full node.

HARVESTER will be the machine you want to run as a harvester, and not a full node.

Step 1. Make a copy of the ca folder on the FULL NODE and put it on the HARVESTER. I used a thumb drive to do this, but I have seen other use secure copy (scp) on the command line.

Linux		~/.chia/mainnet/config/ssl/ca
Windows		C:\Users\<username>\.chia\mainnet\config\ssl\ca

Step 2. Edit the “config.yaml” file on the FULL NODE and make the following change.

farmer: -> logging: -> log_level: Change "WARNING" to "INFO" ("DEBUG" with 1.1.6)

Linux		~/.chia/mainnet/config/config.yaml
Windows		C:\Users\<username>\.chia\mainnet\config\config.yaml

Step 3. You need to get your seed words from your FULL NODE, put them into a text file, and put that text file onto the HARVESTER machine. You could type in the seed words if you have a paper backup of them. Be sure all the words on the first line and a single space separates each word.

GUI Method:
If you open the GUI there will be an eye icon you can click to see your seed words. Copy and paste these into a new text file called “seed.txt”. Move this file to the HARVESTER computer and put in the HOME directory.

CLI Methods:
Linux - Enter the following command to start the Python virtual environment:

source ~/chia-blockchain/activate

chia keys show --show-mnemonic-seed

Windows - Open Powershell and browse to the following directory and run the command to show the keys.

cd C:\Users\<username>\AppData\Local\chia-blockchain\<version>\resources\app.asar.unpacked\daemon

chia keys show --show-mnemonic-seed

The last line will be your 24 secret words. Copy and paste these into a new text file called “seed.txt”. Move this file to the HARVESTER computer and put in the HOME directory.

Step 4. Install Chia Blockchain on HARVESTER machine.

Step 5. If you installed using the GUI, you can close the GUI after it is installed. We will setup the HARVESTER from the command line.

Step 6. On HARVESTER, we will import the keys (this will be the same command for both Linux and Windows)

chia keys add -f <HOME>\seed.txt

Be sure to replace “<HOME>” with your actual home directory for either Linux or Windows. This should be where you moved the seed file.

Step 7. On HARVESTER, open the config file (same path as in Step 2).

Step 8. Under the “harvester” block, set the host of the “farmer_peer” to be the IP Address of the FULL NODE.

Step 9. Back in Terminal or Powershell, run the following command to setup the certificates on the HARVESTER.

chia init -c <HOME>\ca

Be sure to replace “<HOME>” with your actual home directory for either Linux or Windows. This should be where you copied the ca folder.

Step 10. On HARVESTER, we will start the harvester process by running the following command. Note: the GUI should not be open now.

chia start harvester

Note: On windows you must leave the Powershell window open while harvesting.

Step 11. On FULL NODE, we will check to see that we have a connection from the HARVESTER.

GUI Method:
Go to the Farm tab, scroll to the bottom and click on Show Advanced Options. The HARVESTER’s IP Address should now be visible as a node. If it is not, you need to make sure your firewall allows port 8448.

CLI Methods:
I haven't found a way to check this from the command line using chia. Skip to Step 12 and well confirm the HARVESTER IP is in the log file on the FULL NODE.

Step 12. You can confirm it is working by viewing the log on the FULL NODE and searching for the HARVESTER’s IP Address.

Linux log file:		~/.chia/mainnet/log/debug.log
Window log file:	C:\Users\<user>\.chia\mainnet\log\debug.log

Run this command to check the debug.log file.

cat debug.log | grep "<harvester_IP_address>"

You should see an entry saying “new_signage_point_harvester to peer <harvester’s ip address>”.

--Steve

Comments

Popular posts from this blog