removing redundant blob prefix from versioned hashes in BlobTransaction container

Author: g11tech

EIPS/eip-4844.md

@@ -121,7 +121,7 @@ class BlobTransaction(Container):
     data: ByteList[MAX_CALLDATA_SIZE]
     access_list: List[AccessTuple, MAX_ACCESS_LIST_SIZE]
     max_fee_per_data_gas: uint256
-    blob_versioned_hashes: List[VersionedHash, MAX_VERSIONED_HASHES_LIST_SIZE]
+    versioned_hashes: List[VersionedHash, MAX_VERSIONED_HASHES_LIST_SIZE]
 
 class AccessTuple(Container):
     address: Address # Bytes20
@@ -153,8 +153,8 @@ When a blob transaction is passed through the network (see the [Networking](#net
 the `TransactionNetworkPayload` version of the transaction also includes `blobs`, `commitments` and `proofs`.
 The execution layer verifies the wrapper validity against the inner `TransactionPayload` after signature verification as:
 
-- `blob_versioned_hashes` must not be empty
-- All hashes in `blob_versioned_hashes` must start with the byte `BLOB_COMMITMENT_VERSION_KZG`
+- `versioned_hashes` must not be empty
+- All hashes in `versioned_hashes` must start with the byte `BLOB_COMMITMENT_VERSION_KZG`
 - There may be at most `MAX_DATA_GAS_PER_BLOCK // DATA_GAS_PER_BLOB` total blob commitments in a valid block.
 - There is an equal amount of versioned hashes, commitments, blobs and proofs.
 - The commitments hash to the versioned hashes, i.e. `kzg_to_versioned_hash(commitment[i]) == versioned_hash[i]`
@@ -182,7 +182,7 @@ def signed_tx_hash(tx: SignedBlobTransaction) -> Bytes32:
     return keccak256(BLOB_TX_TYPE + ssz.serialize(tx))
 ```
 
-Blob transactions with empty `blob_versioned_hashes` are also considered invalid during execution block verification, and must not be included in a valid block.
+Blob transactions with empty `versioned_hashes` are also considered invalid during execution block verification, and must not be included in a valid block.
 
 ### Header extension
 
@@ -247,8 +247,8 @@ The `ethereum/consensus-specs` repository defines the following beacon-node chan
 ### Opcode to get versioned hashes
 
 We add an opcode `DATAHASH` (with byte value `HASH_OPCODE_BYTE`) which reads `index` from the top of the stack
-as big-endian `uint256`, and replaces it on the stack with `tx.message.blob_versioned_hashes[index]`
-if `index < len(tx.message.blob_versioned_hashes)`, and otherwise with a zeroed `bytes32` value.
+as big-endian `uint256`, and replaces it on the stack with `tx.message.versioned_hashes[index]`
+if `index < len(tx.message.versioned_hashes)`, and otherwise with a zeroed `bytes32` value.
 The opcode has a gas cost of `HASH_OPCODE_GAS`.
 
 ### Point evaluation precompile
@@ -294,7 +294,7 @@ def calc_data_fee(tx: SignedBlobTransaction, parent: Header) -> int:
     return get_total_data_gas(tx) * get_data_gasprice(parent)
 
 def get_total_data_gas(tx: SignedBlobTransaction) -> int:
-    return DATA_GAS_PER_BLOB * len(tx.message.blob_versioned_hashes)
+    return DATA_GAS_PER_BLOB * len(tx.message.versioned_hashes)
 
 def get_data_gasprice(header: Header) -> int:
     return fake_exponential(
@@ -320,7 +320,7 @@ def validate_block(block: Block) -> None:
         # ensure that the user was willing to at least pay the current data gasprice
         assert tx.message.max_fee_per_data_gas >= get_data_gasprice(parent(block).header)
 
-        num_blobs += len(tx.message.blob_versioned_hashes)
+        num_blobs += len(tx.message.versioned_hashes)
 
     # check that the excess data gas is correct
     expected_edg = calc_excess_data_gas(parent(block).header, num_blobs)
@@ -352,7 +352,7 @@ We do network-level validation of `BlobTransactionNetworkWrapper` objects as fol
 
 ```python
 def validate_blob_transaction_wrapper(wrapper: BlobTransactionNetworkWrapper):
-    versioned_hashes = wrapper.tx.message.blob_versioned_hashes
+    versioned_hashes = wrapper.tx.message.versioned_hashes
     commitments = wrapper.commitments
     blobs = wrapper.blobs
     proofs = wrapper.proofs