Inconsistency for transaction's block #251
Description
Since node-reth 0.14 (we noticed the inconsistency when upgrading from 0.12 to 0.14), we noted an inconsistency on the block hash for the fresh transactions included into the latest block. The transaction's block hash doesn't match with the block it was previously announced to be in.
Scenario to reproduce the inconsistency:
- Subscribe to newHeads
- For a sample of the new head's transactions, retrieve the transaction's detail with an eth_getTransactionByHash
- Compare the newHeads block hash with the transaction's block hash.
The inconsistency concerns the block hash only and not the block number.
Logs from a simple testing script:
2025/12/05 10:50:27 new head: block hash 0xed229c46d94eb1e840b9ee363c8fb2559634c4e816aea39f690aac4c61b0e5ad, block number 39069440
2025/12/05 10:50:27 checking tx 0x8adfd6984eaf2b030e5f58de8131753781ba51c87b3c1c3b7a21f20ea8ae4109
2025/12/05 10:50:27 tx 0x8adfd6984eaf2b030e5f58de8131753781ba51c87b3c1c3b7a21f20ea8ae4109 has a different block hash. Expected 0xed229c46d94eb1e840b9ee363c8fb2559634c4e816aea39f690aac4c61b0e5ad, got 0x27067af9a39231f16a4782a8d11f83ade8ae6d60efcce3de327dc583843bd867
2025/12/05 10:50:27 checking tx 0x38e37a618e8690660d146171160f40842600dc9b1223574d579f54f9eda90e46
2025/12/05 10:50:27 tx 0x38e37a618e8690660d146171160f40842600dc9b1223574d579f54f9eda90e46 has a different block hash. Expected 0xed229c46d94eb1e840b9ee363c8fb2559634c4e816aea39f690aac4c61b0e5ad, got 0x27067af9a39231f16a4782a8d11f83ade8ae6d60efcce3de327dc583843bd867