Typed Transaction Envelope

The five-minute read

One action, walked through

1. Open EIP 2718 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: TransactionType || TransactionPayload is a valid transaction and TransactionType || ReceiptPayload is a valid transaction receipt where TransactionType identifies the format of the transaction and Payload is the transaction/receipt contents, which are defined in future EIPs.
3. Name the object that changes: EOA, FORK_BLOCK_NUMBER, MUST.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing EIP 2718 at the status the text itself states: Final.
• The object that has to change is EOA, FORK_BLOCK_NUMBER, MUST. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What must an implementation of Typed Transaction Envelope accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: EOA, FORK_BLOCK_NUMBER, MUST?

Terms

EIP 2718

The public text titled Typed Transaction Envelope.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• TransactionType || TransactionPayload is a valid transaction and TransactionType || ReceiptPayload is a valid transaction receipt where TransactionType identifies the format of the transaction and Payload is the transaction/receipt contents, which are defined in future EIPs.
• In the past, when we have wanted to add new transaction types we have had to ensure they were backward compatible with all other transactions, meaning that you could differentiate them based only on the encoded payload, and it was not possible to have a transaction that matched both types.
• This was seen in EIP-155 where the new value was bit-packed into one of the encoded fields.

How the mechanism is specified

• Taken from the specification, the next constraint is: In the past, when we have wanted to add new transaction types we have had to ensure they were backward compatible with all other transactions, meaning that you could differentiate them based only on the encoded payload, and it was not possible to have a transaction that matched both types.
• Locate EOA, FORK_BLOCK_NUMBER, MUST in EIP 2718 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use EIP 2718 when a pitch says 'Typed Transaction Envelope' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.