Subcommands

This section describes the subcommands available on JMESd.

`debug addr`

Changes an address from hex encoding to bech32.

Syntax

jmesd debug addr <address>

Example

jmesd debug addr jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm

`debug pubkey`

Decodes a pubkey from proto JSON and displays the address.

Syntax

jmesd debug pubkey <pubkey>

Example

jmesd debug pubkey '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AurroA7jvfPd1AadmmOvWM2rJSwipXfRf8yD6pLbA2DJ"}'

`debug raw-bytes`

Changes raw bytes to hex.

Syntax

jmesd debug raw-bytes <raw-bytes>

Example

jmesd debug raw-bytes [72 101 108 108 111 44 32 112 108 97 121 103 114 111 117 110 100]

`keys add`

Generates a public and private key pair for an account so that you can receive funds, send funds, create bonding transactions, and so on.

💡tip

For security purposes, run this command on an offline computer.

Syntax

jmesd keys add <your-key-name>

where <your-key-name> is the name of the account. It references the account number used to derive the key pair from the mnemonic. When you want to send a transaction, you will use this name to identify your account.

To specify the path (0, 1, 2, ...) you want to use to generate your account, you can append the optional --account flag. By default, account 0 is generated.

The command generates a 24-word mnemonic and saves the private and public keys for account 0 simultaneously. You are prompted to specify a passphrase that is used to encrypt the private key of account 0 on disk. Each time you want to send a transaction, this password is required. If you lose the password, you can always recover the private key by using the mnemonic phrase.

🔥danger

To prevent theft or loss of funds, ensure that you keep multiple copies of your mnemonic and store it in a secure place and that only you know how to access it. If someone is able to gain access to your mnemonic, they are able to gain access to your private keys and control the accounts associated with them.

💡tip

After you have triple-checked your mnemonic and safely stored it, you can delete bash history to ensure no one can retrieve it.

history -c
rm ~/.bash_history

To generate more accounts from the same mnemonic, run:

jmesd keys add <your-key-name> --recover --account 1

You are prompted to specify a passphrase and your mnemonic. To generate a different account, change the account number.

🔥danger

Do not use the same passphrase for multiple keys. Do not lose or share your mnemonic with anyone.

Example

jmesd keys add myAccount

In some cases, you might need to recover your key. If you have the mnemonic that was used to generate your private key, you can recover it and re-register your key. Issuing the following command will prompt you to enter your 24-word mnemonic.

Syntax

jmesd keys add <yourKeyName> --recover

`keys show`

Retrieves an address for a specified account. The address is prefixed by jmes-, for example jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc. To receive funds, you must give an account address to the sender.

Syntax

jmesd keys show <account-name>

Example

jmesd keys show myAccount

To show a validator's address, append the --bech=val flag to the end of the command statement, as shown in the following example:

jmesd keys show accountExample --bech=val

To show the validator consensus address that is generated when the node is created by jmesd init and the Tendermint signing key for the node, use the tendermint command, as shown in the following example:

jmesd tendermint show-address

`keys list`

Lists all your keys.

Syntax

jmesd keys list

`query authz grants`

Retrieves all existing grants between a granter and a grantee.

Syntax

jmesd query authz grants <granter-address> <grantee-address>

Example

jmesd query authz grants jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm

Additionally, the grants command can retrieve the specific grant between a granter and a grantee for a message type by appending the message type URL to the end of the command statement, as shown in the following example:

jmesd query authz grants jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm /cosmos.bank.v1beta1.MsgSend

`query bank balances`

Displays your account balance, account number, and sequence number (nonce).

Syntax

jmesd query bank balances <account-address>

Example

jmesd query bank balances jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

📝note

When you query an account balance that has zero tokens or you fund an account before your node has fully synced with the chain, this error message is sent:

No account with address <account-address> was found in the state.

`query bank denom-metadata`

Query the client metadata for coin denominations.

`query bank total`

Query the total supply of coins of the chain.

`query distribution rewards`

Checks the all the current outstanding rewards that have not been withdrawn.

Syntax

jmesd query distribution rewards

Check the current rewards earned by a specific delegator by appending the <delegator-address> at the end of the command statement, as shown in the following example:

jmesd query distribution rewards jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm

Check the current rewards earned by a delegator and restricted to one validator by appending the <delegator-address> followed by the <validator-address> at the end of the command statement, as shown in the following example:

jmesd query distribution rewards jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm jmes19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy

`query distribution commission`

Checks the current outstanding commission for a validator.

Syntax

jmesd query distribution commission <validator_address>

Example

jmesd query distribution commission jmes19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy

`query distribution slashes`

Checks historical slashes for a validator within a range of blocks.

Syntax

jmesd query distribution slashes <validator-address> <start-block-height> <end-block-height>

Example

jmesd query distribution slashes jmes19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy 25 300

`query distribution community-pool`

Checks all coins in the community pool.

Syntax

jmesd query distribution community-pool

`query distribution params`

Checks the current distribution parameters.

Syntax

jmesd query distribution params

The parameters are returned in YAML, as shown in the following example:

community_tax: "0.020000000000000000"
base_proposer_reward: "0.010000000000000000"
bonus_proposer_reward: "0.040000000000000000"
withdraw_addr_enabled: true

`query gov deposit`

Retrieves information about a single proposal deposit on a proposal by its identifier.

Syntax

jmesd query gov deposit <proposal-id> <depositor-address>

Example

jmesd query gov deposit 4 jmes1skjwj5whet0lpe65qaq4rpq03hjxlwd9nf39lk

`query gov deposits`

Retrieves all deposits submitted to a proposal after it is created.

Syntax

jmesd query gov deposits <proposal-id>

Example

jmesd query gov deposits 5

`query gov proposal`

Retrieves information about one proposal.

proposal retrieves information about one proposal.

Syntax

jmesd query gov proposal <proposal-id>

Example

jmesd query gov proposal 3

`query gov proposals`

Retrieves information about all available proposals.

Syntax

jmesd query gov proposals

Additionally, you can query proposals filtered by details, such as voter or depositor, by appending the corresponding flag and address at the end of the command statement, as shown in the following example:

jmesd query gov proposals --voter jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb

`query gov vote`

Retrieves information about a single vote by a specific voter.

Syntax

jmesd query gov vote <proposal-id> <voter-address>

Example

jmesd query gov vote 7 jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb

`query gov votes`

Retrieves all the votes submitted to the proposal.

Syntax

jmesd query gov votes <proposal-id>

Example

jmesd query gov votes 9

`query gov tally`

Retrieves the current tally for a specified proposal.

Syntax

jmesd query gov tally <proposal-id>

Example

jmesd query gov tally 4

`query gov param`

Retrieves all the parameters for the specified governance process.

Syntax

jmesd query gov param <process-type>

Example

jmesd query gov param voting

`query gov params`

Retrieves all the parameters for all governance processes.

Syntax

jmesd query gov params

The parameters are returned in the following format:

voting_params:
  voting_period: 5m0s
tally_params:
  quorum: "0.300000000000000000"
  threshold: "0.500000000000000000"
  veto: "0.334000000000000000"
deposit_parmas:
  min_deposit:
    - denom: ubjmes
      amount: "10000000"
  max_deposit_period: 48h0m0s

`query mint annual-provisions`

Retrieves the value of annual provisions.

Syntax

jmesd query mint annual-provisions

`query mint inflation`

Retrieves the current value of inflation.

Syntax

jmesd query mint inflation

`query mint params`

Retrieves the mint module's parameters.

Syntax

jmesd query mint params

Parameters are returned in the following format:

mint_denom: ubjmes
inflation_rate_change: "0.130000000000000000"
inflation_max: "0.200000000000000000"
inflation_min: "0.070000000000000000"
goal_bonded: "0.670000000000000000"
blocks_per_year: 6311520

`query slashing signing-info`

Retrieves a validator's signing info.

Syntax

jmesd query slashing signing-info <validator-consensus-public-key>

Example

jmesd query slashing signing-info jmesvalconspub1atjdueldlxwft8d4729pqhdhm3nlss0u4wx7wpeqb1zhjf8yr1tn7cgw2b4q4yv9na

`query slashing signing-infos`

Retrieves signing information of all validators.

Syntax

jmesd query slashing signing-infos

`query slashing params`

Retrieves the genesis parameters for the slashing module.

Syntax

jmesd query slashing params

The parameters are returned in the following format:

signed_blocks_window: 100
min_signed_per_window: "0.500000000000000000"
downtime_jail_duration: 10m0s
slash_fraction_double_sign: "0.050000000000000000"
slash_fraction_downtime: "0.010000000000000000"

`query staking delegation`

Retrieves delegation information for a validator.

Syntax

jmesd query staking delegation <delegator-address> <validator-address>

Example

jmesd query staking delegation jmes1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p jmesvaloper15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

`query staking delegations`

Retrieves delegations for a delegator on all validators.

Syntax

jmesd query staking delegations <delegator-address>

Example

jmesd query staking delegations jmes1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p

`query staking delegations-to`

Retrieves all of the delegations on a particular validator.

Syntax

jmesd query staking delegations-to <validator-address>

Example

jmesd query staking delegations-to jmesvaloper15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

`query staking historical-info`

Retrieves all historical information at a specified height.

Syntax

jmesd query staking historical-info <height>

Example

jmesd query staking historical-info 23

`query staking params`

Retrieves all staking parameters.

Syntax

jmesd query staking params

The parameters are returned in the following format:

unbonding_time: 504h0m0s
max_validators: 100
max_entries: 100
historical_entries: 0
bond_denom: ubjmes

`query staking pool`

Retrieves amounts stored in the staking pool.

Syntax

jmesd query staking pool

The following information is returned:

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 staking redelegation`

Retrieves redelegation information for an individual delegator between a source validator and a destination validator.

Syntax

jmesd query staking redelegation <delegator-address> <src-val-addr> <dst-val-addr>

Example

jmesd query staking redelegation jmes1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p jmesvaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm jmesvaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj

`query staking redelegations`

Retrieves all redelegation information for a delegator.

Syntax

jmesd query staking redelegations <delegator-address>

Example

jmesd query staking redelegations jmes1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p

`query staking redelegations-from`

Retrieves all the delegations that are redelegating from a specified validator:

Syntax

jmesd query staking redelegations-from <validator-address>

Example

jmesd query staking redelegations-from jmesvaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj

`query staking unbonding-delegation`

Retrieves information about unbonding delegations for a specified delegator and validator.

Syntax

jmesd query staking unbonding-delegation <delegator-address> <validator-address>

Example

jmesd query staking unbonding-delegation jmes1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p jmesvaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm

`query staking unbonding-delegations`

Retrieves all your current unbonding delegations for a specified delegator.

Syntax

jmesd query staking unbonding-delegations <delegator-address>

Example

jmesd query staking unbonding-delegations jmes1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p

`query staking unbonding-delegations-from`

Retrieves all the unbonding delegations from a specified validator.

Syntax

jmesd query staking unbonding-delegations-from <validator-address>

Example

jmesd query staking unbonding-delegations-from jmesvaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm

`query staking validators`

Retrieves the list of all registered validators.

Syntax

jmesd query staking validators

To retrieve the information of a single validator, append the validator address to the end of the command statement, as shown in the following example:

jmesd query staking validator jmesvaloper15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

`query tx`

Retrieves a transaction by its hash, account sequence, or signature.

Syntax to query by hash

jmesd query tx <hash>

Syntax to query by account sequence

jmesd query tx --type=acc_seq <address>:<sequence>

Syntax to query by signature

jmesd query tx --type=signature <sig1_base64,sig2_base64...>

`query txs`

Retrieves transactions that match the specified events where results are paginated.

Syntax

jmesd query txs --events '<event>' --page <page-number> --limit <number-of-results>

Example

jmesd query txs --events 'message.sender=cosmos1...&message.action=withdraw_delegator_reward' --page 1 --limit 30

`query wasm bytecode`

Retrieves the contract's WASM bytecode by referencing its ID.

Syntax

jmesd query wasm bytecode <code-id>

`query wasm code`

Retrieves information about a piece of uploaded code by referencing its ID.

Syntax

jmesd query wasm code <code-id>

`query wasm contract`

Retrieves the metadata information about an instantiated contract.

Syntax

jmesd query wasm contract <contract-address>

`query wasm contract-store`

Retrieves data about the contract store of the address and prints the results.

Syntax

jmesd query wasm contract-store <contract-address> <query-msg>

where <query-msg> is a JSON string that encodes the QueryMsg.

Example

jmesd query wasm contract-store jmes1plju286nnfj3z54wgcggd4enwaa9fgf5kgrgzl '{"config":{}}'

`query wasm params`

Retrieves the current WASM module's parameters.

Syntax

jmesd query wasm params

The parameters are returned in the following format:

max_contract_size: 512000
max_contract_gas: 100000000
max_contract_msg_size: 1024

`query wasm raw-store`

Retrieves the raw store of a contract and prints the results.

Syntax

jmesd query wasm raw-store <contract-address> <key> <subkey>

If the data uses a Singleton, it has only a key. If the data uses a prefixed data store, such as PrefixedStorage or Bucket, it can accept a subkey too.

`tx authz exec`

Runs a transaction for the granter.

Syntax

jmesd tx authz exec <msg-tx-json-filename> --from=<grantee-address>

Example

jmesd tx authz exec tx.json --from=jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm

`tx authz grant`

Authorizes another address to run transactions for you.

Syntax

jmesd tx authz grant <grantee-address> <authorization-type> --from=<your-address>

Example

jmesd tx authz grant jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm send /cosmos.bank.v1beta1.MsgSend --from=jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

Additionally, you can restrict this authorization to a specified allowance by including the --spend-limit flag, as shown in the following example:

jmesd tx authz grant jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm send /cosmos.bank.v1beta1.MsgSend --spend-limit=15000ubjmes --from=jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

`tx authz revoke`

Removes authorization from an account.

Syntax

jmesd tx authz revoke <grantee-address> <authorization-type> --from=<granter-address>

Example jmesd tx authz revoke jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm /cosmos.bank.v1beta1.MsgSend --from=jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc

`tx bank send`

Sends coins from one account to another account.

Syntax

jmesd tx bank send \
    <from-key-or-address> \
    <to-address> \
    <coins> \
    --chain-id=<chain-id> \

where

<from-key-or-address> is either the key name or the address. If the --generate-only flag is used, only addresses are accepted.
to-address is an account address.
<coins> is a comma-separated list of coins specified as <amount><coin-denominator>. For example, 1000usdr or 1000ubjmes,1000usdr.

Example

jmesd tx bank send \
    jmes15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc \
    jmes14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm \
    8600usdr \
    --chain-id=testnet \

`tx distribution fund-community-pool`

Funds the community pool with the specified amount.

Syntax

jmesd tx distribution fund-community-pool <amount>

Example jmesd tx distribution fund-community-pool 100ubjmes

`tx distribution set-withdraw-addr`

Changes the default withdrawal address for rewards associated with an address.

Syntax

jmesd tx distribution set-withdraw-addr <withdrawal-address>

Example

jmesd tx distribution set-withdraw-addr jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb

`tx distribution withdraw-all-rewards`

Withdraws all rewards.

Syntax

jmesd tx distribution withdraw-all-rewards

`tx distribution withdraw-rewards`

Withdraws your rewards against a validator.

Syntax

jmesd tx distribution withdraw-rewards <validator-address>

Example

jmesd tx distribution withdraw-rewards jmes19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy

`tx gov deposit`

For a proposal to be sent to the network, the amount deposited must be above a minimum amount specified by minDeposit (initial value is 50000000ubjmes). If the proposal you previously created didn't meet this requirement, you can still increase the total amount deposited to activate it. After the minimum deposit is reached, the voting period for the proposal begins.

Syntax

jmesd tx gov deposit <proposal-id> "<deposit-amount>" \
    --from=<name> \
    --chain-id=<chain-id>

Example

jmesd tx gov deposit 15 "10000000lubjmes" \
    --from=jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \
    --chain-id=phoenix-1

☢️caution

Proposals that don't meet this requirement are deleted after MaxDepositPeriod is reached.

`tx gov submit-proposal`

Submits proposals and deposits. To create a governance proposal, you must submit an initial deposit along with a title and description of your proposal. Alternatively, you can provide the proposal directly through the --proposal flag, which points to a JSON file containing the proposal.

Text proposals

Syntax

jmesd tx gov submit-proposal \
    --title=<title> \
    --description=<description> \
    --type="Text" \
    --deposit="<amount>" \
    --from=<name-or-address> \
    --chain-id=<chain-id>

Example

jmesd tx gov submit-proposal \
    --title=Funding for NFT platform \
    --description=Information about the NFT platform \
    --type="Text" \
    --deposit="100000ubjmes" \
    --from=jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \
    --chain-id=phoenix-1

Parameter-change proposals

When you submit a proposal to change a parameter, it is recommended that you send the proposal as a JSON file.

Syntax

jmesd tx gov submit-proposal \
    param-change <path/to/proposal.json> \
    --from=<name> \
    --chain-id=<chain_id>

Example

jmesd tx gov submit-proposal \
    param-change /proposals/proposal.json \
    --from=jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \
    --chain-id=phoenix-1

where proposal.json contains the following information:

{
  "title": "Param Change",
  "description": "Update max validators",
  "changes": [
    {
      "subspace": "staking",
      "key": "MaxValidators",
      "value": 105
    }
  ],
  "deposit": [
    {
      "denom": "ubjmes",
      "amount": "10000000"
    }
  ]
}

☢️caution

Because parameter changes are evaluated but not validated, ensure that the new value you propose is valid for its parameter. For example, the proposed value for MaxValidators must be an integer, not a decimal.

Community pool spend proposal

When you submit a community pool spend proposal, it is recommended that you send the proposal as a JSON file.

Syntax

jmesd tx gov submit-proposal \
    community-pool-spend <path/to/proposal.json> \
    --from=<name> \
    --chain-id=<chain_id>

Example

jmesd tx gov submit-proposal \
    community-pool-spend /proposals/proposal.json \
    --from=jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \
    --chain-id=phoenix-1

where proposal.json contains the following information:

{
  "title": "Community Pool Spend",
  "description": "Pay me some bJMES!",
  "recipient": "jmes1s5afhd6gxevu37mkqcvvsj8qeylhn0rzn7cdaq",
  "amount": [
    {
      "denom": "ubjmes",
      "amount": "10000"
    }
  ],
  "deposit": [
    {
      "denom": "ubjmes",
      "amount": "10000"
    }
  ]
}

Software upgrade proposals

The proposal to upgrade the software follows the syntax of a text proposal.

Syntax

jmesd tx gov submit-proposal software-upgrade <name> \
    --title=<title> \
    --description=<description> \
    --upgrade-height=<block-height> \
    --upgrade-info=<binary-details> \
    --type="Text" \
    --deposit="<amount>" \
    --from=<name-or-address> \
    --chain-id=<chain_id>

Example

jmesd tx gov submit-proposal software-upgrade v0.5.0-beta3 \
    --title="Upgrade to v0.6.0-beta3" \
    --description="let's upgrade to v0.6.0-beta3" \
    --upgrade-height=20 \
    --upgrade-info='{"binaries":{"darwin/amd64":"/Workspace/jmes/core/build/jmesd?checksum=sha256:2032356fe0899dec0cdd559f1c649bc81e53a9b4063b333059135e3a2aae8728"}}' \
    --type="Text" \
    --deposit="50000000ubjmes" \
    --from=jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \
    --chain-id=phoenix-1

To cancel a software upgrade:

Syntax

jmesd tx gov submit-proposal cancel-software-upgrade --title "<title>" --description "<description>"

Example

jmesd tx gov submit-proposal cancel-software-upgrade --title "Upgrade to v0.5.0-beta3" --description "let's upgrade to v0.6.0-beta3"

`tx gov vote`

After a proposal's deposit reaches the MinDeposit value, the voting period begins, and bonded bJMES holders can vote.

Syntax

jmesd tx gov vote \
    <proposal-id> <vote-type> \
    --from=<name> \
    --chain-id=<chain_id>

Example

jmesd tx gov vote \
    7 yes \
    --from=jmes13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \
    --chain-id=phoenix-1

`tx slashing unjail`

Releases a jailed validator.

Syntax

jmesd tx slashing unjail

Example

jmesd tx slashing unjail

`tx staking create-validator`

Creates a new validator that is initialized with a self-delegation.

Syntax

jmesd tx staking create-validator \
    --amount=<ubjmes-amount> \
    --pubkey=$(jmesd tendermint show-validator) \
    --moniker="<moniker>" \
    --website="<validator-website>" \
    --identity="<keybase-identity>" \
    --details="<validator-optional-details" \
    --commission-rate="<commission-rate>" \
    --commission-max-rate="<commission-max-rate>" \
    --commission-max-change-rate="<commission-max-change-rate>" \
    --min-self-delegation="<self-delegation-amount>"
    --chain-id=<chain-ID> \
    --from=<key-name> \

`tx staking delegate`

Delegates an amount of liquid coins from your wallet to a validator.

Syntax

jmesd tx staking delegate <validator-address> <amount>

Example

jmesd tx staking delegate jmesvaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm 2500stake

`tx staking edit-validator`

Edits an existing validator account.

Syntax

jmesd tx staking edit-validator \
    --moniker="<moniker>" \
    --details="<validator-optional-details>" \
    --commission-rate="commission-rate>" \
    --min-self-delegation="<minimum-self-delegation-amount" \

`tx staking redelegate`

Redelegates an amount of illiquid staking tokens from one validator to a different validator.

Syntax

jmesd tx staking redelegate <from-validator-address> <to-validator-address> <amount>

Example

jmesd tx staking redelegate jmesvaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj jmesvaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm 350stake

`tx staking unbond`

Unbonds an amount of bonded shares from a validator.

Syntax

jmesd tx staking unbond <validator-address> <stake-amount>

Example

jmesd tx staking unbond jmesvaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj 600stake

`tx wasm clear-admin`

Removes the contract admin so that the contract cannot be migrated.

Syntax

jmesd tx wasm clear-admin <contract-address>

`tx wasm execute`

Invokes processing functions on the smart contract.

Syntax

jmesd tx wasm execute <contract-address> <handle-msg> <coins>

Where <handle-msg> is a raw JSON string containing the HandleMsg that is parsed and routed to the correct message handling logic in the contract, and <coins> is the optional amount of coins specified in a comma-separated list that you want to send with your message, in case the logic requires some fees.

`tx wasm instantiate`

Creates a new contract by referencing the code ID of a contract that has been uploaded.

Syntax

jmesd tx wasm instantiate <code-id> <init-msg> <coins>

where <init-msg> is a JSON string containing the InitMsg to initialize your contract's state, and <coins> is the optional amount of coins specified in a comma-separated list that you want to send to the new contract account.

Example

jmesd tx wasm instantiate 1 '{"arbiter": "jmes~~"}' "1000000ubjmes"

`tx wasm migrate`

Updates the code ID of the contract to migrate to a new code ID. This command can be issued only from the key corresponding to the contract's owner.

Syntax

jmesd tx wasm migrate <contract-address> <new-code-id> <migrate-msg>

Example

jmesd tx wasm migrate jmes... 10 '{"verifier": "jmes..."}'

`tx wasm store`

Uploads a new WASM binary or migrates to existing binary to the phoenix-1 release.

Syntax for a new WASM binary

jmesd tx wasm store <path-to-wasm-file>

where <path-to-wasm-file> is the path of a file that is the compiled binary of the smart contract code that you want to upload.

`tx wasm update-admin`

Updates a contract owner to a new address. This command can be issued only from the key corresponding to the contract's owner.

Syntax

jmesd tx wasm update-admin <contract-address> <new-owner>

debug addr
debug pubkey
debug raw-bytes
keys add
keys show
keys list
query authz grants
query bank balances
query bank denom-metadata
query bank total
query distribution rewards
query distribution commission
query distribution slashes
query distribution community-pool
query distribution params
query gov deposit
query gov deposits
query gov proposal
query gov proposals
query gov vote
query gov votes
query gov tally
query gov param
query gov params
query mint annual-provisions
query mint inflation
query mint params
query slashing signing-info
query slashing signing-infos
query slashing params
query staking delegation
query staking delegations
query staking delegations-to
query staking historical-info
query staking params
query staking pool
query staking redelegation
query staking redelegations
query staking redelegations-from
query staking unbonding-delegation
query staking unbonding-delegations
query staking unbonding-delegations-from
query staking validators
query tx
query txs
query wasm bytecode
query wasm code
query wasm contract
query wasm contract-store
query wasm params
query wasm raw-store
tx authz exec
tx authz grant
tx authz revoke
tx bank send
tx distribution fund-community-pool
tx distribution set-withdraw-addr
tx distribution withdraw-all-rewards
tx distribution withdraw-rewards
tx gov deposit
tx gov submit-proposal
- Text proposals
- Parameter-change proposals
- Community pool spend proposal
- Software upgrade proposals
tx gov vote
tx slashing unjail
tx staking create-validator
tx staking delegate
tx staking edit-validator
tx staking redelegate
tx staking unbond
tx wasm clear-admin
tx wasm execute
tx wasm instantiate
tx wasm migrate
tx wasm store
tx wasm update-admin

Subcommands

debug addr​

debug pubkey​

debug raw-bytes​

keys add​

keys show​

keys list​

query authz grants​

query bank balances​

query bank denom-metadata​

query bank total​

query distribution rewards​

query distribution commission​

query distribution slashes​

query distribution community-pool​

query distribution params​

query gov deposit​

query gov deposits​

query gov proposal​

query gov proposals​

query gov vote​

query gov votes​

query gov tally​

query gov param​

query gov params​

query mint annual-provisions​

query mint inflation​

query mint params​

query slashing signing-info​

query slashing signing-infos​

query slashing params​

query staking delegation​

query staking delegations​

query staking delegations-to​

query staking historical-info​

query staking params​

query staking pool​

query staking redelegation​

query staking redelegations​

query staking redelegations-from​

query staking unbonding-delegation​

query staking unbonding-delegations​

query staking unbonding-delegations-from​

query staking validators​

query tx​

query txs​

query wasm bytecode​

query wasm code​

query wasm contract​

query wasm contract-store​

query wasm params​

query wasm raw-store​

tx authz exec​

tx authz grant​

tx authz revoke​

tx bank send​

tx distribution fund-community-pool​

tx distribution set-withdraw-addr​

tx distribution withdraw-all-rewards​

tx distribution withdraw-rewards​

tx gov deposit​

tx gov submit-proposal​

Text proposals​

Parameter-change proposals​

Community pool spend proposal​

Software upgrade proposals​

tx gov vote​

tx slashing unjail​

tx staking create-validator​

tx staking delegate​

tx staking edit-validator​

tx staking redelegate​

tx staking unbond​

tx wasm clear-admin​

tx wasm execute​

tx wasm instantiate​

tx wasm migrate​

tx wasm store​

tx wasm update-admin​

`debug addr`

`debug pubkey`

`debug raw-bytes`

`keys add`

`keys show`

`keys list`

`query authz grants`

`query bank balances`

`query bank denom-metadata`

`query bank total`

`query distribution rewards`

`query distribution commission`

`query distribution slashes`

`query distribution community-pool`

`query distribution params`

`query gov deposit`

`query gov deposits`

`query gov proposal`

`query gov proposals`

`query gov vote`

`query gov votes`

`query gov tally`

`query gov param`

`query gov params`

`query mint annual-provisions`

`query mint inflation`

`query mint params`

`query slashing signing-info`

`query slashing signing-infos`

`query slashing params`

`query staking delegation`

`query staking delegations`

`query staking delegations-to`

`query staking historical-info`

`query staking params`

`query staking pool`

`query staking redelegation`

`query staking redelegations`

`query staking redelegations-from`

`query staking unbonding-delegation`

`query staking unbonding-delegations`

`query staking unbonding-delegations-from`

`query staking validators`

`query tx`

`query txs`

`query wasm bytecode`

`query wasm code`

`query wasm contract`

`query wasm contract-store`

`query wasm params`

`query wasm raw-store`

`tx authz exec`

`tx authz grant`

`tx authz revoke`

`tx bank send`

`tx distribution fund-community-pool`

`tx distribution set-withdraw-addr`

`tx distribution withdraw-all-rewards`

`tx distribution withdraw-rewards`

`tx gov deposit`

`tx gov submit-proposal`

Text proposals

Parameter-change proposals

Community pool spend proposal

Software upgrade proposals

`tx gov vote`

`tx slashing unjail`

`tx staking create-validator`

`tx staking delegate`

`tx staking edit-validator`

`tx staking redelegate`

`tx staking unbond`

`tx wasm clear-admin`

`tx wasm execute`

`tx wasm instantiate`

`tx wasm migrate`

`tx wasm store`

`tx wasm update-admin`