Module diem_types::transaction [−][src]
Modules
This file implements Diem transaction metadata types to allow easy parsing and introspection into metadata, whether the transaction is using regular subaddressing, is subject to travel rule or corresponds to an on-chain payment refund.
Structs
A list of transactions under an account that are contiguous by sequence number and include proofs.
The description of a (regular) argument in a script.
RawTransaction is the portion of a transaction that a client signs.
Cryptographic hasher for an BCS-serializable #item
Cryptographic hasher for an BCS-serializable #item
Call a Move script.
Call a Move script function.
A transaction for which the signature has been verified. Created by
SignedTransaction::check_signature and RawTransaction::sign.
A transaction that has been signed.
Cryptographic hasher for an BCS-serializable #item
TransactionInfo is the object we store in the transaction accumulator. It consists of the
transaction as well as the execution result of this transaction.
Cryptographic hasher for an BCS-serializable #item
The output of executing a transaction.
This differs from TransactionListWithProof in that TransactionOutputs are stored (no transactions). Events are stored inside each TransactionOutput.
The description of a type argument in a script.
The result of running the transaction through the VM validator.
Struct for encoding vector<vector
Enums
How to call a particular Move script (aka. an “ABI”).
Transaction will be the transaction type used internally in the diem node to represent the
transaction to be processed and persisted.
Different kinds of transactions.
The status of executing a transaction. The VM decides whether or not we should Keep the
transaction output or Discard it based upon the execution of the transaction. We wrap these
decisions around a VMStatus that provides more detail on the final execution state of the VM.
Two different kinds of WriteSet transactions.