Migrating FCP to Swan Mainnet
Now all CPs can migrate to the mainnet to participate in Swan Mainnet Campaign
Last updated
Now all CPs can migrate to the mainnet to participate in Swan Mainnet Campaign
Last updated
If you are deploying for the first time, you can follow the instructions in the latest version: Swan Chain Computing Provider v1.0.2:
Update resource-exporter
to the latest version v11.3.0
: Follow the instructions in this issue:
Specify a new CP_PATH:
Download the mainnet version of the computing-provider:
Verify CP version:
Ensure it shows version 1.0.2+mainnet
.
Initialize CP repo and update configuration: Refer to
Note:
No need to modify parts of the configuration file with default values.
The "contract address" is now built into the program, no separate configuration is needed.
The default configuration file template can be found .
Initialize a Wallet and Deposit SwanETH: Refer to .
Initialization CP Account: Refer to .
Collateral SWANC for FCP: Refer to .
Withdraw SWANC from FCP: Refer to .
Start the Computing Provider: Refer to .
Different Compilation Method:
Mainnet version: make mainnet
Testnet version: make testnet
Different Collateral:
Different Task Distribution Platform:
Funds Operations:
ECP (Edge Computing Provider):
The new version will support ECP running independently or with FCP, allowing FCP to earn both rewards simultaneously.
ECP tasks are more frequent but offer lower rewards.
In the mainnet, FCP collateral is SwanC. Each task requires 5 SwanC collateral (claim from ).
Mainnet task distribution platform: , same as the testnet lagrangeDAO platform.
Refer to .
For any questions, refer to the detailed documentation on the .