Configure the Xion Daemon

How to initialize and configure the xiond binary

As an application-specific blockchain using the Cosmos SDK, we benefit from its extensive configuration options.

⚠️ Custom Configuration

The configuration in this guide is provided as-is, with no guarantee of any kind.

You are highly encouraged to tweak the Cosmos SDK configuration values to accommodate your specific environment and use case.

The Cosmos SDK documentation is a good place to start exploring the different options.

Initialize the Xion Daemon

• As is the case for most Cosmos-based chains, the daemon is initialized like so:

$ xiond init my-awesome-moniker \
    --chain-id xion-testnet-2 \
    --home /tmp/node

Refer to the config directory

• The xiond init command will output this structure to the specified --home:

.                                   # /tmp/node
  |- data                           # Contains the databases used by the node.
  |- config/
      |- app.toml                   # Application-related configuration file.
      |- config.toml                # Tendermint-related configuration file.
      |- genesis.json               # The genesis file.
      |- node_key.json              # Private key to use for node authentication in the p2p protocol.
      |- priv_validator_key.json    # Private key to use as a validator in the consensus protocol.

⚠️ Node Keys

Take note of the node_key.json and priv_validator_key.jsonfiles.

The combination of these two private keys serves to uniquely identify your node on the Xion Network. If the purpose of your node is ephemeral, such that it can be discarded with no adverse effects, then these files can be discarded and regenerated at will.

However, if the purpose of your node is persistent, such as running a Validator, then protecting and preserving these files becomes paramount.

app.toml

client.toml

config.toml