From c62574b2fd14499b0364a093abe2c80fd99b69f8 Mon Sep 17 00:00:00 2001 From: rakita Date: Thu, 29 Dec 2022 16:14:54 +0100 Subject: [PATCH] bug(consensus): Remove mixHash zero check after merge (#652) * bug(consensus): Remove mixHash zero check after merge * chore(clippy): make clippy happy Co-authored-by: Matthias Seitz --- crates/consensus/src/verification.rs | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/crates/consensus/src/verification.rs b/crates/consensus/src/verification.rs index 06ce8cc1ea..df3856101b 100644 --- a/crates/consensus/src/verification.rs +++ b/crates/consensus/src/verification.rs @@ -3,7 +3,7 @@ use crate::{config, Config}; use reth_interfaces::{consensus::Error, Result as RethResult}; use reth_primitives::{ BlockNumber, Header, SealedBlock, SealedHeader, Transaction, TransactionSignedEcRecovered, - TxEip1559, TxEip2930, TxLegacy, EMPTY_OMMER_ROOT, H256, U256, + TxEip1559, TxEip2930, TxLegacy, EMPTY_OMMER_ROOT, U256, }; use reth_provider::{AccountProvider, HeaderProvider}; use std::{ @@ -57,9 +57,8 @@ pub fn validate_header_standalone( return Err(Error::TheMergeOmmerRootIsNotEmpty) } - if header.mix_hash != H256::zero() { - return Err(Error::TheMergeMixHashIsNotZero) - } + // mixHash is used instead of difficulty inside EVM + // https://eips.ethereum.org/EIPS/eip-4399#using-mixhash-field-instead-of-difficulty } Ok(())