Provider
Last updated
Last updated
To become a provider in the grid trading market, you need to register your provider information, deploy and configure a local Kubernetes cluster, and start the backend program. Here is the step-by-step process:
Navigate to the frontend provider page and register by clicking the "Become A Provider" button.
Fill in the required information such as name, IP address, port, and domain name.
After completing the provider information registration, you need to configure your local Kubernetes cluster and set labels for each cluster node with the following steps:
Refer to the deployment method here: CSDN Blog Post.
Alternatively, you can deploy based on your own deployment experience.
On the frontend interface's "addnode" page, enter the node configuration and unit price information to complete the node registration.
A unique node ID will be automatically assigned for identifying this node within the provider.
Node IDs start incrementing from 0.
First, check the node ID on the frontend interface's node details page, then set labels for each node using the ID as the label. For example:
Replace nodename with the actual node name, and 0 with the actual node ID.
Download the backend program, startup script, and configuration files to your local machine.
Navigate to the directory where the backend program is located.
Import an existing wallet using the private key (sk
) with the following command:
Here, sk represents the provider wallet private key, and pw represents the wallet repository password.
Alternatively, you can create a new wallet using the init command.
Contact the official administrator to top up the provider wallet with gas fees and credits.
Update the http listen
port in the config.toml
file to the desired port for startup. For example, set it to 12347. This completes the specified sections of the backend program startup process in English within a Markdown document.
Execute the backend startup script with the following command:
Here, test indicates the use of a test chain contract; the specific value should be set according to the actual situation.
The operation logs are stored in the log file.