cheqduser will be created. By default,
HOMEdirectory for the user is
/home/cheqd, but it can be changed by setting
CHEQD_HOME_DIRenvironment variable before running
dpkgcommand. Additionnally, a custom logging directory can also be defined by passing the environment variable
cheqduser before managing node. By default, the node stores configuration files in the home directory for the user that initialises the node. By switching to the special
cheqdsystem user, you can ensure that the configuration files are stored in the system app data directories configured by the Debian package.
genesis.jsonfile for the relevant persistent chain and put it in the
seedswith a comma separated list of seed node addresses specified in
seeds.txtfor the relevant persistent chain.
SEEDSvariable is defined, pass the values to the
cheqd-noded configuretool to set it in the configuration file.
minimum-gas-pricesparameter if you want to use custom value. The default is
external-addressproperty which defines the externally reachable address. This can be defined using either IP address or DNS name followed by the P2P port (Default: 26656).
external-addressproperty, the node will report a private IP address from its own host network interface as its
remote_ip, which will be unreachable from the outside world. The node still works in this configuration, but only with limited unidirectional connectivity.
exitto logout and then attempt to execute this as a privileged user (with
sudoprivileges or as root user, if necessary).
cheqd-nodedservice is running. If successfully started, the status output should return
Active: active (running)
cheqd-nodeddaemon is active and running, check that the node is connected to the cheqd testnet and catching up with the latest updates on the ledger.
latest_block_heightand note the value. Execute the status command above a few times and make sure the value of
latest_block_heighthas increased each time.
catching_upreturns the output
cheqd-noded status --node <rpc-address>