eth/65: transaction announcements and retrievals

The five-minute read

One action, walked through

1. Open EIP 2464 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Three additional message types into the eth protocol (releasing a new version, eth/65): NewPooledTransactionHashes (0x08) to announce a set of transactions without their content; GetPooledTransactions (0x09) to request a batch of transactions by their announced hash; and PooledTransactions (0x0a) to reply to a transaction request.
3. Name the object that changes: eth/65: transaction announcements and retrievals.
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 2464 at the status the text itself states: Final.
• The object that has to change is eth/65: transaction announcements and retrievals. 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 eth/65: transaction announcements and retrievals 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: eth/65: transaction announcements and retrievals?

Terms

EIP 2464

The public text titled eth/65: transaction announcements and retrievals.

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

• Three additional message types into the eth protocol (releasing a new version, eth/65): NewPooledTransactionHashes (0x08) to announce a set of transactions without their content; GetPooledTransactions (0x09) to request a batch of transactions by their announced hash; and PooledTransactions (0x0a) to reply to a transaction request.
• This permits reducing the bandwidth used for transaction propagation from linear complexity in the number of peers to square root; and also reducing the initial transaction exchange from 10s-100s MB to len(pool) 32B ~= 128KB.
• The eth network protocol has two ways to propagate a newly mined block: it can be broadcast to a peer in its entirety (via NewBlock (0x07) in eth/64 and prior or it can be announced only (via NewBlockHashes (0x01)).

How the mechanism is specified

• Taken from the specification, the next constraint is: This permits reducing the bandwidth used for transaction propagation from linear complexity in the number of peers to square root; and also reducing the initial transaction exchange from 10s-100s MB to len(pool) 32B ~= 128KB.
• Locate eth/65: transaction announcements and retrievals in EIP 2464 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 2464 when a pitch says 'eth/65: transaction announcements and retrievals' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.