Chives

Start a Discussion or join our Discord for support and to help out.

The Chives Network is a forked clone of the original Chia™ Network blockchain. Chives uses it's own plots, distinct from Chia and other blockchains. Chives operates on a different network port too, so be sure to port-forward tcp/9699 at your router.

Summary Page

When Chives farming is enabled, the Summary will include a display of Chives Total Farmed, Chives Netspace Size, and Chives Estimated Time to Win.

Blockchain challenges from both networks are shown as well.

Plotting Page

Chives uses it's own plots, distinct from Chia and other blockchains. One must generate k29/k30/k31 plots for Chives using its own keys. This means you MUST copy the "Farmer public key" and "Pool public key" from the Keys page (Chives tab) into the Settings | Plotting page for the particular worker and fork (chives) you with to plot with. Then hit Save button:

Plotting should be done with madmax with k set to 29, 30, or 31. Also set network_port: 9699.

Farming Page

Plots are farmed to only the Chives blockchain fork. From the Farming page listing these common plots, it's also possible to view the debug.log from each farmer/harvester for each blockchain. Just click on the fork by name from the worker dropdown menu.

To see only Chives plots, simply enter 'chives' in the Search box on the top-right of the Farming page:

Known Issue: Due to the age of Chives codebase, harvester reporting to the fullnode is weak. Therefore, if you want a real "Estimated Time to Win" on the Chives view of the Summary page, you must place at least one Chives plot on the fullnode itself. If all your Chives plots are on harvesters, with an empty fullnode, then ETW will be inaccurately listed as 'Now'.

NOTE: Because Chives plots are different than Chia plots, the Machinaris Wizard suggests putting Chives plots into a child folder (named chives) within your Chia plot folders. This is a good default, but can be confusing for some existing Chives users who are bringing their own plots. Please double-check your plots_dir environment variable for the machinaris-chives container.

Alerts Page

When enabled, Machinaris tracks farming alerts from Chiadog.

Install and Setup

• Windows/Linux/etc users should use the Machinaris Launch wizard to create a docker-compose.yml that launches one container to farm Chia and one container to farm Chives. Then run docker-compose up to launch both containers.
• Unraid users should install the "Machinaris Chives" application add-on available by searching the Community Applications tab.

NOTE: Because Chives uses its own plot files, with its own keys, I strongly recommend keeping your Chives plots in a separate folder from your regular Chia plots. By default, the Machinaris install wizard and Machinaris New Worker page, both append a folder named chives to your main plots folders on the Host OS.

Import Existing Blockchain

If you have an existing Chives install with a fully-synced blockchain, you can simply copy that into a fresh install of Machinaris-Chives to avoid the need for a full sync. After first launch with docker compose up -d, you could then:

docker-compose stop machinaris-chives
rm -rf ~/.machinaris-chives/chives/mainnet
cp -r /path/to/old/chives/mainnet  ~/.machinaris-chives/chives/
cp /path/to/chives/mnemonic.txt ~/.machinaris-chives/
docker-compose pull
docker-compose up -d --force-recreate machinaris-chives
docker logs -f machinaris-chives

Also tail ~/.machinaris-chives/chives/mainnet/log/debug.log to ensure a clean start of Chives farmer. Then browse to http://localhost:8926/ and wait about 10 minutes for things to populate.