Configure wasp-cli
You can use these step-by-step instructions on how to use wasp-cli to interact with Wasp nodes on the Hornet network.
Download wasp-cli
Download the latest wasp-cli binary from the repo releases page.
(For ease of use, it is recommended to add wasp-cli to your system PATH).
Configuration
You can create a basic default configuration by running:
wasp-cli init
This command will create a configuration file named wasp-cli.json in ~/.wasp-cli/wasp-cli.json (you can change the default with the -c, --config flag).
By default wasp-cli will store the seed in your OS keychain. You can change this behavior by running
wasp-cli wallet-provider (keychain, sdk_ledger, sdk_stronghold) [flags]
If you use a version older then 1.0.3 your seed is still stored as plain text. You can migrate to the keychain by using the following command:
wasp-cli wallet-migrate (keychain) [flags]
After this, you will need to tell the wasp-cli the location of the Hornet nodeA community-developed IOTA Node written in the Go programming language. Additionally, the coordinator runs as a plugin via Hornet. and the committee of Wasp nodes:
wasp-cli set l1.apiaddress http://localhost:14265
# the faucet only exists for test networks
wasp-cli set l1.faucetaddress http://localhost:8091
# You can add as many nodes as you'd like
wasp-cli wasp add wasp-0 127.0.0.1:9090
wasp-cli wasp add wasp-1 127.0.0.1:9091
If you configure the Wasp node to use JWT authentication, you will need to log in after you save the configuration.
wasp-cli login