Get desktop application:
View/edit binary Protocol Buffers messages
Service defines a gRPC service for interacting with transactions.
Simulate simulates executing a transaction for estimating gas usage.
SimulateRequest is the request type for the Service.Simulate RPC method.
tx is the transaction to simulate. Deprecated. Send raw tx bytes instead.
tx_bytes is the raw transaction. Since: cosmos-sdk 0.43
SimulateResponse is the response type for the Service.SimulateRPC method.
gas_info is the information about gas used in the simulation.
result is the result of the simulation.
GetTx fetches a tx by hash.
GetTxRequest is the request type for the Service.GetTx RPC method.
hash is the tx hash to query, encoded as a hex string.
GetTxResponse is the response type for the Service.GetTx method.
tx is the queried transaction.
tx_response is the queried TxResponses.
BroadcastTx broadcast transaction.
BroadcastTxRequest is the request type for the Service.BroadcastTxRequest RPC method.
tx_bytes is the raw transaction.
BroadcastTxResponse is the response type for the Service.BroadcastTx method.
tx_response is the queried TxResponses.
GetTxsEvent fetches txs by event.
GetTxsEventRequest is the request type for the Service.TxsByEvents RPC method.
events is the list of transaction event type.
pagination defines a pagination for the request.
GetTxsEventResponse is the response type for the Service.TxsByEvents RPC method.
txs is the list of queried transactions.
tx_responses is the list of queried TxResponses.
pagination defines a pagination for the response.
GetBlockWithTxs fetches a block with decoded txs. Since: cosmos-sdk 0.45.2
GetBlockWithTxsRequest is the request type for the Service.GetBlockWithTxs RPC method. Since: cosmos-sdk 0.45.2
height is the height of the block to query.
pagination defines a pagination for the request.
GetBlockWithTxsResponse is the response type for the Service.GetBlockWithTxs method. Since: cosmos-sdk 0.45.2
txs are the transactions in the block.
pagination defines a pagination for the response.
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.
BroadcastMode specifies the broadcast mode for the TxService.Broadcast RPC method.
Used in:
zero-value for mode ordering
BROADCAST_MODE_BLOCK defines a tx broadcasting mode where the client waits for the tx to be committed in a block.
BROADCAST_MODE_SYNC defines a tx broadcasting mode where the client waits for a CheckTx execution response only.
BROADCAST_MODE_ASYNC defines a tx broadcasting mode where the client returns immediately.
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
OrderBy defines the sorting order
Used in:
ORDER_BY_UNSPECIFIED specifies an unknown sorting order. OrderBy defaults to ASC in this case.
ORDER_BY_ASC defines ascending order
ORDER_BY_DESC defines descending order
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
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.
Tx is the standard type used for broadcasting transactions.
Used in:
, , ,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.