This guide describes the necessary prerequisites before configuring a storage provider for production.

Being a storage provider will only work if you fully comply with the minimal hardware requirements for the network in which you will be a storage provider. The sealing process is very resource-intensive and is dependent on precise configuration. We strongly recommend Linux systems administration experience before embarking.

Please make sure that the following prerequites are met whether you are planning to run the lotus miner on the same machine as the lotus daemon or a different machine.

  1. Make sure your Lotus Node is running, as the storage provider will communicate with it and cannot work otherwise.
  2. If you are in China, read the tips for running in China page first.
  3. Make sure to add swap to the machine if needed.
  4. Permanently raise your fd-limit.

Install CUDA

  1. Install the latest stable Nvidia drivers and Cuda if you have an Nvidia card on your machine. Nvidia cards have a better performance with Cuda when compared to OpenCL.
  2. Make sure you have followed the instructions to install the Lotus suite to build the lotus-miner binary. Make sure that you have built Lotus with “Native Filecoin FFI”.

If you want to use OpenCL, or disable the GPU when building Lotus, check out this article.

Configure parameters location

For the storage provider to start, it will need to read and verify the Filecoin proof parameters. The proof parameters consist of several files, which in the case of 32 GiB sectors, total over 100 GiB.

We recommend setting a custom location to store the parameters and proofs parent cache:

export FIL_PROOFS_PARAMETER_CACHE=/path/to/folder/in/fast/disk
export FIL_PROOFS_PARENT_CACHE=/path/to/folder/in/fast/disk2

Make sure the ListenAddress has remote access enabled. Instructions on how to obtain a token are available here.

Performance tweaks

Parameters are read on every (re)start, so using disks with very fast access, like NVMe drives, will speed up lotus-miner and workers (re)boots. When the above variables are not set, things will end up in /var/tmp/ by default.

To download the parameters:

# Use sectors supported by the Filecoin network that the storage provider will join and use.
# lotus-miner fetch-params <sector-size>
lotus-miner fetch-params 32GiB
lotus-miner fetch-params 64GiB

Running the storage provider on a different machine as the Lotus Node

If you opt to run the lotus-miner on a different machine than the Lotus Node, set:

export FULLNODE_API_INFO=<api_token>:/ip4/<lotus_daemon_ip>/tcp/<lotus_daemon_port>/http

Make sure the ListenAddress has remote access enabled. Instructions on how to obtain a token are available here.

Creating wallets for the storage provider

You will need at least a BLS wallet (f3... for mainnet) to initialize. We recommend using separate owner and worker addresses:

# A new BLS address to use as owner address:
lotus wallet new bls

# A new BLS address to use as worker address:
lotus wallet new bls

For additional information about the different wallets that a storage provider can use and how to configure them, read the addresses guide.

Cuda variables

There are some changes in the latest Nvidia driver, so if you upgrade your driver remember to check nvidia-smi - it will always display the correct name for the GPU. The new names are not picked by FFI automatically and need to be exported manually.

If you are using an Nvidia driver below 460.91.03

export RUST_GPU_TOOLS_CUSTOM_GPU="GeForce RTX 3090:10496"

If you are using an Nvidia driver above 510.47.03

export RUST_GPU_TOOLS_CUSTOM_GPU="NVIDIA GeForce RTX 3090:10496"

Nvidia RTX 3090 was used in this example. Remember to edit it with your GPU and number of Cuda cores.

Edit this page on GitHub