@@ -396,16 +396,18 @@ block.
396
396
` [txtypes: B, [txsize₁: P, txsize₂: P, ...], [txhash₁: B_32, txhash₂: B_32, ...]] `
397
397
398
398
This message announces one or more transactions that have appeared in the network and
399
- which have not yet been included in a block. The message payload describes a list of
400
- of transactions, but note that it is encoded as three separate elements.
399
+ which have not yet been included in a block. The message payload describes a list of of
400
+ transactions, but note that it is encoded as three separate elements.
401
401
402
- The ` txtypes ` element is a byte array containing the announced [ transaction types] .
403
- The other two payload elements refer to the sizes and hashes of the announced transactions.
404
- Size refers to the length of the 'consensus encoding' of a typed transaction (i.e. the bytes
405
- without rlp header for typed transactions, and with header for legacy transactions). All
406
- three payload elements must contain an equal number of items.
402
+ The ` txtypes ` element is a byte array containing the announced [ transaction types] . The
403
+ other two payload elements refer to the sizes and hashes of the announced transactions.
404
+ All three payload elements must contain an equal number of items.
407
405
408
- The recommended soft limit for this message is 4096 hashes (~ 150 KiB).
406
+ ` txsizeₙ ` refers to the length of the 'consensus encoding' of a typed transaction, i.e.
407
+ the byte size of ` tx-type || tx-data ` for typed transactions, and the size of the
408
+ RLP-encoded ` legacy-tx ` for non-typed legacy transactions.
409
+
410
+ The recommended soft limit for this message is 4096 items (~ 150 KiB).
409
411
410
412
To be maximally helpful, nodes should inform peers of all transactions that they may not
411
413
be aware of. However, nodes should only announce hashes of transactions that the remote
0 commit comments