Get desktop application:
View/edit binary Protocol Buffers messages
AuthInfo describes the fee and signer modes that are used to sign a transaction.
Used in:
signer_infos defines the signing modes for the required signers. The number and order of elements must match the required signers from TxBody's messages. The first element is the primary signer and the one which pays the fee.
Fee is the fee and gas limit for the transaction. The first signer is the primary signer and the one which pays the fee. The fee can be calculated based on the cost of evaluating the body and doing signature verification of the signers. This can be estimated via simulation.
Tip is the optional tip used for transactions fees paid in another denom. This field is ignored if the chain didn't enable tips, i.e. didn't add the `TipDecorator` in its posthandler. Since: cosmos-sdk 0.46
AuxSignerData is the intermediary format that an auxiliary signer (e.g. a tipper) builds and sends to the fee payer (who will build and broadcast the actual tx). AuxSignerData is not a valid tx in itself, and will be rejected by the node if sent directly as-is. Since: cosmos-sdk 0.46
address is the bech32-encoded address of the auxiliary signer. If using AuxSignerData across different chains, the bech32 prefix of the target chain (where the final transaction is broadcasted) should be used.
sign_doc is the SIGN_MODE_DIRECT_AUX sign doc that the auxiliary signer signs. Note: we use the same sign doc even if we're signing with LEGACY_AMINO_JSON.
mode is the signing mode of the single signer.
sig is the signature of the sign doc.
Fee includes the amount of coins paid in fees and the maximum gas to be used by the transaction. The ratio yields an effective "gasprice", which must be above some miminum to be accepted into the mempool.
Used in:
amount is the amount of coins to be paid as a fee
gas_limit is the maximum gas that can be used in transaction processing before an out of gas error occurs
if unset, the first signer is responsible for paying the fees. If set, the specified account must pay the fees. the payer must be a tx signer (and thus have signed this field in AuthInfo). setting this field does *not* change the ordering of required signers for the transaction.
if set, the fee payer (either the first signer or the value of the payer field) requests that a fee grant be used to pay fees instead of the fee payer's own balance. If an appropriate fee grant does not exist or the chain does not support fee grants, this will fail
ModeInfo describes the signing mode of a single or nested multisig signer.
Used in: ,
sum is the oneof that specifies whether this represents a single or nested multisig signer
single represents a single signer
multi represents a nested multisig signer
Multi is the mode info for a multisig public key
Used in:
bitarray specifies which keys within the multisig are signing
mode_infos is the corresponding modes of the signers of the multisig which could include nested multisig public keys
Single is the mode info for a single signer. It is structured as a message to allow for additional fields such as locale for SIGN_MODE_TEXTUAL in the future
Used in:
mode is the signing mode of the single signer
SignDoc is the type used for generating sign bytes for SIGN_MODE_DIRECT.
body_bytes is protobuf serialization of a TxBody that matches the representation in TxRaw.
auth_info_bytes is a protobuf serialization of an AuthInfo that matches the representation in TxRaw.
chain_id is the unique identifier of the chain this transaction targets. It prevents signed transactions from being used on another chain by an attacker
account_number is the account number of the account in state
SignDocDirectAux is the type used for generating sign bytes for SIGN_MODE_DIRECT_AUX. Since: cosmos-sdk 0.46
Used in:
body_bytes is protobuf serialization of a TxBody that matches the representation in TxRaw.
public_key is the public key of the signing account.
chain_id is the identifier of the chain this transaction targets. It prevents signed transactions from being used on another chain by an attacker.
account_number is the account number of the account in state.
sequence is the sequence number of the signing account.
Tip is the optional tip used for transactions fees paid in another denom. It should be left empty if the signer is not the tipper for this transaction. This field is ignored if the chain didn't enable tips, i.e. didn't add the `TipDecorator` in its posthandler.
SignerInfo describes the public key and signing mode of a single top-level signer.
Used in:
public_key is the public key of the signer. It is optional for accounts that already exist in state. If unset, the verifier can use the required \ signer address for this position and lookup the public key.
mode_info describes the signing mode of the signer and is a nested structure to support nested multisig pubkey's
sequence is the sequence of the account, which describes the number of committed transactions signed by a given address. It is used to prevent replay attacks.
Tip is the tip used for meta-transactions. Since: cosmos-sdk 0.46
Used in: ,
amount is the amount of the tip
tipper is the address of the account paying for the tip
Tx is the standard type used for broadcasting transactions.
body is the processable content of the transaction
auth_info is the authorization related content of the transaction, specifically signers, signer modes and fee
signatures is a list of signatures that matches the length and order of AuthInfo's signer_infos to allow connecting signature meta information like public key and signing mode by position.
TxBody is the body of a transaction that all signers sign over.
Used in:
messages is a list of messages to be executed. The required signers of those messages define the number and order of elements in AuthInfo's signer_infos and Tx's signatures. Each required signer address is added to the list only the first time it occurs. By convention, the first required signer (usually from the first message) is referred to as the primary signer and pays the fee for the whole transaction.
memo is any arbitrary note/comment to be added to the transaction. WARNING: in clients, any publicly exposed text should not be called memo, but should be called `note` instead (see https://github.com/cosmos/cosmos-sdk/issues/9122).
timeout is the block height after which this transaction will not be processed by the chain
extension_options are arbitrary options that can be added by chains when the default options are not sufficient. If any of these are present and can't be handled, the transaction will be rejected
extension_options are arbitrary options that can be added by chains when the default options are not sufficient. If any of these are present and can't be handled, they will be ignored
TxRaw is a variant of Tx that pins the signer's exact binary representation of body and auth_info. This is used for signing, broadcasting and verification. The binary `serialize(tx: TxRaw)` is stored in Tendermint and the hash `sha256(serialize(tx: TxRaw))` becomes the "txhash", commonly used as the transaction ID.
body_bytes is a protobuf serialization of a TxBody that matches the representation in SignDoc.
auth_info_bytes is a protobuf serialization of an AuthInfo that matches the representation in SignDoc.
signatures is a list of signatures that matches the length and order of AuthInfo's signer_infos to allow connecting signature meta information like public key and signing mode by position.