Subcommands
This section describes the subcommands available for Terrad.
debug addr
Changes an address from hex encoding to bech32.
Syntax
_1terrad debug addr <address>
Example
_1terrad debug addr terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm
debug pubkey
Decodes a pubkey from proto JSON and displays the address.
Syntax
_1terrad debug pubkey <pubkey>
Example
_1terrad debug pubkey '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AurroA7jvfPd1AadmmOvWM2rJSwipXfRf8yD6pLbA2DJ"}'
debug raw-bytes
Changes raw bytes to hex.
Syntax
_1terrad debug raw-bytes <raw-bytes>
Example
_1terrad 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.
For security purposes, run this command on an offline computer.
Syntax
_1terrad 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.
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.
After you have triple-checked your mnemonic and safely stored it, you can delete bash history to ensure no one can retrieve it.
_2history -c_2rm ~/.bash_history
To generate more accounts from the same mnemonic, run:
_1terrad 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.
Do not use the same passphrase for multiple keys. Do not lose or share your mnemonic with anyone.
Example
_1terrad 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
_1terrad keys add <yourKeyName> --recover
For information about generating multisignature accounts and signing transactions, see Sign with a multisig account.
keys show
Retrieves an address for a specified account. The address is prefixed by terra-, for example terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc. To receive funds, you must give an account address to the sender.
Syntax
_1terrad keys show <account-name>
Example
_1terrad 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:
_1terrad keys show accountExample --bech=val
To show the validator consensus address that is generated when the node is created by terrad init and the Tendermint signing key for the node, use the tendermint command, as shown in the following example:
_1terrad tendermint show-address
keys list
Lists all your keys.
Syntax
_1terrad keys list
query authz grants
Retrieves all existing grants between a granter and a grantee.
Syntax
_1terrad query authz grants <granter-address> <grantee-address>
Example
_1terrad query authz grants terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm
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:
_1terrad query authz grants terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm /cosmos.bank.v1beta1.MsgSend
query bank balances
Displays your account balance, account number, and sequence number (nonce).
Syntax
_1terrad query bank balances <account-address>
Example
_1terrad query bank balances terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
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:
_1No 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
_1terrad 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:
_1terrad query distribution rewards terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm
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:
_1terrad query distribution rewards terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm terra19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy
query distribution commission
Checks the current outstanding commission for a validator.
Syntax
_1terrad query distribution commission <validator_address>
Example
_1terrad query distribution commission terra19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy
query distribution slashes
Checks historical slashes for a validator within a range of blocks.
Syntax
_1terrad query distribution slashes <validator-address> <start-block-height> <end-block-height>
Example
_1terrad query distribution slashes terra19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy 25 300
query distribution community-pool
Checks all coins in the community pool.
Syntax
_1terrad query distribution community-pool
query distribution params
Checks the current distribution parameters.
Syntax
_1terrad query distribution params
The parameters are returned in YAML, as shown in the following example:
_4community_tax: "0.020000000000000000"_4base_proposer_reward: "0.010000000000000000"_4bonus_proposer_reward: "0.040000000000000000"_4withdraw_addr_enabled: true
query gov deposit
Retrieves information about a single proposal deposit on a proposal by its identifier.
Syntax
_1terrad query gov deposit <proposal-id> <depositor-address>
Example
_1terrad query gov deposit 4 terra1skjwj5whet0lpe65qaq4rpq03hjxlwd9nf39lk
query gov deposits
Retrieves all deposits submitted to a proposal after it is created.
Syntax
_1terrad query gov deposits <proposal-id>
Example
_1terrad query gov deposits 5
query gov proposal
Retrieves information about one proposal.
proposal retrieves information about one proposal.
Syntax
_1terrad query gov proposal <proposal-id>
Example
_1terrad query gov proposal 3
query gov proposals
Retrieves information about all available proposals.
Syntax
_1terrad 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:
_1terrad query gov proposals --voter terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb
query gov vote
Retrieves information about a single vote by a specific voter.
Syntax
_1terrad query gov vote <proposal-id> <voter-address>
Example
_1terrad query gov vote 7 terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb
query gov votes
Retrieves all the votes submitted to the proposal.
Syntax
_1terrad query gov votes <proposal-id>
Example
_1terrad query gov votes 9
query gov tally
Retrieves the current tally for a specified proposal.
Syntax
_1terrad query gov tally <proposal-id>
Example
_1terrad query gov tally 4
query gov param
Retrieves all the parameters for the specified governance process.
Syntax
_1terrad query gov param <process-type>
Example
_1terrad query gov param voting
query gov params
Retrieves all the parameters for all governance processes.
Syntax
_1terrad query gov params
The parameters are returned in the following format:
_11voting_params:_11 voting_period: 5m0s_11tally_params:_11 quorum: "0.334000000000000000"_11 threshold: "0.500000000000000000"_11 veto: "0.334000000000000000"_11deposit_parmas:_11 min_deposit:_11 - denom: uluna_11 amount: "10000000"_11 max_deposit_period: 48h0m0s
query mint annual-provisions
Retrieves the value of annual provisions.
Syntax
_1terrad query mint annual-provisions
query mint inflation
Retrieves the current value of inflation.
Syntax
_1terrad query mint inflation
query mint params
Retrieves the mint module's parameters.
Syntax
_1terrad query mint params
Parameters are returned in the following format:
_6mint_denom: uluna_6inflation_rate_change: "0.130000000000000000"_6inflation_max: "0.200000000000000000"_6inflation_min: "0.070000000000000000"_6goal_bonded: "0.670000000000000000"_6blocks_per_year: 6311520
query slashing signing-info
Retrieves a validator's signing info.
Syntax
_1terrad query slashing signing-info <validator-consensus-public-key>
Example
_1terrad query slashing signing-info terravalconspub1atjdueldlxwft8d4729pqhdhm3nlss0u4wx7wpeqb1zhjf8yr1tn7cgw2b4q4yv9na
query slashing signing-infos
Retrieves signing information of all validators.
Syntax
_1terrad query slashing signing-infos
query slashing params
Retrieves the genesis parameters for the slashing module.
Syntax
_1terrad query slashing params
The parameters are returned in the following format:
_5signed_blocks_window: 100_5min_signed_per_window: "0.500000000000000000"_5downtime_jail_duration: 10m0s_5slash_fraction_double_sign: "0.050000000000000000"_5slash_fraction_downtime: "0.010000000000000000"
query staking delegation
Retrieves delegation information for a validator.
Syntax
_1terrad query staking delegation <delegator-address> <validator-address>
Example
_1terrad query staking delegation terra1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p terravaloper15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
query staking delegations
Retrieves delegations for a delegator on all validators.
Syntax
_1terrad query staking delegations <delegator-address>
Example
_1terrad query staking delegations terra1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p
query staking delegations-to
Retrieves all of the delegations on a particular validator.
Syntax
_1terrad query staking delegations-to <validator-address>
Example
_1terrad query staking delegations-to terravaloper15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
query staking historical-info
Retrieves all historical information at a specified height.
Syntax
_1terrad query staking historical-info <height>
Example
_1terrad query staking historical-info 23
query staking params
Retrieves all staking parameters.
Syntax
_1terrad query staking params
The parameters are returned in the following format:
_5unbonding_time: 504h0m0s_5max_validators: 100_5max_entries: 100_5historical_entries: 0_5bond_denom: uluna
query staking pool
Retrieves amounts stored in the staking pool.
Syntax
_1terrad 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
_1terrad query staking redelegation <delegator-address> <src-val-addr> <dst-val-addr>
Example
_1terrad query staking redelegation terra1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p terravaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm terravaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj
query staking redelegations
Retrieves all redelegation information for a delegator.
Syntax
_1terrad query staking redelegations <delegator-address>
Example
_1terrad query staking redelegations terra1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p
query staking redelegations-from
Retrieves all the delegations that are redelegating from a specified validator:
Syntax
_1terrad query staking redelegations-from <validator-address>
Example
_1terrad query staking redelegations-from terravaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj
query staking unbonding-delegation
Retrieves information about unbonding delegations for a specified delegator and validator.
Syntax
_1terrad query staking unbonding-delegation <delegator-address> <validator-address>
Example
_1terrad query staking unbonding-delegation terra1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p terravaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm
query staking unbonding-delegations
Retrieves all your current unbonding delegations for a specified delegator.
Syntax
_1terrad query staking unbonding-delegations <delegator-address>
Example
_1terrad query staking unbonding-delegations terra1gghjut3ccd8ay0zduzj64hwre2fxs9ld75ru9p
query staking unbonding-delegations-from
Retrieves all the unbonding delegations from a specified validator.
Syntax
_1terrad query staking unbonding-delegations-from <validator-address>
Example
_1terrad query staking unbonding-delegations-from terravaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm
query staking validators
Retrieves the list of all registered validators.
Syntax
_1terrad 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:
_1terrad query staking validator terravaloper15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
query tx
Retrieves a transaction by its hash, account sequence, or signature.
Syntax to query by hash
_1terrad query tx <hash>
Syntax to query by account sequence
_1terrad query tx --type=acc_seq <address>:<sequence>
Syntax to query by signature
_1terrad query tx --type=signature <sig1_base64,sig2_base64...>
query txs
Retrieves transactions that match the specified events where results are paginated.
Syntax
_1terrad query txs --events '<event>' --page <page-number> --limit <number-of-results>
Example
_1terrad 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
_1terrad query wasm bytecode <code-id>
query wasm code
Retrieves information about a piece of uploaded code by referencing its ID.
Syntax
_1terrad query wasm code <code-id>
query wasm contract
Retrieves the metadata information about an instantiated contract.
Syntax
_1terrad query wasm contract <contract-address>
query wasm contract-store
Retrieves data about the contract store of the address and prints the results.
Syntax
_1terrad query wasm contract-store <contract-address> <query-msg>
where <query-msg> is a JSON string that encodes the QueryMsg.
Example
_1terrad query wasm contract-store terra1plju286nnfj3z54wgcggd4enwaa9fgf5kgrgzl '{"config":{}}'
query wasm params
Retrieves the current WASM module's parameters.
Syntax
_1terrad query wasm params
The parameters are returned in the following format:
_3max_contract_size: 512000_3max_contract_gas: 100000000_3max_contract_msg_size: 1024
query wasm raw-store
Retrieves the raw store of a contract and prints the results.
Syntax
_1terrad 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
_1terrad tx authz exec <msg-tx-json-filename> --from=<grantee-address>
Example
_1terrad tx authz exec tx.json --from=terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm
tx authz grant
Authorizes another address to run transactions for you.
Syntax
_1terrad tx authz grant <grantee-address> <authorization-type> --from=<your-address>
Example
_1terrad tx authz grant terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm send /cosmos.bank.v1beta1.MsgSend --from=terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
Additionally, you can restrict this authorization to a specified allowance by including the --spend-limit flag, as shown in the following example:
_1terrad tx authz grant terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm send /cosmos.bank.v1beta1.MsgSend --spend-limit=15000uluna --from=terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
tx authz revoke
Removes authorization from an account.
Syntax
_1terrad tx authz revoke <grantee-address> <authorization-type> --from=<granter-address>
Example terrad tx authz revoke terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm /cosmos.bank.v1beta1.MsgSend --from=terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc
tx bank send
Sends coins from one account to another account.
Syntax
_5terrad tx bank send \_5 <from-key-or-address> \_5 <to-address> \_5 <coins> \_5 --chain-id=<chain-id> \
where
<from-key-or-address>is either the key name or the address. If the--generate-onlyflag is used, only addresses are accepted.to-addressis an account address.<coins>is a comma-separated list of coins specified as<amount><coin-denominator>. For example,1000usdror1000uluna,1000usdr.
Example
_5terrad tx bank send \_5 terra15h6vd5f0wqps26zjlwrc6chah08ryu4hzzdwhc \_5 terra14h2od5f3vahd28uywwvt8sqbi52upnzagshtrm \_5 8600usdr \_5 --chain-id=testnet \
tx distribution fund-community-pool
Funds the community pool with the specified amount.
Syntax
_1terrad tx distribution fund-community-pool <amount>
Example terrad tx distribution fund-community-pool 100uluna
tx distribution set-withdraw-addr
Changes the default withdrawal address for rewards associated with an address.
Syntax
_1terrad tx distribution set-withdraw-addr <withdrawal-address>
Example
_1terrad tx distribution set-withdraw-addr terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb
tx distribution withdraw-all-rewards
Withdraws all rewards.
Syntax
_1terrad tx distribution withdraw-all-rewards
tx distribution withdraw-rewards
Withdraws your rewards against a validator.
Syntax
_1terrad tx distribution withdraw-rewards <validator-address>
Example
_1terrad tx distribution withdraw-rewards terra19t4gde4f8ndwx67qhbnur9yqdc31xznpksajbcy
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 50000000uluna). 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
_3terrad tx gov deposit <proposal-id> "<deposit-amount>" \_3 --from=<name> \_3 --chain-id=<chain-id>
Example
_3terrad tx gov deposit 15 "10000000luluna" \_3 --from=terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \_3 --chain-id=phoenix-1
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
_7terrad tx gov submit-proposal \_7 --title=<title> \_7 --description=<description> \_7 --type="Text" \_7 --deposit="<amount>" \_7 --from=<name-or-address> \_7 --chain-id=<chain-id>
Example
_7terrad tx gov submit-proposal \_7 --title=Funding for NFT platform \_7 --description=Information about the NFT platform \_7 --type="Text" \_7 --deposit="100000uluna" \_7 --from=terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \_7 --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
_4terrad tx gov submit-proposal \_4 param-change <path/to/proposal.json> \_4 --from=<name> \_4 --chain-id=<chain_id>
Example
_4terrad tx gov submit-proposal \_4 param-change /proposals/proposal.json \_4 --from=terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \_4 --chain-id=phoenix-1
where proposal.json contains the following information:
_17{_17 "title": "Param Change",_17 "description": "Update max validators",_17 "changes": [_17 {_17 "subspace": "staking",_17 "key": "MaxValidators",_17 "value": 105_17 }_17 ],_17 "deposit": [_17 {_17 "denom": "uluna",_17 "amount": "10000000"_17 }_17 ]_17}
Because parameter changes are evaluated but not validated, ensure that 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
_4terrad tx gov submit-proposal \_4 community-pool-spend <path/to/proposal.json> \_4 --from=<name> \_4 --chain-id=<chain_id>
Example
_4terrad tx gov submit-proposal \_4 community-pool-spend /proposals/proposal.json \_4 --from=terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \_4 --chain-id=phoenix-1
where proposal.json contains the following information:
_17{_17 "title": "Community Pool Spend",_17 "description": "Pay me some Lunas!",_17 "recipient": "terra1s5afhd6gxevu37mkqcvvsj8qeylhn0rzn7cdaq",_17 "amount": [_17 {_17 "denom": "uluna",_17 "amount": "10000"_17 }_17 ],_17 "deposit": [_17 {_17 "denom": "uluna",_17 "amount": "10000"_17 }_17 ]_17}
Software upgrade proposals
The proposal to upgrade the software follows the syntax of a text proposal.
Syntax
_9terrad tx gov submit-proposal software-upgrade <name> \_9 --title=<title> \_9 --description=<description> \_9 --upgrade-height=<block-height> \_9 --upgrade-info=<binary-details> \_9 --type="Text" \_9 --deposit="<amount>" \_9 --from=<name-or-address> \_9 --chain-id=<chain_id>
Example
_9terrad tx gov submit-proposal software-upgrade v0.5.0-beta3 \_9 --title="Upgrade to v0.6.0-beta3" \_9 --description="let's upgrade to v0.6.0-beta3" \_9 --upgrade-height=20 \_9 --upgrade-info='{"binaries":{"darwin/amd64":"/Workspace/terra/core/build/terrad?checksum=sha256:2032356fe0899dec0cdd559f1c649bc81e53a9b4063b333059135e3a2aae8728"}}' \_9 --type="Text" \_9 --deposit="50000000uluna" \_9 --from=terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \_9 --chain-id=phoenix-1
To cancel a software upgrade:
Syntax
_1terrad tx gov submit-proposal cancel-software-upgrade --title "<title>" --description "<description>"
Example
_1terrad 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 Luna holders can vote.
Syntax
_4terrad tx gov vote \_4 <proposal-id> <vote-type> \_4 --from=<name> \_4 --chain-id=<chain_id>
Example
_4terrad tx gov vote \_4 7 yes \_4 --from=terra13a8ddv3h7kbcn73akcbpe7ueks22vaolewpaxmb \_4 --chain-id=phoenix-1
tx slashing unjail
Releases a jailed validator.
Syntax
_1terrad tx slashing unjail
Example
_1terrad tx slashing unjail
tx staking create-validator
Creates a new validator that is initialized with a self-delegation.
Syntax
_13terrad tx staking create-validator \_13 --amount=<uluna-amount> \_13 --pubkey=$(terrad tendermint show-validator) \_13 --moniker="<moniker>" \_13 --website="<validator-website>" \_13 --identity="<keybase-identity>" \_13 --details="<validator-optional-details" \_13 --commission-rate="<commission-rate>" \_13 --commission-max-rate="<commission-max-rate>" \_13 --commission-max-change-rate="<commission-max-change-rate>" \_13 --min-self-delegation="<self-delegation-amount>"_13 --chain-id=<chain-ID> \_13 --from=<key-name> \
tx staking delegate
Delegates an amount of liquid coins from your wallet to a validator.
Syntax
_1terrad tx staking delegate <validator-address> <amount>
Example
_1terrad tx staking delegate terravaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm 2500stake
tx staking edit-validator
Edits an existing validator account.
Syntax
_5terrad tx staking edit-validator \_5 --moniker="<moniker>" \_5 --details="<validator-optional-details>" \_5 --commission-rate="commission-rate>" \_5 --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
_1terrad tx staking redelegate <from-validator-address> <to-validator-address> <amount>
Example
_1terrad tx staking redelegate terravaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj terravaloper1l2rsakp388kuv9k8qzq6lrm9taddae7fpx59wm 350stake
tx staking unbond
Unbonds an amount of bonded shares from a validator.
Syntax
_1terrad tx staking unbond <validator-address> <stake-amount>
Example
_1terrad tx staking unbond terravaloper1gghjut3ccd8ay0zduzj64hwre2fxs9ldmqhffj 600stake
tx wasm clear-admin
Removes the contract admin so that the contract cannot be migrated.
Syntax
_1terrad tx wasm clear-admin <contract-address>
tx wasm execute
Invokes processing functions on the smart contract.
Syntax
_1terrad 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
_1terrad 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
_1terrad tx wasm instantiate 1 '{"arbiter": "terra~~"}' "1000000uluna"
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
_1terrad tx wasm migrate <contract-address> <new-code-id> <migrate-msg>
Example
_1terrad tx wasm migrate terra... 10 '{"verifier": "terra..."}'
tx wasm store
Uploads a new WASM binary or migrates to existing binary to the phoenix-1 release.
Syntax for a new WASM binary
_1terrad 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
_1terrad tx wasm update-admin <contract-address> <new-owner>