Creating a new miner in Curio

[stuberman]

While using curio guided-setup is a great help especially for migrations of existing lotus-miners, I want to share my experiences with building a new curio based miner from scratch (not a migration) using all of the components needed to make deals and store data on a single device. I will update this post as I learn more or as features change.

As it stands today using curio version 1.27.1-dev+calibnet there are four major components needed:

1. Yugabyte (a database that houses the configurations, deal indexes and pipeline state)
2. Lotus node (the daemon that runs the FIlecoin chain and services your wallets)
3. Curio (the software that orchestrates the sealing and storage of data)
4. Boost (the software that manages storage deals and retrieval deals for your Curio node)

High Level Initial setup (other documents provide the details in installing and configuring)

Preconfig:

• Determine your hardware layouts such as which disks and paths will be used
• Lotus chain needs fast disk such as NVMe and around 150GiB minimum space
• Yugabyte should not be using ZFS as it is not supported, the database will grow as you index many deals
• Sealing repo is best with high speed (NVMe or SSD) disk that is very durable the size will vary based on the through put of your sealing hardware. Record your sealing path(s)
• Storage repo should be high quality HDDs - many of use use ZFS for this in order to protect against corruption while allowing it to scale as we grow. Record your storage path(s)
• Environmental variables, Curio attempts to avoid as many env vars as possible but a few are required, whether path statements of Curio sealing parameters.
• Ensure your GPU is properly installed and configured
• Yugabyte wants both NTP and transparent hugepages configured
• DON'T EXPECT THIS TO WORK! "Create a path where you want the potentially large Yugabyte data base to be stored, as an example "/seal/var"" I had to revert to using the default install for Yugabyte which put everything in your ~home directory. If someone can figure this out I will update this document!!!!!!

Yugabyte

• Install a local copy and configure as needed - there is a configuration file that includes the path for data and logs
• I like to include the binaries in a path statement to be able to run simple from any path
• Examples: export PATH=$PATH:/market/db/yugabyte-2.21.0.1/bin and export CURIO_DB_HOST=192.168.1.96
• Initialize the database `yugabyted start --advertise_address 192.168.1.96 NOTE: use your LAN IP the database will install into your ~/home directory
• Verify it is running yugabyted status
• Go to the Yugabyte portal based on your machine IP address: http://192.168.1.96:15433/

Lotus node

• Install a local Lotus node
• Download and sync the chain
• Start Lotus
• Export the chain similar to export FULLNODE_API_INFO=eyJhbGc...[hidden]:/ip4/127.0.0.1/tcp/1234/http
• Create at least two wallets: an owner wallet and a worker (BLS type) wallet
• Fund wallets with FIL and back up private keys!
• lotus wallet list -i

Curio

• Install Curio from the Github repo
• Run curio guided-setup
• Run curio run - notice the logs - expect to see a number of errors until final configuration
• The below assumes you created directories at /seal/worker and /store using proper sizes
• Run curio cli storage attach --init --seal --max-storage 4000000000000 /seal/worker (initializes your sealing repo for 4TB)
• Run curio cli storage attach --init --store --max-storage 4000000000000 /store (initializes your storage repo for 4 TB)
• If you have not already created a storage path json (storage.json) do that now and put in your storage repo
• The last step may take a while for the parameters to download and verify - be very patient!
• Run curio run --layers=gui,post,seal --name MyMiner --storage-json /store/storage.json
• Go to Curio portal based on your Curio IP address: http://192.168.1.96:4701/
• To reduce log noise run curio cli log set-level --system stores info
• Finally test a pledge of a new sector curio seal start --actor t0118948 --cc --now (put in your minerID)

Boost

• Download and install boost
• Enable the Boost adapter in your base layer with your MinerID a Curio miner port t01203456:127.0.0.1:32100 (where the port number is unique)
• Run the boost connector to Yugabyte nohup boostd-data run yugabyte --hosts 192.168.1.96 --connect-string="postgresql://yugabyte:[email protected]:5433?sslmode=disable" --addr 0.0.0.0:8044 &
• Run curio market rpc-info --layers base use the output for [miner api] below
• Initialize the Boost server

boostd --boost-repo=/market/.boost --vv init \
--api-sector-index=[miner api] \
--api-sealer=[miner api] \
--wallet-publish-storage-deals=[wallet address] \
--wallet-deal-collateral=[wallet address] \
--max-staging-deals-bytes=1099511627776

OPTIONS:
--api-sealer value miner/sealer API info (lotus-miner auth api-info --perm=admin)
--api-sector-index value miner sector Index API info (lotus-miner auth api-info --perm=admin)
--wallet-publish-storage-deals value wallet to be used for PublishStorageDeals messages
--wallet-deal-collateral value wallet to be used for deal collateral
--max-staging-deals-bytes value max size for staging area in bytes (default: 0)

• Next edit your .boost/config.toml file for libp2p and other settings for deals and retrievals
• Enable Yugabyte to index deals in the [LocalIndexDirectory.Yugabyte] section and add connect string
• Uncomment and edit section [LocalIndexDirectory] ServiceApiInfo = "ws://127.0.01:8044"
• Run boostd and if desired direct logs: nohup boostd run > /market/logs/boost.log 2>&1 &

Stopping the system

1. [boost - tba]
2. curio cli stop
3. lotus daemon stop
4. yugabyted stop

Starting the system

1. yugabyted start

2. yugabyted status

3. nohup lotus daemon > /store/logs/lotus.log 2>&1 &

4. tail -f /store/logs/lotus.log

5. lotus sync wait

6. curio run --layers=gui,post,seal --name MyMinerName

7. curio cli log set-level --system stores info

8. Start Boost data connector nohup boostd-data run yugabyte --hosts 192.168.1.96 --connect-string="postgresql://yugabyte:[email protected]:5433?sslmode=disable" --addr 0.0.0.0:8044 &

9. Start Boost nohup boostd run > /market/logs/boost.log 2>&1 &