Clore Fleet

Another Method for Adding Rigs to the CLORE Marketplace, Previously Mentioned

This method allows you to add servers via the HiveOS flightsheet and instantly upload multiple servers simultaneously.

IMPORTANT: Do not enable Clore Fleet on servers that are already added to the CLORE platform, as this will cause them to re-register with a new name. This can lead to malfunctions that require a full reinstallation starting from Hive OS.

Go to the My Servers section on the website:

1. Click the Mass Onboard button.

In the window that appears, select HiveOS (Ubuntu is currently unavailable) and choose the rental pricing method:

• Static: the price is set manually in BTC or CLORE, or in USD. For USD, prices in BTC and CLORE are automatically recalculated every two hours.

• Mining Profitability Based: a multiplier is specified, applied to the idle mining profitability.

Set the prices, maximum rental duration, and configure additional options:

Override offer specifics on each machine reboot or change of configuration

Enabling this option makes it impossible to adjust rental pricing through the CLORE website dashboard. To change the rental price, you need to update the Auth token used in the HiveOS flightsheet as follows: go to My Servers, click Mass Onboard, set the desired price, enable or disable the option, then copy the new Auth token and update it in the HiveOS flightsheet. If this option is disabled, you can change the rental price through the server settings on the CLORE website.

Use Overclocking and Power Limits from HiveOS for Orders by Default

When this option is enabled, the overclocking configured in HiveOS will be applied to the server’s default overclocking profile on the CLORE platform. If overclocking is changed in HiveOS, it will automatically update in the default profile on the CLORE website. The server will be moved to the Power Efficient marketplace, as this action modifies the default overclocking profile. To disable this option, change the Auth token in the HiveOS flightsheet.

Keep Clore.ai running even when miner is disabled

If this option is not enabled, when the HiveOS flightsheet is turned off or another flightsheet is used, the server will be disconnected from the marketplace and will appear offline on the CLORE website.

To enable this option, if it was not previously activated, update the Auth token. After this, the server will remain active on the marketplace even if the flightsheet is turned off or changed in HiveOS.

You can only disable this option using the command:

systemctl stop clore-onboarding.service ; systemctl disable clore-onboarding.service ; systemctl stop clore-hosting.service ; systemctl disable clore-hosting.service ; systemctl stop docker.service ; systemctl disable docker.service

Next, go to HiveOS and create a new flightsheet:

Copy the text from the HiveOS Flightsheet field (a copy button is provided there).

In HiveOS, click Clipboard, then Wallet, add the Auth token, paste it, assign a name to the flightsheet, and click Create.

As a second miner, add what will be mined during idle time.

IMPORTANT: Never share your unique Auth token. This token allows others to control your servers.

Once setup is complete, the server will appear in the server list on the CLORE platform. The installation log can be viewed the same way as the mining log — in HiveOS Shell by running the command miner.

You can only disable this option using the command:

systemctl stop clore-onboarding.service ; systemctl disable clore-onboarding.service ; systemctl stop clore-hosting.service ; systemctl disable clore-hosting.service ; systemctl stop docker.service ; systemctl disable docker.service