Step-by-step instructions on how to use wasp-cli to interact with Wasp nodes on the Hornet network.
After going through the instructions on Running a node, you should have the
available in your system.
You can create a basic default configuration by running:
This command will create a configuration file named
wasp-cli.json in the current directory.
After this, you will need to tell the
wasp-cli the location of the Hornet node and the committee of Wasp nodes:
wasp-cli set l1.apiaddress http://localhost:14265
wasp-cli set l1.faucetaddress http://localhost:8091
wasp-cli set wasp.0.api 127.0.0.1:9090
wasp-cli set wasp.0.nanomsg 127.0.0.1:5550
wasp-cli set wasp.0.peering 127.0.0.1:4000
## You can add as many nodes as you like in your committee
wasp-cli set wasp.1.api 127.0.0.1:9091
wasp-cli set wasp.1.nanomsg 127.0.0.1:5551
wasp-cli set wasp.1.peering 127.0.0.1:4001
wasp-cli set wasp.N.api 127.0.0.1:9091
wasp-cli set wasp.N.nanomsg 127.0.0.1:5551
wasp-cli set wasp.N.peering 127.0.0.1:4001
Alternatively, you can edit the
wasp-cli.json file and include the desired server locations:
The Hornet api address:
The API/nanomsg/peering address for each Wasp node:
If you configure the Wasp node to use the experimental JWT authentication, you will need to log in after you save the configuration.