Configuring sagacli - A Deep Dive
sagacli
is a powerful CLI tool that is intended to offer end-to-end management of your private keys, accounts and chainlets.
It is imperative that sagacli
be configured correctly in order for you to get the most out of the tool, and avoid unnecessary errors.
To view the current config, type:
The table below provides an in-depth explanation of each configuration setting.
loglevel
This setting determines the verbosity of logs produced. Possible values are debug
, trace
, info
(default), error
and critical
trace
info
controller
Controller accepts gRPC requests from sagacli
and acts as the gateway for processing commands. Note: This is a critical setting and must be set correctly in order for sagacli
to function properly
controller.cassio-prod-sp1.sp1.sagarpc.io:19090
https://controller.sp1.sagarpc.io
output
This controls the formatting of output from sagacli
commands. Possible values are text
and json
json
text
keyring-backend
This setting indicates the type of keyring sagacli
will use for storing private keys
test
file
network-rpc
This setting specifies the endpoint for connecting to the Saga Platform Chain, which serves as the system of record for chainlets launched, as well as their current status. Note: This is a critical setting and must be set correctly in order for sagacli
to function properly
tcp://spc.cassio-prod-sp1.sp1.sagarpc.io:26657
https://spc.sp1.sagarpc.io
from
This setting specifies the key to be used as the default key when signing transactions. You do not need to have this set in order to be able to use sagacli
and having this set is a convenience feature
mykey1
none
platform-chain-id
This setting specifies the chain-id
of the Saga Platform Chain. Note: This is a critical setting and must be set correctly in order for sagacli
to function properly
spc-testnet-1
spc-testnet-1
denom
This setting specifies the token denomination symbol being used by the Saga Platform Chain. It is best to leave this to the default value
stake
tsaga
broadcast-mode
This controls the submission of transactions to the Saga Platform Chain and whether sagacli
should wait for the transaction to be checked and committed in a block before the command returns. Possible values are sync
and async.
IMPORTANT: It is not recommended that this value be changed. If you do have a use-case for changing the default value, please contact the Saga team before making any changes
sync
sync
ledger
This setting enables the use of a connected ledger device for signing transactions. If you have an HD wallet or other such hardware device used to store your private keys, you can use this setting to force each transaction to be signed via the ledger device
true
false
Last updated