Foxy-Farmer is a simplified farmer for the chia blockchain using the Foxy-Pool chia farming gateway to farm without a full node running on your machine.
[!NOTE] If you can run a full node, you should!
Foxy-Farmer is useful in the following scenarios:
If you are migrating from FlexFarmer please check out this guide.
The docs can be found here.
On Linux ensure you have ocl-icd-libopencl1
installed when using the gigahorse
backend
Download the latest binary zip for your OS from the releases page
Run the binary and follow the first run wizard, it will create a foxy-farmer.yaml
in the current directory based on your inputs.
Note: You can join the pool at any time, just run
./foxy-farmer join-pool
. You can add--fee
to supply a fee in case the mempool is full.
(Optional) Edit the foxy-farmer.yaml
to your liking and restart foxy-farmer
Profit!
On Linux ensure you have ocl-icd-libopencl1
installed when using the gigahorse
backend
Clone the git repo and cd into it: git clone https://github.com/foxypool/foxy-farmer && cd foxy-farmer
Create a venv:
python3 -m venv venv
Install the dependencies:
venv/bin/pip install .
Run using venv/bin/foxy-farmer
(or activate the venv using source venv/bin/activate
and then just use foxy-farmer
) and follow the first run wizard, it will create a foxy-farmer.yaml
in the current directory based on your inputs.
Note: You can join the pool at any time, just run
foxy-farmer join-pool
. You can add--fee
to supply a fee in case the mempool is full.
(Optional) Edit the foxy-farmer.yaml
to your liking and restart foxy-farmer
Profit!
A docker image based on the provided Dockerfile is available via ghcr.io/foxypool/foxy-farmer:latest
and foxypool/foxy-farmer:latest
.
For specific tags see this list.
A docker-compose.yaml example is available as well, to get started.
Currently, this requires you to have a working foxy-farmer.yaml
already available to mount into the container. See this example configuration for reference.
If you do not have a .chia_keys
directory from a previous chia install, you can set the CHIA_MNEMONIC
environment variable to your 24 words and it will create they keyring accordingly. Please unset it again once done.
Note: To execute the join-pool command please first exec into the running container with
docker exec -it <name of your container> bash
Then you can run foxy-farmer join-pool inside the container.
Just download the latest version of the binary from here like you did on install and replace the existing binary, that's it.
foxy-farmer
directory which you cloned during install.git pull
venv/bin/pip install --upgrade .
Pull the latest image using docker pull ghcr.io/foxypool/foxy-farmer:latest
and recreate the container using docker compose up -d
.
Yes, Foxy-Farmer itself is open source and uses the og pooling patched chia-blockchain client under the hood which is open source as well, so you can verify yourself nothing funky happens. When using the gigahorse
backend the Gigahorse Farmer and Harvester from madMAx43v3r are used under the hood which are closed source, however. As such the farming topology has not changed, your locally running farmer still signs your blocks, same as when running a local full node. Your keys do not leave your machine.
Yes, using the chia farming gateway without pooling in Foxy-Pool is supported, but a 1% fee is charged when farming a block with a Pool Public Key or Launcher Id which is not pooling with Foxy-Pool.
You can use remote harvesters with foxy-farmer, just make sure to use the port 18447 and use the ssl ca directory from .foxy-farmer
.
A make_harvester_installer.ps1
and run_harvester.ps1
script is provided to simplify this for Windows users, especially when running gigahorse remote harvesters already. Just run the make_harvester_installer.ps1
script and copy the resulting foxy-harvester
directory onto the remote harvesters and run run_harvester.ps1
on them.
GNU GPLv3 (see LICENSE)