eip-5793: update eip

EIPS/eip-5793.md

@@ -1,7 +1,7 @@
 ---
 eip: 5793
 title: eth/68 - Add tx type to tx announcement
-description: Adds the transaction type to tx announcement messages in the wire protocol
+description: Adds the transaction type and transaction size to tx announcement messages in the wire protocol
 author: Marius van der Wijden (@MariusVanDerWijden)
 discussions-to: https://ethereum-magicians.org/t/eip-5793-eth-68-add-transaction-type-to-tx-announcement/11364
 status: Draft
@@ -13,13 +13,13 @@ requires: 2464, 2481, 4938
 
 ## Abstract
 
-The [Ethereum Wire Protocol](https://github.com/ethereum/devp2p/tree/master/caps/eth.md) defines request and response messages for exchanging data between clients. The `NewPooledTransactionHashes` message response announces transactions available in the node. We propose to extend the `NewPooledTransactionHashes` message such that the node sends both the transaction hashes as well as the transaction types as defined in EIP-2718.
+The [Ethereum Wire Protocol](https://github.com/ethereum/devp2p/tree/master/caps/eth.md) defines request and response messages for exchanging data between clients. The `NewPooledTransactionHashes` message response announces transactions available in the node. We propose to extend the `NewPooledTransactionHashes` message such that the node sends the transaction hashes as well as the transaction types and the size of the transactions as defined in EIP-2718.
 
 ## Motivation
 
 The `NewPooledTransactionHashes` message announces transaction hashes, allowing the peer to selectively fetch transactions it does not yet have.
 
-With the upcoming EIP-4844 a new transaction type is introduced for blob transactions. Since they are large, broadcasting them will increase bandwidth requirements. Adding the transaction type to the `NewPooledTransactionHashes` message will allow nodes to select which types of transactions they want to fetch.
+With the upcoming EIP-4844 a new transaction type is introduced for blob transactions. Since they are large, broadcasting them will increase bandwidth requirements. Adding the transaction type and the transaction size to the `NewPooledTransactionHashes` message will allow nodes to select which types of transactions they want to fetch.
 
 An additional benefit is that clients now know which transaction type to expect before fetching them.
 
@@ -29,7 +29,7 @@ Modify the following message type from the `eth` protocol:
 
 * `NewPooledTransactionHashes (0x08)`
 * * **(eth/67)**: `[hash_0: B_32, hash_1: B_32, ...]`
-* * **(eth/68)**: `[[type_0: B_1, type_1: B_1, ...], [hash_0: B_32, hash_1: B_32, ...]]`
+* * **(eth/68)**: `[[type_0: B_1, type_1: B_1, ...], [size_0: B_4, size_1: B_4, ...], [hash_0: B_32, hash_1: B_32, ...]]`
 
 ## Rationale
 This change will make the eth protocol future proof for new transaction type that might not be relevant for all nodes. It gives the receiving node better control over the data it fetches from the peer as well as allow throttling the download of specific types.