rizond
binary.--help
flag to get more information about.send
. Through this send
command, see how to use tx commands.generate
- sign
- broadcast
steps. So the command above works internally generate unsigned transaction first, and ask password of from_key_or_address
to sign, sign the generated transaction with key, and finally broadcast the signed transaction.--dry-run
flag to the command line.--generate-only
flag. This allows you to separate the creation and signing of a transaction without broadcasting.from_key
is not supported in generate-only mode. You need to use from_address
.--generate-only
flag. It will read a transaction from [file]
, sign it, and print its JSON encoding.--signature-only
flag is set, it will output the signature parts only.--offline
flag makes sure that the client will not reach out to full node. As a result, the account and sequence number queries will not be performed and it is required to set such parameters manually. Note, invalid values will cause the transaction to fail.--offline
flag is also set, signature validation over the transaction will be not be performed as that will require RPC communication with a full node.--generate-only
flag and signed with the sign
command. This command reads the transaction from [file]
and broadcast it to a node.create-validator
command needs some mandatory flags.gas
is a special unit that is used to track the consumption of resources during execution. gas
is typically consumed whenever read and writes are made to the store, but it can also be consumed if expensive computation needs to be done. It serves two main purposes:gas
consumed during message
execution is typically priced, resulting in a fee
(fees = gas * gas-prices
). fees
generally have to be paid by the sender of the message
. Note that the Cosmos platform does not enforce gas
pricing by default, as there may be other ways to prevent spam (e.g. bandwidth schemes). Still, most applications will implement fee
mechanisms to prevent spam. This is done via the AnteHandler
.gas
is dependent on the transaction. Different transaction require different amount of gas
. gas-prices
is the price of each unit of gas
. Each validator sets a minimum-gas-prices
value, and will only include transactions that have a gas-prices
greater than their minimum-gas-prices
.fees
are the product of gas
and gas-prices
. gas-prices
or fees
. The validators specify a minimum-gas-prices
at app.toml
file that they use to determine whether to include a transaction, where gas-prices >= min-gas-prices
. The higher gas-prices
or fees
, the higher chance that your transaction will get included in a block. --gas-prices
flag.--gas
flag every time, the gas
amount for a transaction is calculated as it is being processed automatically as default. Of course, this only gives an estimate, so it returns failures. So you can adjust this estimate with the flag --gas-adjustment
if you want to be sure you provide enough gas
for the transaction.--fees
sure.min-gas-prices
by dividing your fee with the estimated gas
consumption, to properly assign the right priority to your transaction.