You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a debug_traceBlockByNumber using flatCallTracer the returned result incorrectly includes each transaction's block's parentHash instead of hash.
I imagine this has something to do with loading the parents state to re-run/trace each transaction.
Describe the bug
When running a debug_traceBlockByNumber using flatCallTracer the returned result incorrectly includes each transaction's block's parentHash instead of hash.
I imagine this has something to do with loading the parents state to re-run/trace each transaction.
Steps to reproduce
Eg. Ethereum Mainnet
returns results with:
where it should return results with:
Reference: https://etherscan.io/block/21145997
Similarly on Base Mainnet
Traces have
the correct trace would have
https://basescan.org/block/22147096
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
latest docker release:
reth Version: 1.1.1
Commit SHA: 15c230b
Build Timestamp: 2024-11-05T12:39:46.613054379Z
Build Features: asm_keccak,jemalloc
Build Profile: maxperf
What database version are you on?
Current database version: 2
Local database version: 2
Which chain / network are you on?
Tested on Base Mainnet and Ethereum Mainnet using op-reth and reth.
What type of node are you running?
Archive (default)
What prune config do you use, if any?
Archive
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: