Configuration

This guide covers configurations that are needed after initializing your storage provider. It also highlights some optional configurations you might want to consider.

Required configurations #

The API section controls the settings of the miner API:

Since we initialized the storage provider with the --no-local-storage in the initialize page, we need to specify the disk locations for long-term storage and sealing (fast SSDs recommended).

The lotus-miner keeps track of defined storage locations in ~/.lotusminer/storage.json (or $LOTUS_MINER_PATH/storage.json) and uses ~/.lotusminer path as default.

Upon initialization of a storage location, a <path-to-storage>/sectorstorage.json file is created that contains the UUID assigned to this location, along with whether it can be used for sealing or storing.

Adding sealing storage location #

Before adding your sealing storage location you will need to consider where the sealing tasks are going to be performed. While the lotus-miner can run all of the sealing phases, and is configured to do so by default, using seal workers to offload computational heavy sealing tasks to separate machines or processes is recommended. Depending on how you architect your system you will either need to add the sealing location to the lotus-worker, the lotus-miner or both depending on where you want the sealing tasks to be performed.

Under the storage-section in your ~/.lotusminer/config.toml or $LOTUS_MINER_PATH/config.toml file, you can configure which sealing process you would like your lotus-miner to perform. If you want to fully delegate any of these operations to workers, set them to false.

[Storage]
  AllowAddPiece = true
  AllowPreCommit1 = true
  AllowPreCommit2 = true
  AllowCommit = true
  AllowUnseal = true
  AllowReplicaUpdate = true
  AllowProveReplicaUpdate2 = true

If you want some or all of the sealing tasks to be performed on the lotus-miner you will need to add a custom sealing location for the tasks. The seal storage location should be a really fast storage medium so that the disk does not become the bottleneck that delays the sealing process. It can be specified with:

lotus-miner storage attach --init --seal <PATH_FOR_SEALING_STORAGE>

If you want to offload all the sealing tasks to lotus-workers you only need to add the sealing location on the workers and not on the lotus-miner. To setup seal workers follow the seal worker guide.

Adding long-term storage location #

Custom location for storing: After the sealing process is completed, sealed sectors are moved to the store location, which can be specified as follow:

lotus-miner storage attach --init --store <PATH_FOR_LONG_TERM_STORAGE>

This location can be made of large capacity, albeit slower, spinning-disks.

Optional configurations #

These prerequisites are optional and can be used on a case by case basis. Please make sure to understand the use case before performing these steps.

Sealing performance #

It is recommended to set the following environment variables in the environment so that they are defined every time any of the lotus daemons are launched:

 # See https://github.com/filecoin-project/rust-fil-proofs/
 export FIL_PROOFS_USE_GPU_COLUMN_BUILDER=1 # precommit2 GPU acceleration
 export FIL_PROOFS_USE_GPU_TREE_BUILDER=1

 # The following increases speed of PreCommit1 at the cost of using a full
 # CPU Core-Complex rather than a single core. Should be used with CPU affinities set!
 # See https://github.com/filecoin-project/rust-fil-proofs/ and the seal workers guide.
 export FIL_PROOFS_USE_MULTICORE_SDR=1

Depending on your GPU, you might want to experiment with the optional BELLMAN_CPU_UTILIZATION variable to designate a proportion of the multi-exponentiation calculation to be moved to a CPU in parallel with the GPU. However, omitting this environment variable is probably optimal if you have a newer GPU card.

# See https://github.com/filecoin-project/bellman
export BELLMAN_CPU_UTILIZATION=0.875

The interval must be a number between 0 and 1. The value 0.875 is a good starting point, but you should experiment with it if you want an optimal setting.

Configuration file #

The lotus-miner configuration file is created after the initialization step, and is placed in ~/.lotusminer/config.toml or $LOTUS_MINER_PATH/config.toml when defined.

You can see your versions default configuration file with the lotus-miner config default command. Its recommended to get familiar with the different sections and read through the comments in the file. We list a couple of the sections below, but the full list can always be found with the CLI. In the Operate and Advanced configurations sections we will discuss some of these items and sections more in-depth.

The configuration file has all the items commented. To customize one of the items, you must remove the leading #.

API section #

The API section controls the settings of the lotus-miner API:

[API]
  # Binding address for the Lotus API
  #
  # type: string
  # env var: LOTUS_API_LISTENADDRESS
  #ListenAddress = "/ip4/127.0.0.1/tcp/2345/http"

  # type: string
  # env var: LOTUS_API_REMOTELISTENADDRESS
  #RemoteListenAddress = "127.0.0.1:2345"

  # type: Duration
  # env var: LOTUS_API_TIMEOUT
  #Timeout = "30s"

As you see, the listen address is bound to the local loopback interface by default. To open access to the miner API for other machines, set this to the IP address of the network interface you want to use. You can also set it to 0.0.0.0 to allow all interfaces. API access is protected by JWT tokens, but it should not be open to the internet.

Configure RemoteListenAddress to the value that a different node would have to use to reach this API. Usually, it is the miner’s IP address and API port, but depending on your setup (proxies, public IPs, etc.), it might be a different IP.

Subsystem section #

This section allows you to disable subsystems of the lotus-miner.

[Subsystems]
  # type: bool
  # env var: LOTUS_SUBSYSTEMS_ENABLEMINING
  #EnableMining = true

  # type: bool
  # env var: LOTUS_SUBSYSTEMS_ENABLESEALING
  #EnableSealing = true

  # type: bool
  # env var: LOTUS_SUBSYSTEMS_ENABLESECTORSTORAGE
  #EnableSectorStorage = true

  # type: bool
  # env var: LOTUS_SUBSYSTEMS_ENABLEMARKETS
  #EnableMarkets = true

  # type: string
  # env var: LOTUS_SUBSYSTEMS_SEALERAPIINFO
  #SealerApiInfo = ""

  # type: string
  # env var: LOTUS_SUBSYSTEMS_SECTORINDEXAPIINFO
  #SectorIndexApiInfo = ""

Addresses section #

The addresses section allows users to specify additional addresses to send messages from. This helps mitigate head-of-line blocking for important messages when network fees are high. For more details see the Addresses section.

[Addresses]
  # Addresses to send PreCommit messages from
  #
  # type: []string
  # env var: LOTUS_ADDRESSES_PRECOMMITCONTROL
  #PreCommitControl = []

  # Addresses to send Commit messages from
  #
  # type: []string
  # env var: LOTUS_ADDRESSES_COMMITCONTROL
  #CommitControl = []

  # type: []string
  # env var: LOTUS_ADDRESSES_TERMINATECONTROL
  #TerminateControl = []

  # type: []string
  # env var: LOTUS_ADDRESSES_DEALPUBLISHCONTROL
  #DealPublishControl = []

  # DisableOwnerFallback disables usage of the owner address for messages
  # sent automatically
  #
  # type: bool
  # env var: LOTUS_ADDRESSES_DISABLEOWNERFALLBACK
  #DisableOwnerFallback = false

  # DisableWorkerFallback disables usage of the worker address for messages
  # sent automatically, if control addresses are configured.
  # A control address that doesn't have enough funds will still be chosen
  # over the worker address if this flag is set.
  #
  # type: bool
  # env var: LOTUS_ADDRESSES_DISABLEWORKERFALLBACK
  #DisableWorkerFallback = false

Fees section #

The fees section allow you to define what the max amount of gas you want to spend on the different type of messages sent to the chain.

[Fees]
  # type: types.FIL
  # env var: LOTUS_FEES_MAXPRECOMMITGASFEE
  #MaxPreCommitGasFee = "0.025 FIL"

  # type: types.FIL
  # env var: LOTUS_FEES_MAXCOMMITGASFEE
  #MaxCommitGasFee = "0.05 FIL"

  # type: types.FIL
  # env var: LOTUS_FEES_MAXTERMINATEGASFEE
  #MaxTerminateGasFee = "0.5 FIL"

  # WindowPoSt is a high-value operation, so the default fee should be high.
  #
  # type: types.FIL
  # env var: LOTUS_FEES_MAXWINDOWPOSTGASFEE
  #MaxWindowPoStGasFee = "5 FIL"

  # type: types.FIL
  # env var: LOTUS_FEES_MAXPUBLISHDEALSFEE
  #MaxPublishDealsFee = "0.05 FIL"

  # type: types.FIL
  # env var: LOTUS_FEES_MAXMARKETBALANCEADDFEE
  #MaxMarketBalanceAddFee = "0.007 FIL"

  [Fees.MaxPreCommitBatchGasFee]
    # type: types.FIL
    # env var: LOTUS_FEES_MAXPRECOMMITBATCHGASFEE_BASE
    #Base = "0 FIL"

    # type: types.FIL
    # env var: LOTUS_FEES_MAXPRECOMMITBATCHGASFEE_PERSECTOR
    #PerSector = "0.02 FIL"

  [Fees.MaxCommitBatchGasFee]
    # type: types.FIL
    # env var: LOTUS_FEES_MAXCOMMITBATCHGASFEE_BASE
    #Base = "0 FIL"

    # type: types.FIL
    # env var: LOTUS_FEES_MAXCOMMITBATCHGASFEE_PERSECTOR
    #PerSector = "0.03 FIL"

Next steps #

The storage provider should now be preliminarily set up and running, and you should now be ready to explore how to operate it and pledge storage to the Filecoin network. We recommend reading through at least these pages:

• Configure a separate address for WindowPost messages.
• Test your sealing pipeline by running a benchmark or by pledging a sector.
• Learn when to safely shut down/restart your miner

Market operations #

The lotus-miner performs sealing and proving operations. To perform market operations, managing data onboarding and serving retrievals to clients, the storage providers needs to setup Boost.

Boost is the default markets implementation supported by Lotus. It supports multiple options for data transfer when making storage deals, including HTTP. Clients can host their CAR file on an HTTP server, such as S3, and provide that URL when proposing the storage deal. Once accepted, Boost will automatically fetch the CAR file from the specified URL.

Edit this page on GitHub