CLI Commands for aiozd

Useful CLI Command - aiozd

AIOZ Network Daemon

aiozd is the tool that enables you to interact with the node that runs on the AIOZ Network, whether you run it yourself or not. Let us set it up properly. In order to install it, follow the installation procedure.

Setting up aiozd

The main command used to set up aiozd is the following:

aiozd config <flag> <value>

It allows you to set a default value for each given flag.

First, set up the address of the full-node you want to connect to:

aiozd config node <host>:<port>
# example: aiozd config node

If you run your own full-node, just use tcp://localhost:26657 as the address.

Then, let us set the default value of the --trust-node flag:

aiozd config trust-node true
# Set to true if you trust the full-node you are connecting to, false otherwise

Finally, let us set the chain-id of the blockchain we want to interact with:

aiozd config chain-id aioz_168-1


Key Types

There are three types of key representations that are used:

  • aioz
    • Derived from account keys generated by aiozd keys add
    • Used to receive funds
    • e.g. 0xB2ccdDC88A5f8e37d05C0701C3703069d218CD70
  • aiozvaloper
    • Used to associate a validator to it's operator
    • Used to invoke staking commands
    • e.g. 0x4E7Bd7Dd073d7c422C54DB7637E14b535Adc92c8
  • aiozpub
    • Derived from account keys generated by aiozd keys add
    • e.g. aiozpub1zcjduc3q7fu03jnlu2xpl75s2nkt7krm6grh4cc5aqth73v0zwmea25wj2hsqhlqzm
  • aiozvalconspub
    • Generated when the node is created with aiozd init.
    • Get this value with aiozd tendermint show-validator
    • e.g. aiozvalconspub1zcjduepq0ms2738680y72v44tfyqm3c9ppduku8fs6sr73fx7m666sjztznqzp2emf

Migrate Keys From Legacy On-Disk Keybase To OS Built-in Secret Store

Older versions of aiozd used store keys in the user's home directory. If you are migrating from an old version of aiozd you will need to migrate your old keys into your operating system's credentials storage by running the following command:

aiozd keys migrate

The command will prompt for every passphrase. If a passphrase is incorrect, it will skip the respective key.

Generate Keys

You'll need an account private and public key pair (a.k.a. sk, pk respectively) to be able to receive funds, send txs, bond tx, etc.

To generate a new ethsecp256k1 key:

aiozd keys add <account_name>

The output of the above command will contain a seed phrase. It is recommended to save the seed phrase in a safe place so that in case you forget the password of the operating system's credentials store, you could eventually regenerate the key from the seed phrase with the following command:

aiozd keys add --recover

If you check your private keys, you'll now see <account_name>:

aiozd keys show <account_name>

View the validator operator's address via:

aiozd keys show <account_name> --bech=val

You can see all your available keys by typing:

aiozd keys list

View the validator pubkey for your node by typing:

aiozd tendermint show-validator

Note that this is the Tendermint signing key, not the operator key you will use in delegation transactions.

Generate Multisig Public Keys

You can generate and print a multisig public key by typing:

aiozd keys add --multisig=name1,name2,name3[...] --multisig-threshold=K new_key_name

K is the minimum number of private keys that must have signed the transactions that carry the public key's address as signer.

The --multisig flag must contain the name of public keys that will be combined into a public key that will be generated and stored as new_key_name in the local database. All names supplied through --multisig must already exist in the local database. Unless the flag --nosort is set, the order in which the keys are supplied on the command line does not matter, i.e. the following commands generate two identical keys:

aiozd keys add --multisig=foo,bar,baz --multisig-threshold=2 multisig_address
aiozd keys add --multisig=baz,foo,bar --multisig-threshold=2 multisig_address

Multisig addresses can also be generated on-the-fly and printed through the which command:

aiozd keys show --multisig-threshold K name1 name2 name3 [...]

For more information regarding how to generate, sign and broadcast transactions with a multi signature account see Multisig Transactions.

Tx Broadcasting

When broadcasting transactions, aiozd accepts a --broadcast-mode flag. This flag can have a value of sync (default), async, or block, where sync makes the client return a CheckTx response, async makes the client return immediately, and block makes the client wait for the tx to be committed (or timing out).

It is important to note that the block mode should not be used in most circumstances. This is because broadcasting can timeout but the tx may still be included in a block. This can result in many undesirable situations. Therefore, it is best to use sync or async and query by tx hash to determine when the tx is included in a block.

Fees & Gas

Each transaction may either supply fees or gas prices, but not both.

Validator's have a minimum gas price (multi-denom) configuration and they use this value when when determining if they should include the transaction in a block during CheckTx, where gasPrices >= minGasPrices. Note, your transaction must supply fees that are greater than or equal to any of the denominations the validator requires.

Note: With such a mechanism in place, validators may start to prioritize txs by gasPrice in the mempool, so providing higher fees or gas prices may yield higher tx priority.


aiozd tx bank send ... --fees=50000000000000attoaioz


aiozd tx bank send ... --gas-prices=1000000000attoaioz


Get Tokens

On a testnet, getting tokens is usually done via a faucet.

Query Account Balance

After receiving tokens to your address, you can view your account's balance by typing:

aiozd query account <account_aioz>

Note: When you query an account balance with zero tokens, you will get this error: No account with address <account_aioz> was found in the state. This can also happen if you fund the account before your node has fully synced with the chain. These are both normal.

Send Tokens

The following command could be used to send coins from one account to another:

aiozd tx bank send <sender_key_name_or_address> <recipient_address> 10faucetToken \

Note: The amount argument accepts the format <value|coin_name>.


Note: You may want to cap the maximum gas that can be consumed by the transaction via the --gas flag. If you pass --gas=auto, the gas supply will be automatically estimated before executing the transaction. Gas estimate might be inaccurate as state changes could occur in between the end of the simulation and the actual execution of a transaction, thus an adjustment is applied on top of the original estimate in order to ensure the transaction is broadcasted successfully. The adjustment can be controlled via the --gas-adjustment flag, whose default value is 1.0.

Now, view the updated balances of the origin and destination accounts:

aiozd query account <account_aioz>
aiozd query account <destination_aioz>

You can also check your balance at a given block by using the --block flag:

aiozd query account <account_aioz> --block=<block_height>

You can simulate a transaction without actually broadcasting it by appending the --dry-run flag to the command line:

aiozd tx bank send <sender_key_name_or_address> <destination_aiozaccaddr> 10faucetToken \
  --chain-id=<chain_id> \

Furthermore, you can build a transaction and print its JSON format to STDOUT by appending --generate-only to the list of the command line arguments:

aiozd tx bank send <sender_address> <recipient_address> 10faucetToken \
  --chain-id=<chain_id> \
  --generate-only > unsignedSendTx.json
aiozd tx sign \
  --chain-id=<chain_id> \
  --from=<key_name> \
  unsignedSendTx.json > signedSendTx.json

Note: The --generate-only flag prevents aiozd from accessing the local keybase. Thus when such flag is supplied <sender_key_name_or_address> must be an address.

You can validate the transaction's signatures by typing the following:

aiozd tx sign --validate-signatures signedSendTx.json

You can broadcast the signed transaction to a node by providing the JSON file to the following command:

aiozd tx broadcast --node=<node> signedSendTx.json

Query Transactions

Matching a Set of Events

You can use the transaction search command to query for transactions that match a specific set of events, which are added on every transaction.

Each event is composed by a key-value pair in the form of {eventType}.{eventAttribute}={value}. Events can also be combined to query for a more specific result using the & symbol.

You can query transactions by events as follows:

aiozd query txs --events='message.sender=0x...'

And for using multiple events:

aiozd query txs --events='message.sender=0x...&message.action=withdraw_delegator_reward'

The pagination is supported as well via page and limit:

aiozd query txs --events='message.sender=0x...' --page=1 --limit=20

Note: The action tag always equals the message type returned by the Type() function of the relevant message.

You can find a list of available events on each of the AIOZ Network modules.

Matching a Transaction's Hash

You can also query a single transaction by its hash using the following command:

aiozd query tx [hash]



To unjail your jailed validator

aiozd tx slashing unjail --from <validator-operator-addr>

Signing Info

To retrieve a validator's signing info:

aiozd query slashing signing-info <validator-pubkey>

Query Parameters

You can get the current slashing parameters via:

aiozd query slashing params


You can query for the minting/inflation parameters via:

aiozd query minting params

To query for the current inflation value:

aiozd query minting inflation

To query for the current annual provisions value:

aiozd query minting annual-provisions


Set up a Validator

Please refer to the Validator Setup section for a more complete guide on how to set up a validator-candidate.

Delegate to a Validator

On the mainnet, you can delegate aioz to a validator. These delegators can receive part of the validator's fee revenue.

Query Validators

You can query the list of all validators of a specific chain:

aiozd query staking validators

If you want to get the information of a single validator you can check it with:

aiozd query staking validator <account_aiozval>

Bond Tokens

On the AIOZ Network mainnet, we delegate attoaioz, where 1aioz = 1000000000000000000attoaioz. Here's how you can bond tokens to a testnet validator (i.e. delegate):

aiozd tx staking delegate \
  --amount=10000000000000000000attoaioz \
  --validator=<validator> \
  --from=<key_name> \

<validator> is the operator address of the validator to which you intend to delegate. If you are running a local testnet, you can find this with:

aiozd keys show [name] --bech val

where [name] is the name of the key you specified when you initialized aiozd.

While tokens are bonded, they are pooled with all the other bonded tokens in the network. Validators and delegators obtain a percentage of shares that equal their stake in this pool.

Query Delegations

Once submitted a delegation to a validator, you can see it's information by using the following command:

aiozd query staking delegation <delegator_addr> <validator_addr>

Or if you want to check all your current delegations with disctinct validators:

aiozd query staking delegations <delegator_addr>

Unbond Tokens

If for any reason the validator misbehaves, or you just want to unbond a certain amount of tokens, use this following command.

aiozd tx staking unbond \
  <validator_addr> \
  10aioz \
  --from=<key_name> \

The unbonding will be automatically completed when the unbonding period has passed.

Query Unbonding-Delegations

Once you begin an unbonding-delegation, you can see it's information by using the following command:

aiozd query staking unbonding-delegation <delegator_addr> <validator_addr>

Or if you want to check all your current unbonding-delegations with disctinct validators:

aiozd query staking unbonding-delegations <account_aioz>

Additionally, as you can get all the unbonding-delegations from a particular validator:

aiozd query staking unbonding-delegations-from <account_aiozval>

Redelegate Tokens

A redelegation is a type delegation that allows you to bond illiquid tokens from one validator to another:

aiozd tx staking redelegate \
  <src-validator-operator-addr> \
  <dst-validator-operator-addr> \
  10aioz \
  --from=<key_name> \

Here you can also redelegate a specific shares-amount or a shares-fraction with the corresponding flags.

The redelegation will be automatically completed when the unbonding period has passed.

Query Redelegations

Once you begin an redelegation, you can see it's information by using the following command:

aiozd query staking redelegation <delegator_addr> <src_val_addr> <dst_val_addr>

Or if you want to check all your current unbonding-delegations with distinct validators:

aiozd query staking redelegations <account_aioz>

Additionally, as you can get all the outgoing redelegations from a particular validator:

  aiozd query staking redelegations-from <account_aiozval>

Query Parameters

Parameters define high level settings for staking. You can get the current values by using:

aiozd query staking params

With the above command you will get the values for:

  • Unbonding time
  • Maximum numbers of validators
  • Coin denomination for staking

All these values will be subject to updates though a governance process by ParameterChange proposals.

Query Pool

A staking Pool defines the dynamic parameters of the current state. You can query them with the following command:

aiozd query staking pool

With the pool command you will get the values for:

  • Not-bonded and bonded tokens
  • Token supply
  • Current annual inflation and the block in which the last inflation was processed
  • Last recorded bonded shares
Query Delegations To Validator

You can also query all of the delegations to a particular validator:

  aiozd query delegations-to <account_aiozval>


Governance is the process from which users in the AIOZ Network can come to consensus on software upgrades, parameters of the mainnet, signaling mechanisms through text proposals, or proposing new validator. This is done through voting on proposals, which will be submitted by AIOZ holders on the mainnet.

Some considerations about the voting process:

  • Voting is done by bonded AIOZ validators on a 1 bonded AIOZ 1 vote basis
  • Delegators inherit the vote of their validator
  • Votes are tallied at the end of the voting period (2 weeks on mainnet) where each address can vote multiple times to update its Option value (paying the transaction fee each time), only the most recently cast vote will count as valid
  • Voters can choose between options Yes, No, NoWithVeto and Abstain
  • At the end of the voting period, a proposal is accepted iff:
    • (YesVotes / (YesVotes+NoVotes+NoWithVetoVotes)) > 1/2
    • (NoWithVetoVotes / (YesVotes+NoVotes+NoWithVetoVotes)) < 1/3
    • ((YesVotes+NoVotes+NoWithVetoVotes) / totalBondedStake) >= quorum

For more information about the governance process and how it works, please check out the Governance module specification (opens in a new tab).

Create a Governance Proposal

In order to create a governance proposal, you must submit an initial deposit along with a title and description. Various modules outside of governance may implement their own proposal types and handlers (eg. parameter changes), where the governance module itself supports Text proposals. Any module outside of governance has it's command mounted on top of submit-proposal.

To submit a Text proposal:

aiozd tx gov submit-proposal \
  --title=<title> \
  --description=<description> \
  --type="Text" \
  --deposit="1000aioz" \
  --from=<name> \

You may also provide the proposal directly through the --proposal flag which points to a JSON file containing the proposal.

To submit a parameter change proposal, you must provide a proposal file as its contents are less friendly to CLI input:

aiozd tx gov submit-proposal param-change <path/to/proposal.json> \
  --from=<name> \

Where proposal.json contains the following:

  "title": "Param Change",
  "description": "Update max validators",
  "changes": [
      "subspace": "staking",
      "key": "MaxValidators",
      "value": 36
  "deposit": "1000aioz"

To submit a validator proposal:

aiozd tx gov submit-proposal create-validator <path/to/proposal.json> \
  --from=<name> \

Where proposal.json contains the following:

  "title": "Propose new validator",
  "description": "validator information",
  "validator": {...},
  "deposit": "1000aioz"

Query Proposals

Once created, you can now query information of the proposal:

aiozd query gov proposal <proposal_id>

Or query all available proposals:

aiozd query gov proposals

You can also query proposals filtered by voter or depositor by using the corresponding flags.

To query for the proposer of a given governance proposal:

aiozd query gov proposer <proposal_id>

Increase Deposit

In order for a proposal to be broadcasted to the network, the amount deposited must be above a minDeposit value (initial value: 1000aioz). If the proposal you previously created didn't meet this requirement, you can still increase the total amount deposited to activate it. Once the minimum deposit is reached, the proposal enters voting period:

aiozd tx gov deposit <proposal_id> "10000000000000000000attoaioz" \
  --from=<name> \

NOTE: Proposals that don't meet this requirement will be deleted after MaxDepositPeriod is reached.

Query Deposits

Once a new proposal is created, you can query all the deposits submitted to it:

aiozd query gov deposits <proposal_id>

You can also query a deposit submitted by a specific address:

aiozd query gov deposit <proposal_id> <depositor_address>

Vote on a Proposal

After a proposal's deposit reaches the MinDeposit value, the voting period opens. Bonded AIOZ validators can then cast vote on it:

aiozd tx gov vote <proposal_id> <Yes/No/NoWithVeto/Abstain> \
  --from=<name> \
Query Votes

Check the vote with the option you just submitted:

aiozd query gov vote <proposal_id> <voter_address>

You can also get all the previous votes submitted to the proposal with:

aiozd query gov votes <proposal_id>

Query proposal tally results

To check the current tally of a given proposal you can use the tally command:

aiozd query gov tally <proposal_id>

Query Governance Parameters

To check the current governance parameters run:

aiozd query gov params

To query subsets of the governance parameters run:

aiozd query gov param voting
aiozd query gov param tallying
aiozd query gov param deposit

Fee Distribution

Query Distribution Parameters

To check the current distribution parameters, run:

aiozd query distribution params

Query distribution Community Pool

To query all coins in the community pool which is under Governance control:

aiozd query distribution community-pool

Query outstanding rewards

To check the current outstanding (un-withdrawn) rewards, run:

aiozd query distribution outstanding-rewards

Query Validator Commission

To check the current outstanding commission for a validator, run:

aiozd query distribution commission <validator_address>

Query Validator Slashes

To check historical slashes for a validator, run:

aiozd query distribution slashes <validator_address> <start_height> <end_height>

Query Delegator Rewards

To check current rewards for a delegation (were they to be withdrawn), run:

aiozd query distribution rewards <delegator_address> <validator_address>

Query All Delegator Rewards

To check all current rewards for a delegation (were they to be withdrawn), run:

aiozd query distribution rewards <delegator_address>

Multisig Transactions

Multisig transactions require signatures of multiple private keys. Thus, generating and signing a transaction from a multisig account involve cooperation among the parties involved. A multisig transaction can be initiated by any of the key holders, and at least one of them would need to import other parties' public keys into their Keybase and generate a multisig public key in order to finalize and broadcast the transaction.

For example, given a multisig key comprising the keys p1, p2, and p3, each of which is held by a distinct party, the user holding p1 would require to import both p2 and p3 in order to generate the multisig account public key:

aiozd keys add \
  p2 \
aiozd keys add \
  p3 \
aiozd keys add \
  p1p2p3 \
  --multisig-threshold=2 \

A new multisig public key p1p2p3 has been stored, and its address will be used as signer of multisig transactions:

aiozd keys show --address p1p2p3

You may also view multisig threshold, pubkey constituents and respective weights by viewing the JSON output of the key or passing the --show-multisig flag:

aiozd keys show p1p2p3 -o json
aiozd keys show p1p2p3 --show-multisig

The first step to create a multisig transaction is to initiate it on behalf of the multisig address created above:

aiozd tx bank send 0xD4e34679216523cAbE3d198dcf47f9A268755523 1000000000attoaioz \
  --from=<multisig_address> \
  --generate-only > unsignedTx.json

The file unsignedTx.json contains the unsigned transaction encoded in JSON. p1 can now sign the transaction with its own private key:

aiozd tx sign \
  unsignedTx.json \
  --multisig=<multisig_address> \
  --from=p1 \

Once the signature is generated, p1 transmits both unsignedTx.json and p1signature.json to p2 or p3, which in turn will generate their respective signature:

aiozd tx sign \
  unsignedTx.json \
  --multisig=<multisig_address> \
  --from=p2 \

p1p2p3 is a 2-of-3 multisig key, therefore one additional signature is sufficient. Any the key holders can now generate the multisig transaction by combining the required signature files:

aiozd tx multisign \
  unsignedTx.json \
  p1p2p3 \
  p1signature.json p2signature.json > signedTx.json

The transaction can now be sent to the node:

aiozd tx broadcast signedTx.json

Shells Completion Scripts

Completion scripts for popular UNIX shell interpreters such as Bash and Zsh can be generated through the completion command, which is available for both aiozd and aiozd.

If you want to generate Bash completion scripts run the following command:

aiozd completion > aiozd_completion
aiozd completion > aiozcli_completion

If you want to generate Zsh completion scripts run the following command:

aiozd completion --zsh > aiozd_completion
aiozd completion --zsh > aiozcli_completion

Note: On most UNIX systems, such scripts may be loaded in .bashrc or .bash_profile to enable Bash autocompletion:

echo '. aiozd_completion' >> ~/.bashrc
echo '. aiozcli_completion' >> ~/.bashrc

Refer to the user's manual of your interpreter provided by your operating system for information on how to enable shell autocompletion.