Transaction Envelope
Pronunciation: tran-ZAK-shun EN-vuh-lohp
Definition
A transaction envelope is an outer protocol structure that identifies a transaction format and contains or frames the fields needed for decoding, signing, and processing. It may include a type identifier, payload, signatures, and metadata. On Ethereum, EIP-2718 defines typed transaction envelopes so new transaction formats can coexist without ambiguous decoding.
Overview
Meaning and scope
A transaction envelope is an outer protocol structure that identifies a transaction format and contains or frames the fields needed for decoding, signing, and processing. It may include a type identifier, payload, signatures, and metadata. On Ethereum, EIP-2718 defines typed transaction envelopes so new transaction formats can coexist without ambiguous decoding.
Mechanism and operation
A transaction envelope tells software how to interpret the bytes that follow. In Ethereum’s typed model, a leading transaction type identifies the rules for decoding the payload. This allows legacy, access-list, dynamic-fee, blob, and future transaction formats to coexist. The envelope can therefore separate format selection from the internal Transaction Body and its individual fields. The term is also used more broadly for a wrapper containing payload, signatures, network domain, or transport information. Developers must distinguish a consensus-critical envelope from an API-specific JSON wrapper that is removed before broadcast. Only fields included in the signing and serialization specification receive cryptographic commitment.
Practical payment example
A signing client receives a serialized transaction wrapper containing chain context, payload and authorization fields. It checks the envelope type before calculating the signing digest to prevent cross-network confusion.
Operational checks
However, clients, wallets, hardware signers, RPC services, and block explorers must recognize the type. Unsupported types should be rejected clearly rather than decoded as a familiar transaction. Chain identifiers and domain separation also help prevent signed envelopes from being replayed in unintended contexts. Systems should store the transaction type and original serialized envelope alongside decoded fields.
Distinctions and limits
Not every protocol defines an object with that exact name. Typed envelopes improve extensibility because new features do not need to overload old field layouts.
Related reading
Related definitions: transaction, Transaction Body.
Example
A signing client receives a serialized transaction wrapper containing chain context, payload and authorization fields. It checks the envelope type before calculating the signing digest to prevent cross-network confusion.
Comparison
Typed envelopes improve extensibility because new features do not need to overload old field layouts. However, clients, wallets, hardware signers, RPC services, and block explorers must recognize the type. Unsupported types should be rejected clearly rather than decoded as a familiar transaction.
Key Takeaway
A transaction envelope identifies how a transaction is structured and interpreted, enabling protocol evolution without ambiguous decoding.
Sources
- EIP-2718: Typed Transaction Envelope — Ethereum Improvement Proposals (2026-08-02)
- Ethereum Transactions — Ethereum.org (2026-08-02)
- EIP-7702: Set Code for EOAs — Ethereum Improvement Proposals (2026-08-02)