[email protected] with HiveOS


HiveOS has now integrated the Linux flavor of the [email protected] client as another
configurable “miner” that may be chosen in order to build a “flight sheet” for
folding. Now, just as with any other mining configuration within HiveOS, you are
free to customize not only how many cards to fold with, but also to optionally
make use of your miner’s CPU to fold with as well. Just be aware that GPU
folding does incur CPU overhead at the rough ratio of about 1 core per GPU which
will be reflected in your rig’s Load Average (LA) value.

Folding with HiveOS Requirements:

ZelID or Zel address (if you want to enter to win 25k Zel)
A [email protected] passkey
A [email protected] mining wallet
A [email protected] flight sheet (either as a dual miner or standalone)
A configured miner

Covered in this Guide

Creating a [email protected] passkey
Creating a [email protected] wallet within HiveOS
Configuring a flight sheet within HiveOS
Configuring the [email protected] miner
Performance tuning
Monitoring output

Step 1: Get a [email protected] passkey

Before you can set up a new wallet, you must have a Folding at Home passkey.
If you don’t have one, you can create one here.

Once a passkey is obtained, you are free to begin folding with the ZelFlux team (Team ID: 262156).

Step 2: Create a wallet in HiveOS

The coin is FAH-CLI, the Address is your [email protected] username
Note: To be eligible to win 25k in the current zel folding contest you need to use a ZelID or Zel Address

Step 3: : Create (or add secondary [email protected] miner to an existing) flight sheet

Pick a flight sheet that the second miner will be added to
Configure the original miner in the flight sheet to only mine on certain cards (in this example it is miniZ / ZEL)

Back out to the main flight sheet screen and Add Miner

Choose the right coin and the wallet that was created in step 2

Choose [email protected] for the pool name (it is the only choice)

Select the [email protected] miner and configure it

Step 4: Configure the miner

Apply Changes, update and save

You are now ready to begin folding. The final dual mining result looks like this:

Performance Tuning

The [email protected] miner does not require any direct OC and should be left at default for power, core and memory (the algo is “antidote” below)

Power and “intensity” of the miner are controlled from within the [email protected] miner config itself.

Monitoring Output

If you want to see what your [email protected] miner is doing, you can invoke the “Hive Shell”

At the prompt type “miner” to see folding output

The maximum number of stable workers (each GPU or CPU) is equal to the number of cores your CPU has.

Not all work units are created equal - some are more hardware demanding than others - LA (Load Average) will turn red when that number goes over core # count.

Upgraded cooling is recommended if mining with an “unlocked” CPU using such as an Intel i5 7600k as temps WILL spike if not under optimal conditions.

CPU jobs tend to make 1/7 to 1/20 of total points a GPU job makes - some jobs that are tailored for CPUs that are not suited for GPUs, so it is very likely that your CPU will stay consistently busier than your GPUs.

It has been observed that on occasion when a GPU has not found work for an extended period of time, it will go "idle," potentially blank out and fail at finding more work - rebooting the rig is the only fix.

The [email protected] “miner” lacks functional integration with the built in watchdog feature but HiveOS does have a scheduling feature that can be used to compensate by allowing the ability to create a 4 hour reboot schedule which optimally minimizes folding downtime in these scenarios.

While you may be accustomed to set power limits of for your GPUs to something you are comfortable with (if not using the Auto Select Algo feature), it is best to clear out any overclock settings on those folding GPUs. They may still fold and be fine, but it increases the likelihood of a rig crash.

Special Thanks

This guide comes to you from the FOMO community.
Huge thanks to PorkChopSandwiches#9453 and Buck#9968 for putting this together.
Upload by CryptoWrench#6022