From ee0a31576262e43c3291050786f552bab9bef703 Mon Sep 17 00:00:00 2001 From: Micah Zoltu Date: Thu, 3 Dec 2020 18:40:26 +0800 Subject: [PATCH] Automatically merged updates to draft EIP(s) 2976 (#3149) 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-2976.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-2976.md b/EIPS/eip-2976.md index 473f2935..da7808d7 100644 --- a/EIPS/eip-2976.md +++ b/EIPS/eip-2976.md @@ -35,7 +35,7 @@ All changes specified below apply to the `eth/TBD` protocol/version and newer. * `TransactionType` is a positive unsigned 8-bit number between `0` and `0x7f` that represents the type of the transcation * `TransactionPayload` is an opaque byte array whose interpretation is dependent on the `TransactionType` and defined in future EIPs * `LegacyTransaction` is an RLP encoded array of the form `[nonce, gasPrice, gasLimit, to, value, data, v, r, s]` -* `TransactionId` is `ssz_tree_root(TypedTransaction)` or `keccak256(LegacyTransaction)` +* `TransactionId` is `keccak256(Transaction)` ### Protocol Behavior If a client receives a `TransactionType` it doesn't recognize via any message, it **SHOULD** disconnect the peer that sent it.