From ba3833de92d6012ff79d525bf20617fa46d913f2 Mon Sep 17 00:00:00 2001 From: Micah Zoltu Date: Thu, 8 Oct 2020 10:58:20 +0800 Subject: [PATCH] Automatically merged updates to draft EIP(s) 2972 (#3029) Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing --- EIPS/eip-2972.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-2972.md b/EIPS/eip-2972.md index b2acc9ac..d9c15a3f 100644 --- a/EIPS/eip-2972.md +++ b/EIPS/eip-2972.md @@ -60,7 +60,7 @@ By having the signature SSZ encoded up front, we can easily extract the signatur ### TransactionType 0/1 0x65000000 element `0x00 || yParity || r || s || 0x65000000 || rlp(nonce, gasPrice, gasLimit, to, value, data)` is the same as `ssz(0, yParity, r, s, rlp(nonce, gasPrice, gasLimit, to, value, data))`, which may prove convenient for some clients. It costs us 4 extra bytes on the wire (mostly zeros), but the authors deem this a worthwhile trade to be SSZ encodable/decodable. ### SSZ for receipt encoding -There is a weak consensus that RLP is not a particularly encoding scheme for hashed data partially due to its inability to be streamed. +There is a weak consensus that RLP is not a particularly good encoding scheme for hashed data partially due to its inability to be streamed. SSZ is almost certainly going to be included in Ethereum at some point in the future, so clients likely have access to an SSZ decoder. For this particular case, manual decoding without a full SSZ decoder isn't too complicated, though it does require doing a bit of "pointer math" since `logs` is an array of variable length items