Typed Transactions over Gossip

The five-minute read

One action, walked through

1. Open EIP 2976 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Typed Transactions can be sent over devp2p as TransactionType || TransactionPayload.
3. Name the object that changes: SHOULD, MUST, NOT.
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 2976 at the status the text itself states: Final.
• The object that has to change is SHOULD, MUST, NOT. A neighbouring document with a similar name is not this one.
• Measurements of delay in one year do not travel with the specification.

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

• Which message does Typed Transactions over Gossip add, and which old peer must still be answered?
• What does a node do when the short form fails and the full object is required?
• Which names are normative: SHOULD, MUST, NOT?

Terms

EIP 2976

The public text titled Typed Transactions over Gossip.

Final

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

The problem the paper names

A node that cannot fetch, filter, or relay the data it is supposed to validate is not a peer of the network the paper describes.

What the design proposes

• Typed Transactions can be sent over devp2p as TransactionType || TransactionPayload.
• The exact contents of the TransactionPayload are defined by the TransactionType in future EIPs, and clients may start supporting their gossip without incrementing the devp2p version.
• If a client receives a TransactionType that it doesn't recognize, it SHOULD disconnect from the peer who sent it.

How the mechanism is specified

• Taken from the specification, the next constraint is: The exact contents of the TransactionPayload are defined by the TransactionType in future EIPs, and clients may start supporting their gossip without incrementing the devp2p version.
• Locate SHOULD, MUST, NOT in EIP 2976 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

• A peer protocol is not a consensus rule. A peer can disconnect. A block is still valid or not on its own.
• Measurements of delay in one year do not travel with the specification.
• 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 2976 when a pitch says 'Typed Transactions over Gossip' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.