# Interacting with Xion Chain using Xion Daemon `xiond` is the command-line interface (CLI) daemon for interacting with the **XION blockchain**. It allows users to manage accounts, send transactions, query blockchain data, and operate validator nodes. ## Prerequisites Before proceeding, ensure that `xiond` is installed on your system. Follow the setup in: * [Setting up your Local Smart Contract Development Environment for XION](https://docs.burnt.com/xion/developers/computation/local-development/setting-up-env/installation-prerequisites-setup-local-environment) To verify installation, run: ```sh xiond ``` If installed correctly, you should see command output similar to: ``` xion daemon (server) Usage: xiond [command] ``` This output confirms that `xiond` is available. Typical command groups include: * `keys` - manage local keys * `query` - read chain state * `tx` - broadcast transactions * `status` - inspect node status * `start` - run a local node process Use `xiond [command] --help` for command-specific details. ## Command reference quick list Below is a practical command map for day-to-day development and operations. | Command group | Purpose | Example | | ----------------------- | -------------------------------------------------------- | ----------------------------------------------- | | `keys` | Manage local keyring entries | `xiond keys list` | | `query` | Read on-chain data from an RPC node | `xiond query bank balances --node ` | | `tx` | Build, sign, and broadcast transactions | `xiond tx bank send ...` | | `status` | Check remote node status | `xiond status --node ` | | `version` | Show binary version | `xiond version` | | `config` | Manage local CLI/app config | `xiond config --help` | | `comet` | CometBFT-related subcommands | `xiond comet --help` | | `genesis` | Inspect or manage genesis state for local node workflows | `xiond genesis --help` | | `start` | Run a full node process | `xiond start` | | `init` | Initialize local node files | `xiond init ` | | `export` | Export app state to JSON | `xiond export --help` | | `rollback` | Roll back Cosmos SDK + CometBFT state by one height | `xiond rollback --help` | | `prune` | Prune local app history | `xiond prune --help` | | `snapshots` | Manage local snapshots | `xiond snapshots --help` | | `debug` | Debug-oriented utilities | `xiond debug --help` | | `rosetta` | Run Rosetta server mode | `xiond rosetta --help` | | `module-hash-by-height` | Query module hashes for a target height | `xiond module-hash-by-height --help` | ## Generate an account To execute transactions on-chain, you need at least one funded account. Key pairs include: * A **public key / address** used to receive funds. * A **private key** used to sign transactions. ### Generate a new key pair ```sh xiond keys add ``` Replace `` with a name you want to use locally. ### Retrieve a key ```sh xiond keys show ``` Useful key commands: ```sh # List all locally stored keys xiond keys list # Show account address only xiond keys show -a ``` ## Fund your account You can request testnet tokens with: * **Discord faucet** * **Web faucet**: [XION Faucet](https://faucet.xion.burnt.com/) For additional options, see: * [Requesting XION Testnet Tokens](https://docs.burnt.com/xion/developers/references/xion-testnet) For **mainnet** usage, fund your wallet from supported exchanges before broadcasting transactions. ## Connect to different XION networks For chain IDs and public RPC nodes, see: * [Public Endpoints & Resources](https://docs.burnt.com/xion/developers/references/public-endpoints-and-resources) When sending transactions to a non-local network, set both: * `--chain-id` for the target chain * `--node` for the RPC endpoint For queries, only `--node` is required. ### Example: Send tokens ```sh xiond tx bank send uxion \ --chain-id \ --node \ --from \ --gas-prices 0.025uxion \ --gas auto \ --gas-adjustment 1.3 \ -y ``` Expected successful output includes: ``` code: 0 txhash: ``` If `code` is non-zero, inspect `raw_log` for the failure reason. ### Example: Query balances ```sh xiond query bank balances --node ``` Typical query output: ``` balances: - amount: "1223782" denom: uxion pagination: total: "1" ``` ## Common workflows ### Check account sequence and account number before signing ```sh xiond query auth account --node ``` ### Estimate transaction before broadcasting ```sh xiond tx bank send uxion \ --chain-id \ --node \ --from \ --gas auto \ --gas-adjustment 1.3 \ --gas-prices 0.025uxion \ --dry-run ``` ### Query a transaction by hash ```sh xiond query tx --node ``` ## Troubleshooting * `insufficient fees`: raise `--gas-prices` or verify fee denomination for the target network. * `account sequence mismatch`: query account again, then retry with updated sequence (or avoid parallel tx from same account). * `wrong chain-id`: confirm `--chain-id` matches the node endpoint you are using. * `connection refused / timeout`: verify `--node` RPC URL and network reachability. * non-zero `code` in tx result: inspect `raw_log` to identify module-level failure reason. ## Next steps * [Deploying Your First Smart Contract on XION](https://docs.burnt.com/xion/developers/computation/local-development/deploy-a-cosmwasm-smart-contract) * [Xion Agent Toolkit Tutorial](https://docs.burnt.com/xion/developers/tools/xion-toolkit) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.burnt.com/xion/developers/tools/xiond-cli.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.