Module transaction
Expand description
RPC types for transactions
Modules§
- request
- Alloy basic Transaction Request type.
Structs§
- Access
List - AccessList as defined in EIP-2930
- Access
List Item - A list of addresses and storage keys that the transaction plans to access. Accesses outside the list are possible, but become more expensive.
- Access
List Result AccessListResultfor handling errors frometh_createAccessList- AnyReceipt
Envelope - Receipt envelope, as defined in EIP-2718.
- Authorization
- An unsigned EIP-7702 authorization.
- Blob
Transaction Sidecar - This represents a set of blobs, and its corresponding commitments and proofs.
- Receipt
- Receipt containing result of transaction execution.
- Receipt
With Bloom Receiptwith calculated bloom filter.- Transaction
- Transaction object used in RPC.
- Transaction
Info - Additional fields in the context of a (maybe) pending block that contains this transaction.
- Transaction
Input - Helper type that supports both
dataandinputfields that map to transaction input data. - Transaction
Receipt - Transaction receipt
- Transaction
Request - Represents all transaction requests to/from RPC.
Enums§
- Conversion
Error - Error variants when converting from crate::Transaction to [alloy_consensus::Signed] transaction.
- Receipt
Envelope - Receipt envelope, as defined in EIP-2718.
- Transaction
Input Kind - Represents how a
TransactionRequesthandles input/data fields.
Traits§
- Transaction
Trait - Represents a minimal EVM transaction. Currently, EIP-1559, EIP-4844, and EIP-7702 support dynamic fees. We call these transactions “dynamic fee transactions”. We call non dynamic fee transactions(EIP-155, EIP-2930) “legacy fee transactions”.