.png%3Falt%3Dmedia%26token%3De6bb9831-f128-47e4-93d6-29d42e36344a)
.png%3Falt%3Dmedia%26token%3De6bb9831-f128-47e4-93d6-29d42e36344a)
Comment on page
Configure Saga CLI
The
sagacli executable communicates with our Pegasus server applications securely over HTTPS. Before you can start using sagacli, you must configure it talk to the Saga Platform Chain as well as the Saga Controller.If you've used sagacli in the past on Cassiopeia, we recommend carefully verifying that all of the config parameters below are set correctly otherwise your CLI might fail.
Execute the following commands provided below to configure
sagacli:sagacli config network-rpc https://spc.testnet-sp1.sagarpc.io
sagacli config controller https://controller.testnet-sp1.sagarpc.io
sagacli config platform-chain-id spc-testnet-1
sagacli config denom upsaga
sagacli config broadcast-mode sync
sagacli config faucet https://zgl952jrej.execute-api.us-east-1.amazonaws.com/Prod/fund
Ok, now that we have configured the endpoints, it's time to check if they actually work. To do that, run the following command:
sagacli status
You should see the following output:
Saga Platform Chain Controller
------------------- ----------
Online Online
IMPORTANT: If either of the two applications indicate a value of
false, the configuration was not successful. Check your local network connection to ensure that you are connected to the internet, and that your firewall application isn't blocking outgoing traffic over HTTPS.To launch your very first chainlet, there are a few easy steps you will need to go through. Broadly:
- Your
sagacliaccount will receive airdropped tokens. If you do not have tokens, please request them via the Getting Access page
You can access the help for any of the commands by running
sagacli [command?] [subcommand?] --help.